Atuin Threads: one searchable, synced former for all delegate session, on all machineStart a project in Claude Code, afterward resume it in Codex on another device — alongside all environment intact. Install, afterward run atuin resume
0:00
/0:13
Over the former twelvemonth or two, how I use my terminal has changed dramatically. For years I was the sole person of my shell, and everything in my Atuin former was authored by me. Now, additional than fractional the commands operating on my machines weren’t written by me.
These days, much of my activity happens through a coding agent, typed into a small “Topsy-turvying” content box. But during my casing former follows me everywhere, my delegate sessions do not. They're scattered throughout distinct tools and machines (a laptop, a dev server, ephemeral instances on exe.dev, a amazingly cheap naked metal element box in Germany), difficult to search, and frequently forgotten formerly I've moved on.
It’s a acquainted problem!
I started operating on Atuin since the former of my activity was ephemeral: all command I typed was destined to disappear on row 501 of .bash_history. But formerly this activity became indexed, everlasting, and uncomplicated to recall, I could discover the exact command I’d used to fix item years ago, in seconds.
Over the years, this data compounded. It became the former of all of my work, the document of how I solved problems and built things.
Shell former has continually been an outstanding document of what happened, but it’s lone the surface. It never kept the reasoning… or the intentions rearward what I was trying to do. I could lone discover a command if I remembered a part of it, although frequently I remembered what I was trying to accomplish additional readily.
Agent sessions shop the lot of it. Every command, its output, my intent, and everything I tried alongside the way to the eventual solution. It’s all there, in plain English, in my residence directory! But fair as alongside casing former all those years ago, we don’t put it to work.
Atuin Threads
That is why we built Atuin Threads.
Starting alongside Atuin 18.24, you can hunt your delegate sessions throughout machines, resume them anywhere, or fork the meeting into a distinct delegate harness. Start item in Claude Code on a dev server, afterward complete it in Codex on your laptop.
Behind the scenes, this was a natural expansion of Atuin. We put a lot of period and attempt into construction a reliable, encrypted sync engine. It’s generic, and can sync item that can be modelled as an append-only log. As it turns out, most AI sessions are exactly this.
Like casing history, Threads is end-to-end encrypted whenever synced, so we can't peruse your sessions. You can use our hosted sync server, run your own, or keep everything local. Capturing delegate sessions is opt-in, too.
Run atuin resume, and following environment up, you volition see the TUI from the top of this post!
It doesn’t matter which delegate you started alongside - you can resume it anywhere. With Atuin’s sync, this plant throughout devices, and keeps your former backed up forever.
Right now, we support
- Claude Code
- Codex
- Pi
- Omp
- OpenCode
with additional agents coming soon.
MCP
With MCP, agents can hunt and citation former sessions themselves. They can discover activity you’ve done before, comprehend why a decision was made, and build on former investigations without having to dig up the context.
Our MCP is accessible as atuin mcp, and can be automatically installed with
atuin mcp instal claude/codex/pi/opencode
There are all sorts of ways to put this former to work. A few examples:
Work that never shipped
I’ve iterated on our onboarding and setup so many times complete the former few months, but never fairly been blessed alongside it. When I ask an delegate to activity on onboarding now, it finds all my former attempts, as fine as why they had been abandoned and what can be done better.
These sessions merge the code that never made it into main, as fine as my first prompts and iteration. Subsequent agents can use this to fig out exactly what I want, without me having to compose up a elephantine spec.
Object shop outage
With all the safety issues going on in the industry recently, we rolled our keys as a precaution. One of the new entity shop keys did not have the accurate permissions for avatar uploads! We didn’t notice direct distant 😬
My regular Sentry triage delegate picked up on it, and traced the nonaccomplishment downward to a command run before that day. I hadn’t gotten about to study it yet, but prompting another delegate with
seeing several tigris avatar issues?
led to the delegate discovering the former investigation, highlighting the cause, and evolving the fix much faster than if it had done the entire item from scratch.
Forking threads throughout machines
Before releasing Threads, I did several evaluation on a assortment of machines and setups.
One device did not execute well. The delegate examining projected that this was since of mediocre IO performance, but that it needed item alongside a faster disk to confirm.
I forked the meeting onto my MacBook, and it continued from exactly anywhere it remaining off. With the faster SSD, the inquiry concluded that dilatory disk was lone part of the narrative - we could speed up imports elsewhere, too.
Once the benchmarks were complete, the thread operating on the first device could drag the results from the Mac and build a fix. I didn’t have to copy-paste item or co-ordinate throughout machines, and the data is now part of the document of my work.
Teams
While this is tremendously helpful as a solo engineer, it gets equal additional engaging alongside a team.
So much of what we do never makes it into Git, matter trackers, or documentation. The environment rearward that activity ends up scattered throughout idiosyncratic delegate sessions. What if the remainder of the squad could study from it too? What if we could hand off an delegate thread fair akin a Git branch?
We’re construction opt-in meeting sharing for teams, and would affection to comprehend from folks using agents day to day. If this appears helpful to you, please get in touch!
While agents have radically changed my regular workflow, casing former isn’t going anywhere, and is arguably additional helpful than ever. Threads is an expansion of the identical idea that started Atuin in the archetypal location - the former of your activity have to be useful, accessible, and yours to keep.
Threads is out in Atuin 18.24+
- Install or update Atuin alongside curl --proto '=https' --tlsv1.2 -LsSf https://setup.atuin.sh | sh
- Run atuin resume to get started
- Use the MCP alongside atuin mcp install
Please don’t hesitate to attain out alongside any questions or feedback!
