Quickstart
These docs describe the Capacitor v1.1.1 release.
Capacitor records your coding-agent sessions so you and your team can search the conversation, understand a change, and continue work in another agent. Start with one repository and one session.
1. Install and connect
Section titled “1. Install and connect”npm install -g @kurrent/kcapkcap setupSign in when the browser opens. Setup discovers the workspaces your account can access. If you have no workspace, choose Create a new workspace, enter your organization name and a URL slug, and wait for provisioning. You can also create a workspace in the browser.
If you already know your workspace, use its slug or URL:
kcap setup acmeFollow the setup screens to choose your agents, recording, tools, default visibility, and any history you want to import. On servers with browser setup, your browser choices are applied by the CLI. Otherwise, setup continues in the terminal. Leave the terminal running until setup finishes.
Recording uploads the transcript, including prompts and tool output, to your workspace. Capture allow lists and exclusions let you limit which repositories and directories are recorded. Visibility controls who can read recorded sessions.
2. Start a fresh agent session
Section titled “2. Start a fresh agent session”Restart your agent after setup so it loads the integration. For Codex, accept the hook trust prompt in the CLI, or trust the Capacitor hooks in Settings → Hooks in the Codex desktop app.
From your repository, start an installed agent and give it a small task:
cd ~/dev/my-repoclaudeClaude Code, Codex, Cursor, Gemini CLI, Copilot CLI, Kiro, OpenCode, Pi, and Antigravity are supported. Use the agent you normally work with; see Setup CLI for installation details.
3. Open the recording
Section titled “3. Open the recording”Open your workspace at https://<your-workspace>.kcap.ai, sign in, and select Sessions. Open the new session to read the conversation and inspect tool calls as they arrive.
If it does not appear, run:
kcap whoamikcap statusCheck the server URL, identity, and integration status. Your first session covers the other common causes.
4. Bring in earlier work
Section titled “4. Bring in earlier work”If you skipped history during setup, preview what is on disk, then import a repository:
kcap import --discoverkcap import --repo .Read the confirmation before uploading. Repeating an import uploads missing content without duplicating what is already stored. Import your history explains repository, agent, and date filters.
5. Continue with that context
Section titled “5. Continue with that context”Copy a session ID from the dashboard. Start another session in the same repository, in the same or a different supported agent, and ask:
Recap session <session-id> and continue where it left off.The installed recall tools let the agent read the previous decisions and unfinished work. You can also read the transcript directly:
kcap recap --full <session-id>Use the session’s sharing controls to give a teammate access. They can then use the same session ID from their own agent. When the work produces a pull request, review it with the implementation context:
kcap review <pr-url>For the next steps, see session recall, visibility and sharing, and PR review. Workspace owners can follow Setup Server to invite teammates and configure optional services.
