Getting Started
What is Node9?Quick StartHow It WorksForecastAgent IntegrationsAccount & Machine
Configuration
ConfigurationPrivacy & Cloud ModeSmart RulesEffective ConfigurationPersistent DecisionsPause & Resume
Protections
ShieldsSandboxSecurity PostureContent Scanner (DLP)Trusted HostsCanary CredentialsSkill PinningRepository ScanningEgress ControlBadges
Integrations
MCP GatewayMCP ServerPython SDKGoverned Agents
Operations
Mission ControlReportSecurityAgentic Threat CoverageBlast RadiusSessions & Live ActivityRedacting Session HistoryCloud Policy Rules
Help
Help & SupportAbout Node9

Account & Machine · node9 documentation

Account & Machine

Creating an account, connecting this machine to a workspace, and undoing both.

Account
node9 signup
node9 signup --login    # already have one
Opens the dashboard in your browser. node9 runs without an account; this is for the parts that involve a team.
Connect a machine
node9 login
node9 login --no-browser    # print the link instead
Run it on the machine and node9 opens your browser to confirm it. Nothing is copied and pasted, and there is no key to keep anywhere.

The other two ways in

From the dashboard
node9 connect <token>
node9 connect <token> --profile work
For onboarding a machine you are not sitting at. The dashboard issues the token, and the same setup runs from it: credentials, agent wiring, policy sync. A profile lets one machine follow more than one workspace without the credentials colliding.
Service and CI accounts
node9 login <service-key>
node9 login --force          # interactive login inside CI
A key is still how an account with no person behind it authenticates. node9 refuses an interactive login when it detects CI unless you say otherwise, so a pipeline cannot hang waiting for a browser nobody will open.
Disconnecting does not disarm the machine
node9 logout
Revokes this machine's key and stops it following the workspace. Enforcement keeps running from local configuration. A machine that has left a workspace is not an unprotected machine, and the reverse is worth knowing too: it stops receiving policy the workspace publishes.

Which layer governs turns on one thing: whether the machine holds a workspace key. It does, and the workspace decides. It does not, and the local stack does. Logging out removes the key, so local configuration takes over again by the same rule, not as a fallback.
Removing node9
node9 uninstall           # hooks only
node9 uninstall --purge   # also deletes ~/.node9/
Without --purge, hooks are removed and your configuration, audit log and credentials stay. With it they are deleted, and the audit log is the record of everything the agent did on this machine. Copy it first if it might be wanted.