Your first session

If the setup wizard finished cleanly, you don’t need to do anything special to capture a session. Hooks fire automatically. This page is a 60-second sanity check that the loop is working end-to-end.

1. Open the dashboard

Open your Capacitor server URL in a browser. The setup wizard printed it in the final summary; you can also re-read it any time with kcap status. It looks like:

https://<your-workspace>.kcap.ai

Open Sessions for the session list. Dashboard shows your recent activity and next actions; the sidebar also leads to Insights, Agents, Work Items, Knowledge, Evals, and Flows.

2. Run a session

In a git repo where Capacitor hooks are installed (the wizard installs user-wide by default, subject to your profile’s capture allow lists and exclusions):

cd ~/some/repo
claude            # or codex / gemini / cursor / copilot / pi / kiro / opencode

For Antigravity, open the repository in the IDE and start a conversation, or use its agy CLI.

Ask the agent anything — a question, a small task, doesn’t matter. The point is that the agent starts and finishes a turn.

3. Watch it arrive

Switch to the dashboard. Within a few seconds you should see:

• A new entry in Sessions with your repo name, your avatar, and a live “running” status.
• Messages and tool output arriving as the agent works, with token counts when the agent records them.
• Tool calls in Transcript and Events when you open the session.

End the session using your agent’s normal exit action. Capacitor records its end when the agent reports it or its capture process detects that it has stopped; timing varies by agent.

If nothing shows up

Walk this checklist in order; one of the first three usually catches it:

1. kcap status — does the CLI reach the server? The output prints the server it’s targeting, so you can confirm the URL is right and that you’re signed in. If you’re pointed at the wrong server, run kcap login --discover to re-pick.
2. Are hooks installed for the right agent? Run kcap plugin install for Claude, or add the flag for the others — --codex, --gemini, --pi, --opencode, --antigravity, --cursor, --kiro, --copilot (full list in Setup CLI). For Codex, also confirm you accepted the trust prompt the next time you launched codex (or trusted the kcap entries individually in /hooks) — and if you only use the Codex desktop app, which never prompts, that you trusted the Capacitor hooks under Settings → Hooks in the app.
3. Does the session pass your capture rules? Check kcap allow --list, kcap ignore --list, and kcap config show. A configured path or repository allow list must match, and exclusions always win.
4. Are you running the agent from a directory inside a git working tree with a remote? Sessions outside a git repo are still captured, but they won’t be grouped by repo on the dashboard.
5. Is your default visibility set to private? Private sessions only appear to you — confirm you’re signed into the dashboard as the same identity the CLI is using.

Next: what to do with sessions

Once you have a session, the rest of the docs cover the things you’ll actually do with it:

• Sessions — reading and navigating recorded work.
• Session recap and recall — ask your agent to catch up on earlier work and find past decisions.
• PR review — kcap review <pr-url> with full session context.