How a recorded session becomes shared memory.

Capacitor records each coding-agent session as a durable event stream, then turns it into memory your whole team can draw on. Here’s the machinery: what runs on your machine, what runs on your server, and how one session travels between them.

Two moving parts

How it works

On your machine

The Capacitor client is source-available — you can read every line. It installs hooks into the coding agents you choose, and a background watcher tails each agent’s own transcript file and streams it to your server as the session runs — without changing how you work.

Your Capacitor server (cloud)

A Kurrent-hosted cloud instance, dedicated to your organization. It receives the session transcript, stores each session, and builds the data models behind the dashboard and search — then answers your agents’ queries against them.

Architecture diagram. You interact with your coding agent and the kcap CLI. On your machine, kcap hooks and the agent transcript sit inside the coding agent; the hooks send hook events to the kcap server, and the transcript feeds the kcap watcher, which streams it live to the kcap server. The agent makes tool calls to the kcap MCP server, which queries the kcap server; the kcap CLI talks to the kcap server too. In your Capacitor server in the cloud, the kcap UI talks to the kcap server, which reads and writes the kcap event store database (KurrentDB). — One session, end to end: the watcher streams the transcript to your server, which appends it to an immutable event store and projects it into the dashboard, search, and review.

Go deeper

For what a recording contains, where it goes, and who can see it, see Security. For the exhaustive, field-by-field list — and the exclusions and controls in full — read What Capacitor captures, System architecture, and Visibility & sharing.

See it on your own repo.

Start free in minutes. Capacitor records what your agents actually did — for your team to replay, audit, and discuss. Nothing about how you work changes.

Start free Rather start a conversation? Talk to the team

Built by the team behind KurrentDB — event streams in production are what we do. Coding agents just produce a new kind.

Session recap · yesterday 16:42

Fix flaky auth-token refresh test

Tried mocking the clock first — abandoned after the race persisted. Root cause: token cache TTL rounding. Patched in auth/cache.ts, added regression test. Two approaches rejected, one shipped.

claude-code41 min12.4k tokenscontinue →