> ## Documentation Index
> Fetch the complete documentation index at: https://docs.prbe.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Settings

> Automatic updates, research plan review and pasted images, and what a new session does by default.

```bash theme={null}
npx probe-research            # → Settings
probe wizard --action settings
```

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.

> [!NOTE]
>
> **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](/wizard/flags.md).

## What Probe does here

> **Automatic updates**
>
> *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.

> **Research plan review**
>
> *Your agent plans with you before writing research code.*
>
> A line in the managed rules block that runs the [`/plan-research-review`](/agents/skills) 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.

> **Upload images you paste**
>
> *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](/agents/capture.md).

## 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](/agents/daemon.md).

```bash theme={null}
probe wizard --who-records daemon --yes
probe wizard --who-records agent --yes
```

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](/agents/overview.md#the-switch) starts at when a new coding-agent session opens. Its three states are three different disclosures:

**on**

New sessions read and write Probe.

Reads and writes. The agent records work as it happens (or the Probe daemon does, where it records).

**read**

Write commands are blocked; search still works.

The read surface stays live, so the agent keeps its memory of the lab — it just stops adding to it.

**off**

No Probe calls at all, so no search either.

This is the state to choose deliberately, not by accident. An agent with no reads does not know what it is not seeing.

```bash theme={null}
npx probe-research            # → Defaults → Probe in new sessions
probe wizard --action defaults
```

A single conversation can always override the default with `/probe on`, `/probe read` or `/probe off`, or from a shell:

```bash theme={null}
probe session state read       # this conversation only
probe session default on       # the device-wide default
probe session status           # what this conversation is doing, and how that was decided
```

## From a script

Every capability is a flag, and omitting one preserves what is already configured:

```bash theme={null}
probe wizard --no-capture --yes                    # capture off, everything else untouched
probe wizard --tracking --agent-rules --yes        # ensure both on
probe wizard --no-auto-update --yes                # stop background upgrades
```

See [Unattended use](/wizard/flags.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.