Atuin Threads lets you start a Claude Code session on one machine and finish it in Codex on another
Atuin Threads: All your agent sessions on every machine
Atuin 18.24 adds Threads, a synced, end-to-end encrypted history of your coding agent sessions across every machine. Start a task in Claude Code on a dev server, then resume it in Codex on your laptop with full context intact. Sessions are captured opt-in, searchable, and forkable across agent harnesses; an MCP server lets agents search past sessions themselves. Supported agents include Claude Code, Codex, Pi, Omp, and OpenCode.
Shell history has always been an excellent record of what happened, but it's only the surface. It never kept the reasoning… or the intentions behind what I was trying to do.
- baalimago
I suspect this is one of those problems "everyone" has built their own solution for. Including me!
I built slivingdoc[0] with an alternative approach: instead of syncing exact sessions (which are often quite noisy, and not so useful), the agents gets a living document with automatic merge conflict resolution backed by s3 ("infinite" storage). Idea being that the agents are prompted to summarize their context into slivingdoc as normal utf-8 files. So this way only you only need to add the stdio MCP server to all your harnesses which supports it and it just works!
Some harnesses are _super_ hyped about this concept. Codex needs no prompting at all to start communicating. I got the idea from enabling agentic forums via all the openAI hacks.
[0]: slivingdoc.dev
- nzoschke
I started building my own version of this in Superlogical Rex.
It's a bit hard to decide where to hook in.
Rex has events, harnesses have hooks, terminal output can set program status, git has hooks.
I'm not sure I actually want every session from every machine saved. That's a lot of noise especially when half of coding sessions are experimental / throwaway.
But at the same time its not that much data that's easy to ripgrep / LLM through.
- hugmynutus
Really enjoyed Atuin for a few weeks, until I realized it doesn't have correct `EFSRO` (Error: Read-Only File System) handling. So when my `/home` mount had a raid array drive failure it broke my local shell. Issue has been sitting open for almost a year. Pretty disappointing.
- thesurlydev
I've a love affair with Atuin but this may turn into a full blown obsession
- talloaktrees
I've built this for myself, but not across multiple machines.
It scans the session logs of all coding harnesses I use, one extra thing it does is create embeddings to allow hybrid BM25/semantic search.
I think these kinds of tools are on of the few times I've spent time "using AI to work on my AI tools" that was actually a good use of time.
It's so useful to be able to say "search sessions for the time I was working on XYZ 3 months ago"