Install, update and remove Probe — through the wizard, with the commands underneath.
One command sets everything up. The tabs on this page show the wizard first and the equivalent command second, for when a script is doing the work.
npx probe-research install
The npm package is a thin launcher: it resolves and runs the real CLI, so you do not need Python tooling set up first. It signs you in, installs the plugins for the coding agents you pick, and offers to import work you already have.
Pick your coding agents, review what will be set up, install, and import. npx probe-research with no verb opens the main menu instead — the right entry point when you are managing an install rather than creating one.Add --agent codex for Codex, or --agent both for Claude Code and Codex together.
Same flow, no prompts. An omitted flag preserves whatever is already configured, so this is safe to run repeatedly against a fleet. See unattended use.
probe wizard --action manual
Prints every command the wizard runs, for the agents you name — generated from the same constants, so it cannot drift. This is the path for air-gapped machines and for anyone who wants to read the commands before running them.
The last step authorizes this Codex device — Codex needs its own capture credential, separate from Claude Code’s.
On pi, check the result rather than assuming it. A settings file that carries the package without its extensions loads the skills and the MCP manifest but never spawns the capture daemon — tracking reads as on while nothing is captured. probe doctor names that state.
The two plugins are separate on purpose, because they are separate consent decisions: tracking adds skills and read-only search, tap streams your sessions to the team knowledgebase.
If you are instrumenting a training script and no coding agent is involved, skip the wizard entirely:
pip install probe-research
uv tool install probe-research
uv add probe-research
One package ships both surfaces — import probe (the SDK) and probe (the CLI). They are the same implementation with different ergonomics, so they have capability parity.Then sign in:
probe login
Auth and accounts
Signing in, switching accounts, tokens, contexts, and air-gapped sign-in.
The read-only MCP server ships inside the tracking plugin, so a plugin install needs no extra step. To wire it into another MCP client:
probe-research-mcp # stdio server
The hosted HTTP endpoint is https://mcp.research.prbe.ai/mcp. Credentials:
probe mcp status # where the credential resolves from, and whether it worksprobe mcp headers # Authorization header as JSONprobe mcp env # the export line, for clients that only read the environment
The server prefers PROBE_MCP_TOKEN, a separately minted read-only token. It falls back to PROBE_TOKEN for local development and exposes no mutation tools either way.
MCP reference
All six tools, token budgets, pagination and entity views.
Auto-update is on by default and runs in the background at session start.
Wizard
Command
npx probe-research # → Update to the latest version
The On this device block carries a Versions section: what you have installed, what is published, and whether you are current — graded per component, because CLI, SDK, plugin and tap update on their own cadences.To stop background upgrades, untick Automatic updates in Settings.
probe wizard --action update # update nowprobe wizard --no-auto-update --yes # stop background upgradesprobe doctor # versions, and the LAST UPDATE ATTEMPT
probe doctor’s last line matters more than the version numbers: a detached auto-updater that has been failing silently is otherwise invisible.
Stops capture and imports, clears local import history, removes the plugins, and signs this device out — the tokens saved here are revoked.To sign out without uninstalling, choose Sign out instead; the plugins stay installed.
probe wizard --action uninstall --yes # remove everythingprobe logout # credentials only; plugins stayprobe wizard --no-capture --uninstall --yes # drop the capture plugin only
Nothing already sent to your team’s knowledgebase is touched. Uninstalling a client does not delete data.
Credentials in your shell outrank the config file. If PROBE_TOKEN, PROBE_MCP_TOKEN, PROBE_INGEST_TOKEN or PROBE_SERVICE_TOKEN is exported in your environment, signing out clears the file but the CLI still authenticates. The wizard says so when it sees one — it cannot unset a variable in your parent shell.
Assistant
Responses are generated using AI and may contain mistakes.
