Atuin 18.24 adds Threads to search and resume agent sessions across machines

The team behind Atuin, the shell-history tool, has announced Atuin Threads. Starting with Atuin 18.24, you can search your agent sessions across machines, resume them anywhere, or fork a session into a different agent harness. The post's example: start something in Claude Code on a dev server, then finish it in Codex on your laptop.

The post is written in first person by the person who started Atuin, and its argument is that terminal use has changed. For years the author was the only user of their shell. Now, they say, more than half the commands running on their machines were not written by them. Much of the work happens through a coding agent, but while shell history follows the author everywhere, agent sessions do not. They are scattered across a laptop, a dev server, ephemeral instances on exe.dev and a bare metal box in Germany, hard to search and often forgotten.

The author draws a parallel with why Atuin exists: commands typed into a shell used to vanish on line 501 of .bash_history, and once that history was indexed and easy to recall, they could find a command used years ago in seconds. Shell history records what happened but not the reasoning or intent behind it. Agent sessions keep all of it: every command, its output, the author's intent and everything tried on the way to the solution, in plain English in the home directory. Threads is meant to put that data to work.

Technically, the post calls Threads a natural extension of Atuin. The existing encrypted sync engine is generic and can sync anything that can be modelled as an append-only log, and the author says most AI sessions are exactly that. Like shell history, Threads is end-to-end encrypted when synced, so the team says it cannot read sessions. You can use the hosted sync server, run your own, or keep everything local. Capturing agent sessions is opt-in. Sync also keeps the history backed up.

Supported agents at launch are Claude Code, Codex, Pi, Omp and OpenCode, with more coming soon. You run atuin resume and, after setup, get a terminal interface listing the sessions. There is also an MCP server, atuin mcp, which lets agents search and reference earlier sessions themselves: find past work, understand why a decision was made, and build on earlier investigations without digging up context. It installs with atuin mcp install claude/codex/pi/opencode.

The author gives three examples. First, work that never shipped: after iterating on onboarding and setup many times over several months, they now ask an agent to work on onboarding and it finds the earlier attempts, why they were abandoned and what could be better, including code that never reached main, so no giant spec is needed. Second, an object store outage: the team rolled its keys as a precaution after security issues in the industry, and one new object store key lacked the right permissions for avatar uploads. A daily Sentry triage agent noticed and traced the failure to a command run earlier that day. The author had not yet read it, but prompting another agent with 'seeing some tigris avatar issues?' led it to find the previous investigation, name the cause and develop the fix much faster than starting from scratch. Third, forking across machines: while testing before release, one machine performed badly, and the investigating agent suspected poor IO but needed a faster disk to confirm. The author forked the session onto a MacBook, where it continued from exactly where it left off. With the faster SSD, the investigation concluded slow disk was only part of the story and imports could be sped up elsewhere too. The original thread then pulled the benchmark results from the Mac and built a fix, with no copy-pasting or manual coordination.

Looking ahead, the team is building opt-in session sharing, so an agent thread could be handed off like a Git branch, and it asks teams using agents daily to get in touch. To try Threads: install or update Atuin with the setup script from setup.atuin.sh, run atuin resume, and optionally run atuin mcp install.

Key facts

Atuin Threads ships in Atuin 18.24 and later: search agent sessions across machines, resume them anywhere, or fork one into a different agent harness.
Five agents are supported now: Claude Code, Codex, Pi, Omp and OpenCode, with more said to be coming soon.
Threads reuses Atuin's sync engine for append-only logs; it is end-to-end encrypted when synced, can use the hosted server, a self-hosted one or stay local, and capture is opt-in.
An MCP server (atuin mcp) lets agents search past sessions themselves; install with atuin mcp install claude/codex/pi/opencode.
Opt-in session sharing for teams is being built but is not released.

Why it matters

Agent sessions hold the commands, output and reasoning behind work, but they sit in separate tools and on separate machines. Atuin's pitch is to treat them like shell history: one searchable, synced record. The practical gain the post describes is continuity. A session can move between machines and between agents, and later agents can read earlier investigations instead of starting cold. Atuin already did this for commands; Threads extends it to agent work.

Who it affects

Developers who run coding agents on several machines, such as a laptop, a dev server or cloud instances, and want to find or continue past sessions. Users of Claude Code, Codex, Pi, Omp or OpenCode are covered now. Teams are a future audience: the authors are building opt-in session sharing and are asking teams that use agents daily to get in touch.

How to use it

Install or update Atuin with the setup script from setup.atuin.sh (curl piped to sh, as given in the post), making sure you are on 18.24 or later. Run atuin resume and follow the setup to get the session interface. To let agents search earlier sessions, run atuin mcp install claude, codex, pi or opencode. Syncing can use Atuin's hosted server, your own server, or stay local. Capturing agent sessions is opt-in. No pricing is stated for the hosted sync server.

How solid is it

This is a first-party launch post by the Atuin team, and the feature is released in 18.24+. The evidence is the author's own anecdotes: the onboarding iterations, the avatar upload outage and the fork onto a MacBook. No user numbers, benchmarks or performance figures for Threads are given. The 'more than half' figure for commands not written by the author is their own impression of their machines, not a measured study.

Risks and caveats

Sessions contain commands, outputs and intent, so what gets captured matters; the post says capture is opt-in and sync is end-to-end encrypted, but it does not specify which encryption scheme is used. Only five agents are supported now, and the source does not say which are 'coming soon'. Team session sharing has no release date or timescale. The post's examples show faster debugging in the author's workflow, not a measured improvement.

“the history of your work should be useful, accessible, and yours to keep.”

— Atuin Threads announcement, blog.atuin.sh