Node CLI reference

Keep four layers separate: the installed binary, the account credential, this machine’s identity, and the running process.

Connect an account

• login — interactive sign-in, then start in the background
• pair — wait for Desktop or App to claim a one-time code
• join [CODE] — redeem a Desktop join code
• logout — clear the account credential and stop; keep machine identity

Useful flags: --name 'lab-1', --no-start, --foreground, and --yes where confirmation is supported.

Run and inspect

• start / stop — change the process without changing login
• autostart status|on|off — inspect or change startup integration
• info — account, identity, process, and paths
• where — binary, data directories, and relevant environment
• logs, logs -n 200, logs --once — follow or inspect logs
• code — show the permanent short code
• version — show the binary version
• lang — show or set the persisted CLI language

Diagnose and reset

• doctor — check binary, API, account, and process, then suggest a fix
• reset --auth — clear the credential, keeping machine identity
• reset --identity — clear identity; the next connection creates or claims a new cloud identity
• reset --all — remove the complete local configuration

Upgrade and uninstall

• upgrade — install the latest approved binary and keep configuration
• uninstall — remove the binary
• uninstall --purge — remove binary and configuration

If an install replaces a running Node, it normally stops and restarts it. Set AIHPER_NO_RESTART=1 only when you deliberately want to replace the file without restarting.

Identity rule

logout is not “forget this machine”. The instance ID stays so a later login can reclaim the same cloud entry. Use reset --identity only when you intentionally want a new identity.