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.
"Half of coding sessions being throwaway" is exactly why I stopped keeping them per session. Mine hang off a work item, and each item has its own folder with its session logs.
I basically throw them away and also record their summary in a vector DB to be able to find why I did something, if I'm ever curious about it!
Otherwise I'm gonna need a tool to help me manage my sessions :D
I've gone a different route and prefer using the native harnesses (Claude, Codex), but with multiple accounts due to the limits.
In order to easily switch between accounts I've build Switcheroo, which I've been using for the past 2-3 months now. I've decided to open source it: https://github.com/FTCHD/switcheroo
Works with other AI CLIs like Gemini, and other various CLIs like Vercel (if you're managing multiple accounts like me), Netlify, Github etc
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"
I love Atuin, but have some reservations about a shared server keeping all my shell history and agent sessions. Am I being too paranoid and missing out on convenience?
Same, I really wanted to share history, but when I realised I was going to need to send things to a remote server I instead wrote a tiny script to search through backups that are shared across machines by Syncthing.
I just search over $BACKUPS/*/latest/local/share/fish/fish_history with grep and skim
https://github.com/comalice/pi-tools contains a 'memory everywhere' module that makes all sessions BM25 vectors, and surfaces a set of memory tools to enable agents to search. You can add a new machine to the mix by registering a 'spoke'. The app runs on the 'hub'. I want to containerize the core app soon.
You can also change which computer is the hub fairly easily.
Correct me if I am wrong, but I imagine this would hammer one's token usage to read past entries to resemble context across machines/terminals and models?
Yes i too faced the problem, lost valuable content across group of chat and not remembering in which chat it was. Tried searching but couldn't find it. Even asked ai itself does about the content whether it remembered.
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.
Probably a little late to this, because herdr has really eaten this segment. With their new Mac app, I don't see myself going back to atuin for this kind of experience. In fact, I get a little peeved using it on a vanilla terminal.
It’s likely because you can vibe code the bones of one in a few hours.
This week I got Claude to build me a browser-based session manager to keep track of sessions and history of tasks. Works well enough for me and I’ll add features as I need.
I've spent the last couple of months putting a lot of time and energy into isolating my agents from each other: aggressive sandboxing, regular scanning of transcripts for agent-leaked credentials, per-agent encrypted credential stores, even physical (and network) separation of machines with different areas of work on them. Needless to say, as much as I have found atuin an excellent manager of my command-line history, I will be avoiding this.
I've a love affair with Atuin but this may turn into a full blown obsession
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.
Nice! Rex is super cool. We have an Atuin Threads integration for Herdr already, definitely exploring building one for Rex too
We actually don’t use hooks at all at the moment, and instead rely on parsing session files
Agents are definitely super good at searching and finding relevant data amongst noise!
"Half of coding sessions being throwaway" is exactly why I stopped keeping them per session. Mine hang off a work item, and each item has its own folder with its session logs. I basically throw them away and also record their summary in a vector DB to be able to find why I did something, if I'm ever curious about it! Otherwise I'm gonna need a tool to help me manage my sessions :D
I've gone a different route and prefer using the native harnesses (Claude, Codex), but with multiple accounts due to the limits.
In order to easily switch between accounts I've build Switcheroo, which I've been using for the past 2-3 months now. I've decided to open source it: https://github.com/FTCHD/switcheroo
Works with other AI CLIs like Gemini, and other various CLIs like Vercel (if you're managing multiple accounts like me), Netlify, Github etc
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"
I've done exactly this.
I'm also experimenting with a 'dream mode' that extracts facts, and a 'librarian' that stores those facts in the MD wiki.
I don't know if there's a benefit to that yet, but I'm going to find out.
I love Atuin, but have some reservations about a shared server keeping all my shell history and agent sessions. Am I being too paranoid and missing out on convenience?
It is encrypted client side. Or you can run your own server.
> Am I being too paranoid and missing out on convenience?
No, I'd say it is more-so a lack of reading the article that is causing you to miss out.
I did read the article but missed that. Paranoia can definitely co-occur with distracted reading, they're independent dimensions ;)
Thanks for the info, will give it a try
Atuin is open source, you can just host your own server?
Fair enough, I missed that. Will give it a try!
Same, I really wanted to share history, but when I realised I was going to need to send things to a remote server I instead wrote a tiny script to search through backups that are shared across machines by Syncthing.
I just search over $BACKUPS/*/latest/local/share/fish/fish_history with grep and skim
Nice solution
I cant get used to it taking over the entire screen when scrolling history
I faced this too! Turned out it’s an easy config change to limit to height of your choice
atuin config set inline_height 5
export ATUIN_NO_MOUSE=true
But… you don't have to sync anything?
Fascinating. I just finished implementing this.
https://github.com/comalice/pi-tools contains a 'memory everywhere' module that makes all sessions BM25 vectors, and surfaces a set of memory tools to enable agents to search. You can add a new machine to the mix by registering a 'spoke'. The app runs on the 'hub'. I want to containerize the core app soon.
You can also change which computer is the hub fairly easily.
Correct me if I am wrong, but I imagine this would hammer one's token usage to read past entries to resemble context across machines/terminals and models?
Built this for same purpose: https://github.com/codealong/codealong
More of a desktop flavor though
posted on X a couple a days ago how atuin threads saved me from loosing the code I was working on and I accidentally removed uncommited worktree https://x.com/nklmilojevic/status/2118401844401541604
Yes i too faced the problem, lost valuable content across group of chat and not remembering in which chat it was. Tried searching but couldn't find it. Even asked ai itself does about the content whether it remembered.
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.
Aren't session also deleted after some time? It would be nice to keep them.
I've been using (and supporting) atuin for a while, and I find it a required bit of infrastructure. This is a nice upgrade!
I’ve been a supporter of Atuin and forever, and I really like her model here.
Excited to try it!
Probably a little late to this, because herdr has really eaten this segment. With their new Mac app, I don't see myself going back to atuin for this kind of experience. In fact, I get a little peeved using it on a vanilla terminal.
I'm using atuin as part of my Herdr setup. Atuin is not a replacement shell or multiplexer, it's basically a really advanced shell history.
Threads doesn’t compete with herdr, the two actually go together really nicely
Atuin indexes all your past sessions, herdr multiplexes all your present sessions.
We made a mod for herdr desktop to integrate the two: https://herdr.dev/mods/atuinsh/herdr-atuin-threads/
What peeves you on the vanilla terminal?
So now everyone and their mother are putting out AI harnesses/session managers aka browser tabs for AI.
It’s likely because you can vibe code the bones of one in a few hours.
This week I got Claude to build me a browser-based session manager to keep track of sessions and history of tasks. Works well enough for me and I’ll add features as I need.
I've spent the last couple of months putting a lot of time and energy into isolating my agents from each other: aggressive sandboxing, regular scanning of transcripts for agent-leaked credentials, per-agent encrypted credential stores, even physical (and network) separation of machines with different areas of work on them. Needless to say, as much as I have found atuin an excellent manager of my command-line history, I will be avoiding this.
yes agent leak secrets “Yes, and don’t ask again” in Claude Code would also save secrets in .claude/settings.local.json.