Capture with Zed

Zed runs Claude Code in its agent panel over ACP — and one field in Zed’s settings file routes it through paper, so every thread you start there is captured to paper console. Prerequisites: paperctl installed and authenticated, with the daemon running, and the Claude agent installed in Zed from its ACP registry.

Point Zed’s agent at the proxy

1. Get your proxy address:

   paperctl status

   The proxy line shows the address — 127.0.0.1:51539 by default. The address is set by daemon configuration and stays the same across restarts, so Zed’s setting survives them.

2. Open Zed’s settings file: cmd-, on macOS, or zed: open settings from the command palette.

3. Find your Claude agent’s entry under agent_servers. A registry-installed agent already has one — keyed by its agent id, claude-acp for the Claude agent.

4. Add an env block to that entry setting ANTHROPIC_BASE_URL to the proxy address with an http:// prefix. Everything else in the entry stays as it was:

   "agent_servers": {
     "claude-acp": {
       "type": "registry",
       "env": {
         "ANTHROPIC_BASE_URL": "http://127.0.0.1:51539"
       }
     }
   }

5. Start a new thread in the agent panel. Sessions appear in paper console from then on. Threads already open when you saved the setting keep the old configuration and are not captured.

Zed’s Claude agent keeps its own sign-in — if it isn’t authenticated yet, run /login inside an agent thread. paperd never holds your Anthropic credential.

Verify the capture

paperctl sessions list

Zed agent sessions show up alongside your other captured runs. Session titles are editable in the console, so give a Zed run a readable name if you want one.

The same approach works for any tool that lets you set ANTHROPIC_BASE_URL: point it at the paperd proxy and its Claude traffic is captured through your organization’s gateway like every other session. Conductor is the same one-variable setup in a different place.

If something’s off

• No sessions appearing: confirm paperctl status shows the daemon running and the proxy address matches what you entered, then start a fresh thread — an open thread keeps the configuration it started with.
• Settings edit rejected: agent_servers is a top-level key in settings.json, a sibling of your other settings rather than nested inside one.
• More cases: CLI troubleshooting.