Atuin, the open-source shell history tool, wants to do for AI coding agents what it did for terminal commands: keep every session, sync it across machines, and make it searchable. The feature is called Atuin Threads. It launched on the Atuin blog on October 27, for Atuin 18.24 and later, but it reached a much bigger audience on November 11, when the post hit the Hacker News front page.
As of 1:20 AM PT on November 12, the Hacker News thread had 216 points and 79 comments, and the Atuin GitHub repo had 32,316 stars. The reaction split three ways: longtime Atuin users who wanted it, security-minded developers who did not want their agent transcripts on any server, and a large group who said they had already built something similar for themselves.
What Atuin Threads does
Coding agents such as Claude Code and Codex save each session as a log file on the machine where it ran. Those logs hold the prompts, the commands, the output and the reasoning behind a change. They tend to stay on one laptop or one server, and they get forgotten.
In the launch post, Atuin creator Ellie Huxtable says Threads lets you "search your agent sessions across machines, resume them anywhere, or fork the session into a different agent harness." Huxtable's example: "Start something in Claude Code on a dev server, then finish it in Codex on your laptop."
The key facts from the post:
- It ships in Atuin 18.24 and later. You run
atuin resumeto start. - Supported agents at launch: Claude Code, Codex, Pi, Omp and OpenCode. A later 18.24.4 post from Huxtable on X added Copilot CLI.
- Sync is end-to-end encrypted. You can use Atuin's hosted server, run your own, or keep everything local. Capture is opt-in.
- An MCP server (
atuin mcp) lets agents search earlier sessions themselves. - Session sharing for teams is in development.
The praise: fans of Atuin already wanted this
Many of the first comments came from people who already use Atuin every day. User RyJones wrote that Atuin is "a required bit of infrastructure" for them. timothyduong said: "Atuin is so invaluable to me, I self host an atuin server but even client only is amazing."
The most concrete success story came from X. Nikola Milojević (@nklmilojevic) wrote that a deleted git worktree held uncommitted changes made by Claude and Codex. Then: "I just asked the agent to look into atuin mcp and threads and it was able to fully reconstruct and reapply changes." HN user nklmilojevic linked the same post in the thread.
On X, Huxtable's post about a Threads mod for the herdr desktop app had 230 likes and about 15,600 views at about 1:20 AM PT. A shorter one drew a laugh: "after a month of using atuin threads, claude now says 'I'll do xyz, as I usually do'". Pranjal Gupta (@gupta_pranjal) framed the use case most people recognize: "Claude Code hits its limit halfway through a task. You open Codex and explain everything again."
User amelius asked whether sessions get deleted after a while. The account ellieh, which lists ellie@atuin.sh as a contact elsewhere in the thread, replied: "claude deletes them after 30 days, but Atuin Threads keeps them synced and searchable forever." That 30-day figure is the account's claim; we did not check it against Anthropic's docs.
The worry: agent transcripts are full of secrets
The sharpest pushback was about security. petesergeant described months of work isolating agents from each other, including "aggressive sandboxing, regular scanning of transcripts for agent-leaked credentials" and separate machines. The verdict: "Needless to say, as much as I have found atuin an excellent manager of my command-line history, I will be avoiding this."
Further down that thread, after ahmedketata noted that Claude Code can save secrets in a local settings file, jothimani extended the point to agent config files: "I now treat the agent config files as something to protect from the agent itself, not only from other people."
orbis-tertius said: "I love Atuin, but have some reservations about a shared server keeping all my shell history and agent sessions." Other users pointed out the answer was in the post. aaronax replied: "It is encrypted client side. Or you can run your own server." dietr1ch was not fully sold on self-hosting, writing that the sync server is "centralized, which is annoying unless you can trust A machine you own to be up and reachable by all others all of the time."
NelsonMinar asked a harder question: "It's not clear which parts of Claude state are safe to sync and which you want to keep local to one machine." Atuin engineer suis_siva answered plainly: "Atuin doesn't attempt anything special in terms of deciding what to sync. Pretty much everything is synced." The same reply says sessions are end-to-end encrypted. So if a secret lands in a transcript, it syncs with the rest, encrypted.
"I just built this myself"
The thread's running joke was how many commenters had written their own version. ashenke put it best: "I love this new AI era of coding where the HN submission is about a new way to manage agent, and almost literally all the comments are 'I just finished implementing this myself.' It's almost like a parody."
They were not exaggerating. Commenters linked or described their own session tools: kristopolous's ctools resumes a session from another machine over SSH, all2 shared a BM25 "memory everywhere" module, ghempton linked codealong, and baalimago described a shared "living document" that agents write summaries into. talloaktrees said a homemade search tool was worth the time: "It's so useful to be able to say 'search sessions for the time I was working on XYZ 3 months ago'".
tacker2000 was less impressed by the trend: "So now everyone and their mother are putting out AI harnesses/session managers aka browser tabs for AI." ellieh pushed back that Threads "stores every turn for every harness you use, syncs it across machines, and makes it searchable and resumable anywhere. it's not a replacement for your harness, or your harness wrapper." 0cf8612b2e1e offered the classic HN line that "you could get an 80% solution to this problem with rsync and a hundred lines of python."
Cost, speed and an old bug fixed in a day
GNOMES asked whether Threads would burn tokens. forsalebypwner said: "I don't think this, by default, has any effect on anybody's token usage." Asked about electricity, ellieh said it is "actually super low on compute, doesn't use tokens, mostly just needs storage."
languagehacker complained about lag in plain shell history: "Pressing up or ctrl+r has this lag which throws off my typing." ellieh suggested turning on the Atuin daemon, which the reply says is "the default on new installs."
The most practical exchange: hugmynutus said Atuin broke their shell when a drive failure left /home read-only, and that the "Issue has been sitting open for almost a year." suis_siva replied "Will fix," linked a pull request, and GitHub shows that fix merged at about 5:19 PM PT on November 11. Issue 2999 now shows as closed.
One gap people asked about: tristanMatthias wanted to sync Claude Code web sessions. ellieh replied "not yet but we're definitely interested in figuring out how to make that happen."
Why it matters
Agent session logs are becoming the real record of how software gets built: the prompts, the dead ends and the reasons. Threads is a bet that this record should be kept and searched like shell history. The HN reaction shows the trade-off clearly. The convenience is real, and the people who tried it liked it. But a full transcript of an agent's work can hold API keys and private code, and Atuin syncs all of it. Encryption and self-hosting answer part of that worry, not all of it.
For other agent tooling reactions, see what people said about the AWS emulator written by AI agents and Anthropic's advice on Claude Code auto mode and deny rules. For another open-source tool that HN weighed this week, see the Yogurt meeting notes reactions.
Sources
- Atuin Threads: All your agent sessions on every machine (Atuin blog, Oct 27, 2026)
- Hacker News discussion, item 50453637
- Atuin on GitHub
- Atuin pull request 4711, read-only storage fix
- herdr mod for Atuin Threads
- @elliehuxtable on X: herdr mod
- @elliehuxtable on X: 18.24.4 release
- @elliehuxtable on X: "as I usually do"
- @nklmilojevic on X
- @gupta_pranjal on X
