It never scans or uploads your repository — but files your agent read or changed are part of the recording. If a project shouldn’t be recorded at all, exclude it.
What if a credential appears in a session?
It’s removed on your machine first. We match known formats for keys, tokens and passwords, so treat it as a safety net — not a substitute for excluding sensitive projects.
How do I keep a project out?
Exclude it. Nothing from that work is sent.
Who can see my sessions?
By default, teammates with access to the same repository. Work in a personal repo stays private, you can make any individual session private, and you can change your default so every new session starts private.
Where is my data hosted?
The EU. Sign-in runs through WorkOS in the US; the full list of services we rely on is in the privacy policy.
Do you train on my data?
No — and we don’t sell or share it.
Can I delete a session?
Yes. Any session, any time.
Questions about security?
If your team needs detail this page doesn’t cover, ask us directly — we’d rather answer than have you guess. Talk to the team
See it on your own repo.
Start free in minutes. You choose what’s recorded, who sees it, and what gets deleted.
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.
