Join an existing kcap workspace

Your team’s workspace already exists; an admin invited you to it. This page takes you from the invitation email to your first stored session

1. Accept the invitation

The email has a link that is valid for seven days. Open it and sign in with the account the invitation was sent to. You become a member of the organisation with the role the admin chose; there is nothing to approve on their side

If the link has expired, ask the admin to resend it from Administration → People → Invitations

2. Install kcap on your machine

Sign in to the workspace in your browser and open Get set up from your avatar menu in the top right. It shows the two ways to install, with your workspace already filled in. Either works; pick the one you prefer

The desktop app, on a Mac

1. From Get set up, download the app (Apple silicon, macOS 15 or later), drag it into Applications and open it
2. Choose For your team, cloud and sign in with the same account you accepted the invitation with. The app lists the workspaces your account belongs to; pick yours
3. On the agents screen, tick Record for each coding agent you want stored and Tools for each one that should get kcap’s tools. The app only lists agents it found on this machine
4. Choose who can read new sessions by default. The choices are Nobody else, People I share a project with, and Everyone in the account for your organisation’s repositories. We recommend Everyone in the account: shared sessions are what let a teammate pick up your work, a reviewer see your reasoning, and the team’s knowledge build. If you would rather start with Nobody else, that is fine too; you can change the default later and share any single session when you want to
5. Import the history already on this machine. We recommend it: your past sessions are what make recall, next work and knowledge useful from the first day. It runs in the background
6. Let the app put kcap on your terminal path and run the daemon as a background service. We recommend both: the path gives you the terminal commands, and the daemon is what lets you run agents on this machine from the browser

The CLI, on any machine

Either installer works. The script, on macOS or Linux:

curl -fsSL https://www.kurrent.io/install | bash

On Windows, in PowerShell:

irm https://www.kurrent.io/install.ps1 | iex

The script downloads kcap, checks it against the release checksum, and starts kcap setup. Or npm:

npm install -g @kurrent/kcap
kcap setup

Setup opens a browser tab. Sign in with the account you accepted the invitation with; setup finds your workspace, so you never need its URL. It then asks, in the browser where the workspace supports it and otherwise in the terminal:

• Which agents to store, and which get kcap’s tools. Say yes to every agent you use
• Who can read new sessions by default. We recommend sharing with everyone in the account; Nobody else is a fine place to start if you prefer, and you can change it later
• Whether to import the history on this machine. We recommend yes; it runs in the background
• Whether to run the daemon as a service. We recommend yes; it is what lets you run agents on this machine from the browser

Leave the terminal open until setup says it is finished

3. Store your first session

Restart any coding agent that was already running, so it loads the kcap hooks. Then start one in a repository and give it anything to do:

cd ~/code/my-repo
claude          # or codex, gemini, cursor-agent, copilot, kiro-cli, opencode, pi, agy, muse, grok, vibe

Using Codex? Trust the hooks once

Codex runs newly added hooks only after you trust them, so until you do, nothing is stored

Codex CLI

1. Start codex in any repository
2. Codex shows a prompt listing the new kcap hooks. Choose to trust them. Accepting once trusts them all
3. If you dismissed the prompt, type /hooks inside Codex and trust each kcap entry

Codex desktop app

1. The app never shows the trust prompt, and setup may not have detected it. In a terminal, run kcap plugin install --codex
2. In the app, open Settings → Hooks
3. Trust each hook named kcap
4. Start a new conversation; it is stored from the first turn

Open https://<your-workspace>.kcap.ai and choose Sessions. Within a few seconds your new session appears, with your repository and your avatar, and fills in turn by turn. If you imported history, your past sessions are arriving too, newest first; a large import takes a while and continues in the background

Sessions other people have shared with you appear in the same list. An empty list beyond your own means nothing has been shared yet, not that something is wrong

If your session does not appear, start with these:

kcap whoami     # which account and workspace the CLI is signed in to
kcap status     # the server is reachable, and which agents are wired

My session doesn’t appear has the rest

Further reading

• Take the tour: seven questions to ask your agent about your own work
• What you can do: the walkthroughs