Skip to main content
Three rows in three groups. Space toggles a row, → on the Set settings › band saves, and so does leaving with ← or Esc after a change.
Tracking, session capture and the rules block have no row here. Probe is installed whole by Install Probe and removed whole by Uninstall Probe, because a row per part is how devices ended up with half of it. To change one part on its own, use the flags: probe wizard --no-capture --yes, or --agent codex --no-capture for one agent. See Unattended use.

​
What Probe does here

Updates the CLI and plugins at session start.Off means you update deliberately, with npx probe-research and Update Probe. probe doctor still grades your versions either way.
Your agent plans with you before writing research code.A line in the managed rules block that runs the /plan-research-review skill before your agent writes code for ML research: it maps the plan to the code that already exists and asks you about every gap. On by default.
Images you paste into a prompt upload with the session, unscanned.A screenshot that shows a credential is uploaded with it. On by default; untick it to keep pasted images on this device. See Session capture.

​
Defaults

The two rows that set what happens in every session sit at the top of the main menu, under Defaults, so their current values show every time the wizard opens.

​
Who records

Your agents, or the Probe daemon: who records your coding agents’ work in Probe, and who searches the team’s work for them. ← / → on the row switches it for every coding agent on this device. See The Probe daemon.
While the daemon records, Enter on the row opens its own page, with one setting: Daemon sees the agent’s reasoning. Claude Code and Codex then write reasoning summaries for the daemon; they also show in your terminal and upload with the session. It applies to new sessions.

​
Probe in new sessions

It sets what the switch starts at when a new coding-agent session opens. Its three states are three different disclosures:
New sessions read and write Probe.Reads and writes. The agent records work as it happens (or the Probe daemon does, where it records).
A single conversation can always override the default with /probe on, /probe read or /probe off, or from a shell:

​
From a script

Every capability is a flag, and omitting one preserves what is already configured:
See Unattended use.