Source: blog.atuin.sh/threads-agent-sessions
Atuin Threads records agent sessions, including commands, their output, the user's intent and the attempts made along the way, and makes them searchable across machines. Users can resume a session anywhere or fork it into a different agent harness, such as starting in Claude Code on a dev server and finishing in Codex on a laptop. Capturing sessions is opt-in.
Threads uses Atuin's existing sync engine, which is end-to-end encrypted, so Atuin says it cannot read the sessions. Users can sync through the hosted server, run their own, or keep everything local. Atuin says more agents are coming.
Agents can also reach the history through MCP. The MCP server is available as atuin mcp and can be installed for Claude, Codex, Pi or OpenCode with atuin mcp install. Atuin is also building opt-in session sharing for teams.
Why it matters if you build agents
Agents built on Atuin's MCP server can look up earlier sessions to find past decisions, abandoned attempts and prior investigations instead of starting from scratch. Developers who run agents on several machines can move a session between them without copy-pasting context. Anyone storing agent transcripts should check the opt-in and encryption settings before enabling capture.
Get stories like this every weekday
One short email with the day's agent tooling news.