Pilot kcap with one team, and settle the terms Kurrent's pages leave open before the first session is stored. Get the price and invite terms in writing, set exclusions and visibility, decide who pays for headless calls, then take the SSO, audit and certification questions to Kurrent.
When you need this
- Developers run several coding agents and want each session kept where teammates and the next agent can read it.
- A team has asked for a kcap Team trial and you need to know what it will cost at your seat count.
- Security asks which repositories kcap stores, who can read a session and how it is deleted.
Evaluation criteria
Price at your seat count
What will Team cost for this team?
Look forThe pricing page's structured data lists US$30 a month for one seat, or US$100 for five seats plus US$25 per additional seat, and prints no price for two to four seats. Kurrent's llms.txt prints US$15 per person per month billed annually. Get the figure for your seat count in writing.
Invites and seats
How does the team get in, and how many can join?
Look forThe pricing page's Local and Team buttons read Request an invite, and the Team card says 60 days free with no card required. Team holds 100 seats, pending invitations count as seats, and at the limit invitations are refused until a seat is freed.
Exclusions before capture
Which repositories must never be stored?
Look forAn excluded repository or folder is never stored, live or on import, whatever else is configured. Antigravity's imported history records no working directory, so exclusions cannot match it, while a configured allow list skips it.
Session visibility
Who can read a developer's sessions?
Look forMembers' sessions default to org_public, readable by the organisation for the organisation's own repositories. An admin sets the org-visible list of GitHub organisation or user names, and a blank list uses the connected GitHub account.
Headless call billing
Who pays for titles, summaries and local evaluations?
Look forThey run on each user's Claude or ChatGPT subscription sign-in by default, because the CLI removes ANTHROPIC_API_KEY and OPENAI_API_KEY from those calls. With use_provider_api_key set to true, the calls are charged to the key.
CI and shared machines
Can CI runners and sandboxes store sessions?
Look forMachine credentials let CI runners, build boxes and agent sandboxes store sessions without a person signing in, on workspaces that sign in through single sign-on. Revocation is immediate for new requests, and a token already held expires within the hour.
Deletion
What stays after a session is deleted?
Look forDeleting a session removes its data from the server, including its subagents, and cannot be undone. The agent's own transcript file on the machine stays, and so do other segments of a continuation chain unless they are deleted too.
Questions to ask vendors
- What is the Team price at our seat count, and which Kurrent page does it follow?
- Which provisioning standard does Enterprise directory integration use?
- Does kcap keep an audit log of user and admin actions, and can we export it?
- Which certifications cover kcap, and can we read the reports before signing?
- Which repositories and folders have we excluded, and who set the org-visible list?
Red flags
- Developers install the hook before exclusions and the org-visible list are set.
- A team assumes the llms.txt price without Kurrent confirming it in writing.
- Several people share one machine running the local edition, where anyone signed in can act as its admin.
- Windows developers rely on the local kcap agent commands, which are not available on Windows.
Products in this piece
Sources
- Official documentation
- 10