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.
nzoschke
It's not clear which parts of Claude state are safe to sync and which you want to keep local to one machine. I'm doing something with syncthing trying to keep agent session history available and little bits of it keep breaking. I haven't looked at this new feature in atuin does it have a really good understanding of what is worth syncing?
NelsonMinar
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
baalimago
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.
hugmynutus
My version is very unixy:
$ ctools resume ssh://laptop.local/code/project
Goes to laptop.local, looks for sessions done in that path, finds the most recent, copies it locally and resumes it.
There's also ls, grep, copy, cat... It looks and feels like the existing tools, that's the point.
Workflow is the thing that matters here and I'm terminal first
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"
talloaktrees
I've a love affair with Atuin but this may turn into a full blown obsession
thesurlydev
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?
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
comments (10)
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.
nzoschke
NelsonMinar
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
baalimago
hugmynutus
$ ctools resume ssh://laptop.local/code/project
Goes to laptop.local, looks for sessions done in that path, finds the most recent, copies it locally and resumes it.
There's also ls, grep, copy, cat... It looks and feels like the existing tools, that's the point.
Workflow is the thing that matters here and I'm terminal first
I'll make it more flashy soon https://github.com/day50-dev/ctools
kristopolous
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"
talloaktrees
thesurlydev
orbis-tertius
nklmilojevic
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
ftchd