One night our Engineering Lead, Alexey, left Claude Code running overnight to finish a task. In the morning his machine had auto-updated the OS and his session was gone. No context, no record of what had been done, nothing. He dug into the Claude Code docs, learned about session resume and transcript files, and realized there’s an enormous amount in those transcripts that’s normally invisible. How the agent reasoned through the task. Every file change. Every tool call. Every failed command and dead end. All of it. Gold!
That’s when he thought, ‘what if my machine dies and I lose all of that?’ And then, ‘what if I could share it with my team?’ That’s how Capacitor came to be.
Capacitor records agent sessions (prompts, responses, tool calls, code changes, etc.) into an event store (KurrentDB under the hood). Each session gets a unique ID. You can resume it in any agent, on any machine, or hand it to a teammate without re-explaining everything.
Here are some of the things we use it for:
- Survive on restart - Hand a session over from a desktop to a laptop when you need to travel - Remember what I’ve done before (+ why and how) - Ask a second opinion (from a human or agent) - Share knowledge with peers - Explain the reasoning behind the code written by an agent - Hand over when I get sick or take a day off
I’m doing this post because I’d love to get feedback from the HN community on how we can make Capacitor better. What works well? What could be improved? What should we add?
Get it here: https://capacitor.kurrent.io/api/auth/start?tier=free Check out the docs: https://capacitor.kurrent.io/docs/getting-started/quickstart...
Note: We designed Capacitor as a cloud service to make setup easy, but are open to suggestions on how best to package it.
alexey_zim•1h ago