Skip to content
KurrentDB

Integrations

Integrations → Integrations (/admin/settings/integrations). What appears depends on plan and deployment

The Integrations page in the admin area: GitHub authentication, Slack and the trackersThe Integrations page in the admin area: GitHub authentication, Slack and the trackers
Integrations: GitHub authentication, the Slack app and the trackers

On workspaces that sign in with the GitHub App, a read-only panel shows the provider, the connected organisation or account, admin and team sync status, last successful syncs and errors

Trackers connects the two trackers kcap reads: with them, linked work items carry live issue and pull-request titles and status, and pull-request context reaches reviews. Each is an app, installed once for the workspace; nobody’s personal token is involved, and nothing is stored until the provider has confirmed the connection

The Trackers panel: Connect GitHub App and Connect LinearThe Trackers panel: Connect GitHub App and Connect Linear
Trackers: Connect GitHub App and Connect Linear

GitHub. Connect GitHub App sends you to GitHub to install kcap’s app on your organisation, or to pick it if it is already installed, and comes back here. Connecting uses your own GitHub account, so if it is not yet linked to kcap the panel says so and offers Link your GitHub account first. Once connected the panel reads Connected to org through the GitHub App, with the app’s permission state, how many repositories are admitted and how many are still waiting for verified access. Reconnect GitHub App repeats the installation while the current connection keeps serving; Disconnect removes it

Linear. Connect Linear opens Linear in another tab, where a Linear workspace admin approves kcap’s app; back here the panel previews the workspace it would connect, with a warning if that changes the workspace already connected, and Activate finishes. kcap then reads the workspace’s public teams plus any private team the admin gives the app. Disconnect removes it; if Linear later rejects the connection the panel says Linear needs to be reconnected with a Reconnect Linear button. A self-hosted deployment without Kurrent’s connection service connects with the app’s Client id and Client secret instead, with only the client-credentials grant enabled on the app

If work-item projection events have failed, a warning shows how many and Rebuild work items projection requests a rebuild at the next restart

One Slack app gives session and agent links a preview card and, where notifications are on, delivers direct messages. It has no slash commands

  1. Set up (or Reconfigure). Create Slack app opens Slack with a manifest prepared for your server; or paste it into Create New App → From a manifest. Choose the workspace, create the app, and install it under OAuth & Permissions. For an existing app, replace its manifest and reinstall; Slack only grants new scopes on reinstall
  2. Paste the Signing Secret (Basic Information) and Bot User OAuth Token (xoxb-…, OAuth & Permissions) and Save and validate. Both are stored encrypted
  3. Optionally post a session link in a channel the app is in and Check that the signed event arrived
The Slack integration settings in the admin areaThe Slack integration settings in the admin area
The Slack integration

Organisation-visible and public sessions unfurl with their summary; private, project-only and scoped sessions unfurl as a lock placeholder, because Slack has no signed-in viewer. Direct-message notifications readiness shows whether the app’s scopes allow DMs; each person opts in with Connect Slack in the bell’s notification settings, which show only where your workspace has notifications turned on

To stop the integration, uninstall the app from Slack

Integrations → Machines lists machine credentials with name, client id, role, creation date and Active or Revoked. Revoke stops a machine’s access; the row stays for audit. kcap machine list and kcap machine revoke do the same from a terminal. Machines are created in the CLI, never here, so the secret never passes through the server; Store sessions from headless machines has the commands