❯ kcap import --all
[claude] Loaded 171 · Resumed 3
[codex] Loaded 40
✓ 214 imported · 0 failed
1 · Record
Hooks and the watcher stream each agent’s transcript as it runs. Past sessions come in with one import.
kcap/How it works
How a recorded session becomes shared memory.
kcap 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 kcap 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.
❯ kcap status
Server northwind.kcap.ai ✓
Hooks Claude ✓ Codex ✓ Cursor ✓
Daemon running
Your kcap workspace (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.
One session, end to end
2 · Append
Your server appends every turn, tool call and result to an immutable event stream.
3 · Project
The stream becomes a readable record: outcome, evaluation, changes and cost.
› Have we worked on this before?
● kcap-sessions · search_sessions
Yes: Tomás fixed it in PR #1279.
4 · Recall
The next agent asks your server what the team already knows, and cites it.
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 kcap captures, System architecture, and Visibility & sharing.
See it on your own repo.
Start free in minutes. kcap 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.