R090 · Infrastructure for agents at scale › Agent session hosting and control planes

Atuin Threads: move an agent session between machines and harnesses

Read the original

agent-memorysession-portabilitydevtoolsagent-harness

Source: atuinsh/atuin README (MIT). Surfaced by André Lindenberg.

What it is

Atuin started as an encrypted, syncable shell-history tool. It now also captures coding-agent sessions. Threads records the sessions of agents such as Claude Code, Codex, Pi, OpenCode and Omp, syncs them across machines with end-to-end encryption, and lets atuin resume pick a session up on another machine, even in a different harness (for example, start in Claude Code on a laptop, resume in Codex over SSH on a dev server). A built-in MCP server lets an agent search your shell history and past threads.

Design points

Why it matters

Risks and failure modes

Review checklist

  1. Is capture opt-in per repo or project, with secrets redacted?

  2. Where does the sync server run, and what is the retention policy?

  3. What does resume do when the target harness lacks a tool used in the thread?

  4. Which agents may query history through the MCP server?

R084 (memory for always-on agents), R035 (durable waits), R083 (agent memory patterns), R002.

Connections

See R090 on the knowledge map

Part of the Research notes on nowucca.com. Figures and claims are the source's own unless the summary says otherwise.