Kapacitor/Multi-agent
One coding agent gets stuck. The next one reads the recap, sees what was tried, and continues from there — not from turn one.
Without the session
codex › context limit reached codex › /reset?
You switch to Claude Code. It has none of the prior reasoning.
flush().I’ll start by checking whether the lock-free swap is losing writes under contention.
Without the session, switching tools means repeating old work.
With the session
47 turns
stuck on race in flush()
new session
reads codex recap
Claude Code reads the Codex recap.
The four hypotheses Codex already ruled out stay ruled out.
Codex ruled out the lock-free swap, the channel rewrite, the timer reset, and the retry loop.
I’ll try the staged-commit approach next and keep the same failing test open.
With the session, changing agents does not erase the investigation.
How it works
Every session is tagged with its vendor and serialized to the same event stream. The next agent starts a new session, pulls the prior recap through the same MCP tool, and continues from there — regardless of who wrote the original. Read the mechanics in Recap and Session recall.
Kapacitor is vendor-neutral by design. Request private preview and we'll hook up the agents your team already runs.
Rather start a conversation? Talk to the team — we’re building with teams that already use coding agents.
Built by the team behind KurrentDB — event streams in production are what we do. Coding agents just produce a new kind.