Space toggles, Enter applies, Esc leaves without changing anything.
The boxes read as the union across this device’s agents: a row is ticked if this device does that thing at all. Applying a change leaves untouched rows exactly as they were.
What Probe does here
CLI + MCP
CLI + MCP
Track runs in your coding agents; search lab history read-only.This is the tracking plugin: the skills that teach your agent the workflow, and the read-only MCP server it searches with. The box answers “is this installed here”, which is what toggling it changes.
A plugin that is installed but signed out is a different problem, and this row will not tell you about it.
probe doctor owns that diagnosis.Session capture to the knowledgebase
Session capture to the knowledgebase
Sends this device’s coding-agent sessions to your team’s search.Off stops the upload immediately and unpairs this device’s capture credential.
Rules in your global instructions
Rules in your global instructions
Prompts your coding agents to search and track research in Probe.A managed block in each selected agent’s global instruction file. Everything outside the block is left alone.
probe agent-rules refresh rewrites the block when it is older than the CLI.Automatic updates
Automatic updates
Upgrades the CLI and plugins in the background at session start.Off means you update deliberately, with
npx probe-research and Update to the latest version. probe doctor still grades your versions either way.Defaults
Probe in new sessions
This row cycles rather than toggles, because its three states are three different disclosures. It sets what the switch starts at when a new coding-agent session opens.- on
- read
- off
Sessions will be tracked through your coding agent.Reads and writes. The agent records work as it happens.
/probe on, /probe read or /probe off, or from a shell: