Settings

Nothing needs setting. Install, run /reload-plugins or start a new session, and ask Claude a NetSuite question. Every setting has a working default.

All settings

Setting	Default	What it does
`account_id`	(empty)	Optional. Keys the cache instead of the connector, so one account reached through several connectors shares a cache
`environment`	production	`production` or `sandbox`. Only used with `account_id`
`read_only`	true	Blocks all creates and updates
`inline_max_chars`	6000	Results larger than this go to a file. Accepts 500 to 200,000
`saved_search_default_rows`	200	Row cap added to saved searches without `range_end`. Accepts 1 to 1000
`suiteql_default_page_size`	500	`pageSize` (with `pageIndex: 0`) added to SuiteQL without one, so a query returns one page. Accepts 5 to 1000
`results_retention_days`	7	Saved results and write previews older than this are deleted at the next session start. Accepts 1 to 3650
`ttl_overrides`	(none)	Days before a cache section is stale, for example `searches=2, periods=0.5`

A query that ends in FETCH FIRST n ROWS ONLY with n up to 1000 gets a page of n rows instead of the default page size. Any pageSize below 5 is raised to 5, the connector's minimum.

Change a setting

Ask Claude, or run nsx yourself (see Commands for how to find it):

nsx config show
nsx config set inline_max_chars=10000
nsx config set results_retention_days=14 saved_search_default_rows=500

nsx config show lists every setting, its value and where the value came from. An empty value resets a setting to its default:

nsx config set inline_max_chars=

Changes apply to the next NetSuite call. There's no restart.

Turning writes on needs your terminal

Setting read_only=false is left to you, and Claude is told not to do it. nsx config set refuses it from anything Claude Code runs: Claude's Bash tool, a ! command typed into Claude Code, or a command wrapped in script. Run it in your own terminal, outside Claude Code:

node <path to nsx.mjs> config set read_only=false

When the write guard blocks a write, Claude prints this command with the full path filled in.

This isn't a hard lock. The setting lives in a plain settings.json in the plugin's data directory, so anyone who can edit that file can change it. Two things stop an accidental change: the command refuses to run outside a real terminal, and every write still needs your approval in Claude Code's permission prompt. A read_only value the plugin doesn't recognise counts as true. See Writes and approvals.

ttl_overrides

Each cache section goes stale after a number of days. When a section Claude needs is stale, Claude refreshes it first. The defaults are:

Section	Days
`searches`, `periods`	1
`reports`, `subsidiaries`	7
`recordtypes`, `fields`, `recordmeta`, `books`, `contexts`, `nexus`, `profile`	30

To change them, pass a comma-separated list of section=days. Fractions work:

nsx config set "ttl_overrides=searches=2, periods=0.5"

That makes saved searches stale after two days and periods after twelve hours. An unknown section name or a zero is refused. nsx cache status shows each section's TTL next to its age.

The same account reached through two connectors gets two caches. That happens with the claude.ai connector plus a Claude Code MCP server, for example. To share one cache, set both keys:

nsx config set account_id=1234567 environment=production

The account and environment then key the cache instead of the connector. Set them to the account the connector actually reaches. If they don't match, /su-ns-harness:doctor flags it. The usual fix is to clear account_id so the cache follows the connector again.

All settings

Change a setting

Turning writes on needs your terminal

ttl_overrides

Sharing one cache across connectors

Install su-ns-harness