What Capacitor captures
Capacitor is a session recorder. If you’re evaluating Capacitor for a codebase where confidentiality matters, read this page first — and know that everything here is under your control before a team-wide rollout.
Click here for more about the system architecture.
What’s captured
Section titled “What’s captured”When a session is captured, the kcap watcher sends the complete transcript to your Capacitor server:
| Data | Detail |
|---|---|
| Every prompt | Full text of every user message to the agent |
| Every response | Full text of every agent reply |
| Every tool call + result | Bash commands, file reads, edits — with timing, output, and the exact diffs applied |
| Thinking blocks | The agent’s reasoning, alongside the turn that produced it |
| Token counts | Input, output, cache reads and writes — per turn and per subagent |
| Subagent trees | Every spawned subagent with its own transcript and token tally |
| Repository context | Git repo, branch, and PR linkage |
Treat the transcript as sensitive by default: if a prompt or a command’s output contains a secret or a proprietary discussion, that content is part of the transcript and will be stored on your Capacitor server.
- Your source code. The repository itself and source code is never uploaded by Capacitor. However, if prompts, responses, and/or tool output contains it, then it will appear in Capacitor.
- Excluded work. Sessions in
excluded_reposor under akcap ignorepath send nothing — the hooks skip them silently.
The controls
Section titled “The controls”Two kinds of control apply, and they’re worth knowing before a team-wide rollout:
- What is captured — the exclusions above, configured in the CLI configuration.
- Who can see it — per-session visibility, hiding, and deletion, covered in Visibility & sharing.
For how capture works mechanically — hooks, the watcher, and the event store — see System architecture.