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

# Capture pi work

> Capture pi implicit accepts, Attribution, inference calls, and optional edit evidence.

Use this guide to capture pi Developer decisions, commit Attribution,
inference calls, and optional Edit observations on one developer machine.

## Evidence captured

| Evidence                          | Support  | Source or limit                                                                                      |
| --------------------------------- | -------- | ---------------------------------------------------------------------------------------------------- |
| Commit Attribution                | Yes      | The bundled extension marks the Session after edits.                                                 |
| Developer decisions               | Implicit | A successful `edit` or `write` emits one implicit accept. Stock pi has no explicit approval gesture. |
| Inference calls                   | Optional | pi can route an Anthropic-compatible provider through a gateway.                                     |
| Edit observations                 | Optional | The extension extracts successful edits at `session_shutdown`.                                       |
| Rejected edits and Retry linkages | No       | The extractor omits failed edits.                                                                    |
| External line counts              | No       | pi has no pre-edit snapshot hook.                                                                    |

## Before you begin

You need the following:

* Sediment 0.3.0 or later. Earlier releases don't bundle the pi extension.

* Node 24 and pi 0.84.1:

  ```bash theme={"dark"}
  npm install --global @earendil-works/pi-coding-agent@0.84.1
  ```

* A capture login, a git repository, and the other steps in
  [Configure local capture](/capture/local-capture).

Start pi once to create `~/.pi/agent`, sign in to your model, and then close
pi.

## Install capture

1. Connect the CLI to the Sediment endpoint:

   ```bash theme={"dark"}
   sediment login https://sediment-api.example.com --capture
   ```

2. Install capture in the repository. The installer registers the extension in
   `~/.pi/agent/settings.json`:

   ```bash theme={"dark"}
   sediment install --user-id alice /path/to/repo
   ```

   Replace `alice` with your developer identifier.

3. Load the environment, and start pi in the repository:

   ```bash theme={"dark"}
   . "$HOME/.sediment/env.sh"
   cd /path/to/repo
   pi
   ```

If the extension is missing or unregistered, `sediment doctor` reports `FAIL`.
After you move the CLI, rerun the install command with the same flags, and
remove the stale extension path from `~/.pi/agent/settings.json`.

## Configure Edit observations

Edit observations send applied text and observed file text. If participants
approve that, rerun the installer with `--transcripts` and the same other
flags:

```bash theme={"dark"}
sediment install --user-id alice --transcripts /path/to/repo
. "$HOME/.sediment/env.sh"
```

This sets `SEDIMENT_PI_TRANSCRIPTS=1`, and the extension extracts edits at
`session_shutdown`. Any other value disables extraction. A later reinstall keeps
the opt-in. If you manage the environment yourself with `--no-env`, set the
endpoint, token, and `SEDIMENT_PI_TRANSCRIPTS=1` there.

If a one-task host keeps pi running, set `SEDIMENT_EXTRACT_ON_SETTLE=1` so that
extraction runs at `agent_settled`. Leave it unset for interactive Sessions.
Repeated settling keeps the earliest file state, because the first write wins.

Keep transcripts at their original paths. pi resolves relative edits from the
transcript's working directory. The extractor skips an edit with an invalid
directory (`execution_directory_invalid`) or path form (`unsupported_path`).
For a fork, keep the complete parent transcript in the same directory. The
extractor reads one regular parent file of up to 64 MiB, excludes inherited
messages, and counts an unusable parent as `parent_source_unverified`.

## Configure inference-call capture

If your deployment routes pi through a gateway, your operator distributes the
`sediment` provider and its credential, as described in
[Distribute gateway routing](/capture/managed-capture#distribute-gateway-routing).
You don't need a gateway credential. Start pi with the provider:

```bash theme={"dark"}
pi --provider sediment --model '<existing Anthropic model ID>'
```

In a running Session, open `/model` to reload the provider file and select the
model.

## Verify capture

Remote checks need a separate [operator login](/capture/local-capture#verify-capture).

1. Ask pi to create a small file with its `write` tool, and end the Session.

2. Commit the file, and read the commit's Session note:

   ```bash theme={"dark"}
   git notes --ref=refs/notes/sediment show HEAD
   ```

3. Check that Session on the server:

   ```bash theme={"dark"}
   sediment doctor /path/to/repo --agent pi --session-id '<session_id>'
   ```

   If you opted in to Edit observations, add `--transcripts`. For a
   gateway-routed Session, add `--inference-calls`. A model response alone
   doesn't prove capture.

## Limits

* pi accepts are implicit, so reports don't count them as human approvals.
* The extractor omits failed edits and doesn't emit Rejected edits or Retry
  linkages.
* pi can request evidence from a previous Session through a separate retrieval
  token. See
  [Enable agent-requested retrieval](/operate/resume-with-evidence#enable-agent-requested-retrieval).

[Privacy boundaries and ceilings](/capture/how-capture-works#privacy-boundaries-and-ceilings)
lists the fields that each capture path sends.