Technology1 min read

Atuin Threads: All your agent sessions on every machine

By · Published by Everything Blog

In short

Starting in version 18.24, the platform introduces session indexing to help programmers navigate past AI interactions across multiple machines. Developers can fork or resume tasks between supported tools, including Claude Code, Codex, Pi, Omp, and OpenCode. Furthermore, integration with the Model Context Protocol allows agents to reference previous technical decisions directly through an automated command interface. Users maintain complete privacy governance with flexible hosting alternatives tailored to their infrastructure needs.

Key points

  • Users retain control over their session history through options for hosted sync, self-hos…: Users retain control over their session history through options for hosted sync, self-hosting, or local-only storage.
  • The feature captures abandoned iterations and plain-English intents that are typically lo…: The feature captures abandoned iterations and plain-English intents that are typically lost during coding sessions.
  • AI agents can build upon prior technical decisions without requiring engineers to supply…: AI agents can build upon prior technical decisions without requiring engineers to supply extensive background documentation manually.

Sources checked by our analysis pipeline: 1

Atuin Threads: one searchable, synced history for every agent session, on every machine Start a task in Claude Code, then resume it in Codex

Atuin Threads: one searchable, synced history for every agent session, on every machine

Start a task in Claude Code, then resume it in Codex on another machine — with all context intact. Install, then runatuin resume

Over the past year or two, how I use my terminal has changed dramatically. For years I was the sole user of my shell, and everything in my Atuin history was authored by me. Now, more than half the commands running on my machines weren’t written by me.

These days, much of my work happens through a coding agent, typed into a little “Topsy-turvying” text box. But while my shell history follows me everywhere, my agent sessions do not. They're scattered across different tools and machines (a laptop, a dev server, ephemeral instances on exe.dev, a surprisingly cheap bare metal box in Germany), difficult to search, and often forgotten once I've moved on.

It’s a familiar problem!

I started working…

Technology