242 points by linsomniac 9 days ago | 87 comments | View on ycombinator
nzoschke 9 days ago |
hugmynutus 9 days ago |
baalimago 9 days ago |
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
orbis-tertius 9 days ago |
talloaktrees 9 days ago |
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"
yababa_y 8 days ago |
thesurlydev 9 days ago |
d4rkp4ttern 8 days ago |
On my machine, with ~22 GB of sessions, its index is under 1 GB, while Threads added 8.1 GB after importing the same sessions (it stores each conversation twice: once encrypted for sync, once for search). Agents can use it too (aichat search --json), and from a search result you can resume, or carry the work into a new session.
uv tool install claude-code-tools
brew install pchalasani/tap/aichat-search # or: cargo install aichat-search
aichat search
aichat also has other subcommands for working with sessions: porting one between Claude Code and Codex (or to another provider), rolling over to a fresh session that carries the context, trimming bloated sessions, moving a session to another project or account, etc.No sync across machines; that's where Threads is nicer. Also Threads seems to show sub-agent relations and live-status, which mine doesn't. I like my TUI interface better though.
https://pchalasani.github.io/claude-code-tools/tools/aichat/...
nklmilojevic 9 days ago |
ftchd 9 days ago |
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
all2 9 days ago |
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.
kristopolous 9 days ago |
$ 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
petesergeant 9 days ago |
oorestisime 8 days ago |
NelsonMinar 8 days ago |
jdorfman 8 days ago |
RyJones 9 days ago |
stasomatic 8 days ago |
tristanMatthias 8 days ago |
ashenke 9 days ago |
baskar12ai 9 days ago |
TheIronYuppie 9 days ago |
Excited to try it!
ghempton 9 days ago |
More of a desktop flavor though
GNOMES 9 days ago |
timothyduong 8 days ago |
ndrake 9 days ago |
amelius 9 days ago |
krisgenre 8 days ago |
languagehacker 9 days ago |
nharziro 7 days ago |
tacker2000 9 days ago |
myagentbudget 9 days ago |
agline_in 9 days ago |
cellularatom 8 days ago |
sick_of_slop 9 days ago |
LimitExperience 8 days ago |
jackfreeman 9 days ago |
sehw 9 days ago |
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.