Skip to main content
The wizard signs in before the main menu opens, so most of the time there is nothing to do here. The account screen exists for the cases where there is: the wrong account, a second team, a laptop handed on.

​
The rows

Switch and Remove act on the other saved accounts, so they only appear when this device holds more than one.

​
Several accounts on one device

Probe stores credentials in named contexts, the way kubectl stores clusters. One device can hold several; exactly one is active. To add one, sign in to it by name:
Each context carries an endpoint, its credentials, and its anchors — the active workspace and project that scope commands like probe run start.
“Signed in as X” is only half the answer. The other half is which of this device’s saved accounts is currently answering, which is why the wizard’s summary shows the active context alongside the email.

​
What sign-out actually does

Signing out is not just forgetting a token:
  • the token this device holds is revoked, not merely deleted
  • the active context is cleared
  • session capture stops, so it cannot keep uploading to the account you just left
  • local import history is cleared
The plugins stay installed. Removing those is Uninstall.
Credentials in your shell outrank the config file. PROBE_TOKEN, PROBE_MCP_TOKEN, PROBE_INGEST_TOKEN and PROBE_SERVICE_TOKEN are all checked before it, so after a sign-out the CLI will still authenticate if one of those is exported. The wizard names any it finds — it cannot unset a variable in your parent shell, and staying quiet about it would be the same lie as an empty file with live capture behind it.

​
Signing in without a browser

For air-gapped machines and CI:
All three write ~/.config/probe/config.json and install nothing. Or skip the file entirely and set PROBE_TOKEN in the environment. To mint and manage tokens:

Authentication in full

Token kinds, scopes, environment variables and the read-only MCP credential.

​
For scripts