Control what Crosshead saves

Choose which repositories and tools to connect, how much they capture, and whether to keep automatic memory on.

On this page

Understand what leaves your machine

The daemon can save recent checkpoints locally while offline and sync them when the service is reachable. “Saved locally” can mean there is still an upload pending. Your agent’s private key stays in the local runtime secret store. Crosshead uses it to sign authentication requests and working memory. Other machines can sync only after being configured with the matching identity and profile.

Check and change source excerpt capture

In new Claude Code and Codex workspace setup, --source-excerpts off is the default. Run crosshead workspace check --json and look at sourceExcerpts for the selected host’s binding. Some older registrations capture excerpts by default. For a legacy host launched from a shell, set CROSSHEAD_CAPTURE_SOURCE_EVIDENCE=0 before starting it.

To change a scoped project’s setting, rerun guided setup in the project for the intended host and profile, select your excerpt preference, and check the preview before applying. Restart the host and confirm with workspace check. If you use all-project scope, review the all-project binding because its excerpt preference applies to all directories it covers.

Excerpts can help preserve exact rules the agent read. Turn them off when you want to limit retained source text. Prompts, summaries, and explicit saves may still contain code or sensitive details with excerpts disabled.

Pause automatic memory

To stop automatic memory for a profile, choose off. This affects every project using that profile. To restore typical automatic use, switch back to assist.

crosshead memory mode off --profile default

For a single project under project scope, remove its hooks using crosshead workspace remove --workspace-root <path>. Add --adapter codex or --adapter claude-code to remove just that host. To turn off Claude Code and Codex automatic hooks across an all-project configuration, select manual scope in crosshead quickstart.

Use workspace check and restart the affected sessions to verify the change. Existing memory stays stored until you clear it or request deletion.

Memory modes

assist
The default for automatic workspace setup. Saves recent working state and makes it available to later sessions. Transcript archiving in this mode requires explicit approval.
manual
Skips ordinary automatic checkpoint writes. Use manual workspace scope as well if you want a command-only setup with no Claude Code or Codex hooks.
off
Disables automatic retrieval and capture for the profile.
auto
Keeps automatic memory and can batch transcripts for paid archiving. This is separate from the runtime’s automatic update setting.

Export or delete stored memory

crosshead memory export --profile <name> requests an export. This is a paid operation. Store the result somewhere private.

To clear a specific hot-memory scope, run crosshead memory sync --profile <name> to find the exact scope, then run crosshead memory hot reset --scope <scope> --profile <name> for that scope. The local view clears immediately. Other devices can still have an offline copy until they reconnect and learn about the reset.

For full hosted private-memory deletion, follow the instructions under data controls and deletion. A hosted request uses your public npub and a signed confirmation. Keep your identity available until the request is complete.

For processing details and subprocessors, see the privacy policy. If you are using your own service, confirm the policies for the API origin you configured.