Atuin Threads Resumes a Claude Code Session in Codex on Another Machine; Atuin's Agents Page Still Says It Is Unbuilt

Atuin 18.24.0, released on 15 October, lets a developer start a task in Claude Code and resume it in Codex on another machine. The feature is called Threads, and Ellie Huxtable, who says she started working on Atuin, described it in a post dated 27 October.

The post says Threads stores, searches and syncs agent sessions, and that a session can be resumed elsewhere or forked into a different agent. It names Claude Code, Codex, Pi, Omp and OpenCode as supported, with more "coming soon." Updating is one command, curl --proto '=https' --tlsv1.2 -LsSf https://setup.atuin.sh | sh, and atuin resume opens the session picker.

What the releases added after the post

The GitHub release notes show the list has already grown. Version 18.24.0 renamed AI sessions to threads, added atuin threads, a threads.db file, tool-call capture and capture of edit diffs. It also added atuin ai resume, with atuin resume as the shorter alias, and atuin mcp install <agent> plus MCP tools to list, read and search sessions.

Release	Date	Added
18.24.0	15 Oct	Threads, resume, MCP tools
18.24.1	16 Oct	omp thread support
18.24.3	29 Oct	Windows MSI installer
18.24.4	30 Oct	GitHub Copilot CLI capture, search, resume
18.24.5	4 Nov	Grok Build, Kiro CLI, Amp capture
18.24.6	10 Nov	Claude Code shell-edit diff fix

One release carries a warning. The notes for 18.24.2, dated 22 October, say its Docker container ships stale ca-certificates with known vulnerable certificates, and tell users to pull tag 18.24.2-1 instead.

Privacy: what the post claims

Huxtable's post says Threads is end-to-end encrypted when synced, and that Atuin cannot read the sessions. Capture is opt-in. Users can sync through the hosted server, run their own, or keep everything local. This piece did not test any of that; the encryption claim is the author's, and the sync server's code is the thing to read before trusting it with transcripts that often contain file contents and tokens pasted into prompts.

The MCP server is the other half. atuin mcp install claude, codex, pi or opencode lets an agent search earlier sessions, and the post gives two examples: finding an abandoned onboarding attempt and tracing a storage permissions issue back to an earlier investigation.

The page that disagrees

Atuin's own agents page, atuin.sh/atuin-for-agents, was fetched the same day as the release notes. It says only the commands agents run are recorded and synced, and: "Syncing complete agent sessions across machines is in development." It lists hooks for Claude Code, Codex, OpenCode and pi, and does not mention Threads.

That page describes a narrower, older product: shell history tagged by which agent ran each command, hidden from ctrl-r by default and filterable with --author. Both products sync encrypted. A reader who finds the agents page first would conclude the feature the 18.24.0 notes describe does not exist.

How it compares with SpecStory

SpecStory's documentation describes the same idea. specstory resume shows every captured session for a project across agents, reconstructs the conversation in the target agent's native format, and launches it. Cross-machine resume "requires SpecStory Cloud and a Pro plan", while same-machine resume works for everyone.

Atuin's post names no price, and says a hosted sync server, a self-hosted one and local-only use are all options. Whether the hosted server stays free is not said anywhere in the post. Team sharing, which the post describes as opt-in and in development, is not released.

For related coverage of how developers are packaging agent behaviour, see Matt Pocock's skills repo against Anthropic's and Claude's enterprise defaults. The next release to watch is 18.25.0, which has a beta dated 3 November and no published notes.