Privacy & Cloud Mode

Choose how much Node9 connects to the cloud via approvers.cloud.

Local Onlyapprovers.cloud: false

All policy decisions stay on your machine. No tool call data, no agent names, no audit events are sent to the cloud.

Use this when working with proprietary code, sensitive data, or air-gapped environments.

node9 login --local

Sets approvers.cloud to false in your global config. Policy is read from your local config files only.

Cloud Connectedapprovers.cloud: true

Intercept events are streamed to Mission Control in real time. Policy can be managed centrally via the Cloud Policy Studio.

When cloud is enabled, Cloud Policy Studio has the highest priority in the config hierarchy — it overrides your local config files.

node9 login <your-api-key>

Team members can see agent activity and approve flagged actions from the dashboard.

Named Credential Profiles

Multiple profiles let you manage several workspaces on one machine without conflicting credentials.

Saving and switching profiles

# Save credentials to a named profile
node9 login <key1> --profile work
node9 login <key2> --profile personal

# Activate a profile for the current session
export NODE9_PROFILE=work

# Or per-project: set apiKey directly in node9.config.json
{
  "apiKey": "key_abc123"
}

Profile data is stored in ~/.node9/credentials.json:

{
  "default":  { "apiKey": "key_...", "apiUrl": "https://..." },
  "work":     { "apiKey": "key_...", "apiUrl": "https://..." },
  "personal": { "apiKey": "key_...", "apiUrl": "https://..." }
}

Credential Priority Chain

Resolution order (highest → lowest)

NODE9_API_KEY environment variable — wins over everything
Profile named by NODE9_PROFILE env var in ~/.node9/credentials.json
default profile in ~/.node9/credentials.json

Note: node9.config.json is a policy file — it does not carry credentials. The CLI reads API keys only from the env var or from credentials.json.

Privacy & Cloud Mode · node9 documentation