Skip to main content
That is the whole surface. The wizard knows what is installed on this machine, which credentials resolve, whether the last update worked and what imports are running — so instead of describing what you should do, it does it.
If you already have the CLI, probe wizard is the same thing. npx exists so the first run needs nothing installed.

​
Two doors

install is the launcher’s word for wizard --action configure — the same flow, not a second implementation of it.

​
Everything the wizard does, and its command

Every screen has a scriptable equivalent. Prefer the wizard at a keyboard — it shows you the state before you change it, and it can tell you when a change did not take. Prefer the command in a script.
Two things have no wizard screen, deliberately. Minting a token (probe token create) requires a human in a browser and prints a secret you must copy. Workspace write permissions (probe access-group, probe workspace writers) are a team-admin surface, not a device one. The Claude Code status line comes with Install and goes with Uninstall.

​
On this device

Every screen of the menu sits under a live summary of the machine. It is the reason the menu is short: you choose against real state rather than guessing which action you need.
Three parts of that are worth calling out:
  • Versions are graded per component. CLI, SDK, plugin and tap update on their own cadences, and a machine is routinely current on one and months behind on another. The verdict shown here is the same one probe doctor prints.
  • Last update attempt is the only way to notice a detached auto-updater that has been failing silently.
  • Import progress is live. Background imports keep running while you use the menu, and you can leave the wizard without stopping them.
The Capy row reads its capture connection: whether capture is on, how many Capy projects it covers, and when it last synced. Its MCP comes from the Probe plugin in Capy’s own settings, which this machine cannot see.

​
The main menu

The menu shows every group but the one under the cursor collapsed to its heading.
Who records — your agents, or the Probe daemon. ← / → switches it for every coding agent on this device. While the daemon records, Enter opens the daemon’s own settings.Probe in new sessions — on, read or off for new sessions.These lead the menu because their current values are worth seeing every time it opens. See Settings.
Install Probe — set up tracking, capture and updates.Update Probe — upgrade the CLI and the plugins.Uninstall Probe — remove plugins, stop capture, sign out.See Install.
Import research work — past sessions, a project folder, or both.Existing imports — check, resume or cancel imports.See Import research work and Existing imports.
Settings — automatic updates, research plan review, and uploading the images you paste.See Settings.
Diagnose a problem — check setup, sign-in and updates.See Diagnose and repair.
Exit — leave the wizard. Imports keep running.Sign out — stop capture and imports, then sign out. It asks first.Sign-in happens before the menu opens, so it is not a row here. Switching between accounts saved on this device is reachable with --action account. See Accounts.

​
Getting around

The wizard is a terminal UI, and the keys are the same on every screen. Screens that step forward also carry a ‹ Back / Next › band at the bottom, so the navigation is visible and not only a keybinding. The folder picker adds Ctrl+L to type a path directly, Ctrl+N to continue with the current folder and Ctrl+B to go back.

​
The flags are the contract

Every capability the menu offers is also a flag, and the menu is a front end over the flags — not the other way round. That has one consequence worth relying on:
An omitted flag preserves whatever is already configured. probe wizard --yes in CI can never silently revoke someone’s capture pairing, because it only changes what you named.
See Unattended use for the full list.