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.
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!
As far as I know(?) beta testers don't have the ability to give out invites anyways. At least I don't.
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'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.
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
atuin stores, searches and syncs agent sessions regardless of harness or setup
> 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.
Thanks for the info, will give it a try
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.
More of a desktop flavor though
Excited to try it!
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?
What peeves me is the poor responsiveness when navigating history. Pressing up or ctrl+r has this lag which throws off my typing. I'm on a pretty well specced setup, too. I used to be able to tolerate it, but since I barely do things directly from the command line anymore and have Claude worry about most of the command construction, the experience can be particularly grating.
Chalk it up to ever more instant gratification :)
Ahh. We've done a lot of work to improve this lately, if you're not using the daemon please try
``` atuin config enable daemon ```
and it should perform much better (it's the default on new installs)
atuin 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.
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.