Skip to content
Kapacitor docs

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

Section titled “1. Open the dashboard”

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

https://<your-github-org>.kapacitor.ai

You should see the unified dashboard with three tabs: Agents, Sessions, Analytics. The list will be empty until you produce a session.

2. Run a session

Section titled “2. Run a session”

In a git repo where Kapacitor hooks are installed (the wizard installs user-wide by default, so this is any repo you open Claude Code in):

Terminal window
cd ~/some/repo
claude            # or: codex

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

Section titled “3. Watch it arrive”

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

  • A new entry in the Sessions tab with your repo name, your GitHub avatar, and a live “running” status.
  • Token counts updating as the agent produces output.
  • Tool calls appearing in the Trace tab if you open the session detail panel.

If you end the session in Claude/Codex (close the terminal or type /exit), the status flips to ended within a few seconds.

If nothing shows up

Section titled “If nothing shows up”

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

  1. kapacitor status — does the CLI reach the server? The output prints the tenant it’s targeting, so you can confirm the URL is right and that you’re signed in. If you’re pointed at the wrong tenant, run kapacitor login --discover to re-pick.
  2. Are hooks installed for the right agent? Run kapacitor plugin install (Claude) or kapacitor plugin install --codex (Codex). For Codex, also confirm you trusted each hook in /hooks.
  3. Is the repo in your ignore list? kapacitor ignore --list prints excluded paths. If the repo lives under one, Kapacitor silently skips it by design.
  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 GitHub identity the CLI is using.

Next: what to do with sessions

Section titled “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: