Why it mattersAn agent chat on your laptop is often where the real decision lives. A synced history lets you find it later. The next agent can read what the last one did.
A developer runs Claude Code on a laptop in the morning and Codex on a desktop that evening. The two chats sit on two different machines. They are in two different formats. The second agent has no idea what the first one tried. Atuin released Threads to close that gap.
Ellie Huxtable and the Atuin team posted the release on 27 October. It surfaced on Hacker News today with 111 points at the time of writing. Atuin is already the shell history tool many developers use to sync their terminal commands across machines. Threads extends the same sync to agent sessions.
What it does
Threads records every session that a supported agent has on your machine. The sessions go into the same encrypted sync store Atuin already uses for shell history. Each session becomes an append-only log. You can search those logs by content. You can resume a session on a second machine. You can also fork a session into a different agent. Start with Claude Code, continue with Codex. That last part is the most unusual piece.
The release supports Claude Code, Codex, Pi, Omp and OpenCode. Atuin says capture is opt-in for each agent. The sync can run on Atuin's own hosted server, on a server you run yourself, or not at all.
The MCP piece
The second half of the release is an MCP server. Point Threads's MCP server at your agent and the agent itself can search past sessions. It can read what a previous attempt did before trying the same work again. That turns the history from a thing you read into a thing the agent reads.
Atuin says this is why the feature exists. A fresh agent that reopens a repository without any memory of last week's work is a common source of churn. An MCP-connected history lets the agent find its own earlier runs without the developer pasting a transcript in.
Where this sits
Atuin is MIT-licensed and the code lives at github.com/atuinsh/atuin. The hosted sync is a paid service. Every feature in Threads also works against a server you run yourself. A team that wants the search and the MCP server with no vendor involved can run the whole stack in-house.
What a developer does on Monday
A developer tries this in three steps. Install Atuin. Turn on capture for the agents they already use. Point the Threads MCP server at the same agents. The first session moves to the sync store on its own. After a few days, the search box shows every agent conversation across every machine. The test is whether the search answers a question you now have to answer by hand. What did I ask the agent to do last Tuesday, and did it finish?
Source
Atuin Threads: all your agent sessions on every machine, Atuin, by Ellie Huxtable.
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.