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
Full transcript, not a summary. The resumed session keeps everything, including dead ends, so the next agent sees what was tried and rejected.
Opt-in capture, self-hostable sync server. Teams can keep transcripts inside their own infrastructure.
Harness-neutral format. The value is moving work between tools, so the thread representation must map across harnesses that model tools and context differently.
Why it matters
The work behind a coding task is increasingly the agent transcript, not just the diff. Losing it when you switch machines forces the next session to rediscover context.
Cross-harness resume lets you pick the best agent per stage without paying a re-explanation tax.
Shell history plus agent threads behind one MCP gives agents a searchable memory of how the environment was actually operated.
Risks and failure modes
Transcripts contain secrets, file contents and customer data. Encryption in transit is not enough; decide retention and who can read synced threads.
Replaying a full transcript into a new harness can exceed its context window or confuse it with tool calls it does not support; check how resume compacts or translates.
An MCP that exposes full history widens what a prompt-injected agent can read.
Review checklist
Is capture opt-in per repo or project, with secrets redacted?
Where does the sync server run, and what is the retention policy?
What does resume do when the target harness lacks a tool used in the thread?
Which agents may query history through the MCP server?
Related entries
R084 (memory for always-on agents), R035 (durable waits), R083 (agent memory patterns), R002.