Setup Server

Note

This page is for the admin doing the one-time setup. Other users can skip ahead to Setup CLI.

1. You receive a server URL

Kurrent provisions your Capacitor server and sends you a URL of the form:

https://acme.kcap.ai

…where acme is your organization’s slug, chosen at signup.

2. Sign in

Open your Capacitor server URL. You’ll be redirected to Kurrent’s hosted sign-in (single sign-on):

https://acme.kcap.ai

You signed up as the organization’s owner, so you can sign in right away — there’s no app to install and no per-server secret to configure. Anyone who’s a member of your Capacitor organization can sign in; membership in the organization is the gate, so there’s no separate user-provisioning step.

Admins

The organization owner (you, from signup) is automatically a Capacitor admin. Owners and admins get an Administration item in the avatar menu — see Invite your team below to add members and grant admin, and Administration for the runtime configuration that lives there (eval runner credentials, embedding provider, Slack integration).

3. Invite your team

Bring the rest of your team onto the server from the Administration console.

Owners and admins reach it from the avatar menu in the top-right corner → Administration. The item only appears if you’re an owner or admin; everyone else just uses the dashboard. The console opens on People → Members, with Invitations and Teams alongside.

Send an invitation

1. Go to People → Invitations and fill in the Send Invitation card:
   • Email address — the person you’re inviting.
   • Role — Member by default. The Admin option only appears if you’re the owner; admins can invite members but not other admins.
2. Click Send Invitation. Kurrent emails them an invitation link that’s valid for 7 days.
3. They open the link, sign in through single sign-on, and join your organization automatically with the role you chose — there’s no approval step on your side.

Pending invitations appear in the list below the form, with their status and expiry. Use the ⋮ menu on a row to Resend the email or Revoke an invite before it’s accepted.

Seats

Invitations count against your plan’s seat limit (active members plus pending invites). At the limit, Send Invitation is disabled with a note to upgrade — revoke a stale invite or remove a member to free a seat.

Manage members

People → Members lists everyone on the server with their role and join date. From the ⋮ menu on a row, an owner can Promote to Admin, Demote to Member, or Transfer Ownership; owners and admins can Remove Member (which also drops them from any teams). You can’t remove the last owner, and you can’t remove yourself.

4. Optional: Configure API keys for evals and embeddings

Two server-side features need third-party LLM credentials before they work: the eval runner and the embedding service. Both are configured from the Administration console (avatar menu → Administration → Settings). Both are gated to admins.

• Judge credentials (Settings → AI Providers). Lets users dispatch evaluations from the dashboard without running a local daemon. Add an Anthropic and/or OpenAI API key plus a judge model. Without this, dashboard evals can only run on a user’s own daemon, which means reviewers without a local Claude/Codex install can’t trigger them. See AI providers.
• Embeddings (keys on Settings → AI Providers; enable judge-fact dedup and pick the active provider on Settings → Evals). Powers judge-fact clustering on the Curation tab and the SessionStart guideline injection that feeds curated guidance back into future sessions. Supply a Voyage or OpenAI API key plus model. Without this, evaluation findings are still stored but never cluster, the Curation tab stays empty, and Claude won’t pick up curated guidance at session start. See AI providers and Evals.

Keys are stored encrypted at rest. You can configure either feature independently; neither is required to sign in or run sessions, but both are recommended for any team intending to use evals.

5. Optional: install Slack link previews

If you want session links posted into Slack to expand into a card showing repo, summary, and ownership, follow the in-app wizard at /admin/slack. The whole flow takes about 90 seconds: it generates a Slack app manifest pre-filled for your Capacitor server, you create an app from it in your Slack workspace, click Install to <Workspace> in OAuth & Permissions so Slack issues a bot token, then paste the Signing Secret and Bot User OAuth Token back into the wizard. See the Integrations walkthrough for the detailed step-by-step.

Slack is optional. Skip it now; come back later.

What’s next

You’re done. Teammates don’t need the server URL to sign in — once a member of your organization runs kcap setup, the CLI discovers your Capacitor server automatically. Point them at Setup CLI.