Integrations & machines
Open Integrations → Integrations (/admin/settings/integrations) for GitHub authentication health, Slack, and tracker credentials. Available sections depend on your deployment and plan.
GitHub authentication health
Section titled “GitHub authentication health”On deployments that use GitHub authentication, a read-only panel reports the authentication provider, connected organization or personal account, and administrator/team sync status. It shows last successful syncs and errors. This panel moved from the former General page.
GitHub and Linear credentials
Section titled “GitHub and Linear credentials”On Team and Enterprise, Trackers connects GitHub and Linear to enrich linked work items with issue or pull-request titles and status. On Free, the section is GitHub integration: GitHub still supports default-branch, commit-history, and deployment synchronization, while Linear and Work Items are unavailable.
| Provider | Form field | Configuration key |
|---|---|---|
| GitHub | Personal access token | Integrations:GitHub:Token |
| Linear | Personal API key | Integrations:Linear:ApiKey |
Enter the credential and click that provider’s Save button. Capacitor validates it with the provider before saving it encrypted. Leaving the input blank keeps the existing credential. Clear asks for confirmation before removing it. Status can include the last sweep, cooldown, and last error.
If work-item projection events failed, a warning shows their count and oldest failure. Rebuild work items projection requests a destructive rebuild at the next server restart; use it to recover a projection stuck behind unresolved errors.
Slack setup
Section titled “Slack setup”One Slack app handles session and agent link previews and, when enabled, direct-message notifications. It does not provide slash commands or interactive message inputs.
Under Slack integration, click Set up, or Reconfigure for an existing connection. This opens /admin/settings/integrations/slack; the older /admin/slack address redirects there.
1. Create the Slack app
Section titled “1. Create the Slack app”Click Create Slack app to open Slack with a manifest prepared for your server. Alternatively, choose Or paste manifest manually and use Slack’s Create New App → From a manifest flow.
Choose your workspace and create the app. In its OAuth & Permissions, install it to the workspace. The manifest requests links:read, links:write, chat:write, im:write, users:read, and users:read.email for previews and notification delivery.
For an existing app, replace its App Manifest with the wizard’s current manifest and reinstall it. Slack requires reinstallation to grant newly added scopes.
2. Paste credentials
Section titled “2. Paste credentials”Copy the Signing Secret from the Slack app’s Basic Information page and the Bot User OAuth Token (xoxb-…) from OAuth & Permissions. Paste them into the wizard and click Save and validate.
The wizard validates the bot with Slack before persisting the credentials. A successful save shows the bot and workspace name. Both secrets are stored encrypted.
3. Verify a link preview
Section titled “3. Verify a link preview”In Verify unfurl (optional), post a Capacitor session link in a channel where the app is installed, then click Check. The wizard waits for a signed link_shared event and reports whether it arrived. Complete the wizard when finished.
Private, project-only, and explicitly scoped sessions produce a lock placeholder instead of their full summary, because Slack has no authenticated viewer for checking membership grants. Organization-visible and public sessions can produce the full preview; see Visibility & sharing.
Slack direct-message notifications
Section titled “Slack direct-message notifications”When notifications are enabled on the deployment, the wizard also shows Direct-message notifications readiness. Each person opts in through their own notification settings; configuring the app does not opt everyone in.
If the panel reports missing scopes, update the manifest in step 1 and reinstall the same app. Readiness updates after the server verifies the scopes. If Slack does not report scopes, delivery waits for a successful probe. A missing public origin causes notification links to be omitted until an operator configures it.
Public URL and reverse proxies
Section titled “Public URL and reverse proxies”The manifest must use the server’s public origin. An operator can set Slack:PublicOrigin explicitly; otherwise setup uses the browser origin hint, then the inbound request host. Configure the explicit origin behind a proxy that changes the host.
If the app’s saved manifest origin differs from the current origin, Integrations shows a warning. Reconfigure and reinstall the app after a domain change so Slack sends link events for the correct domain.
To stop the Slack integration, uninstall the app from the Slack workspace. Operators can also remove its stored credentials through server settings.
Machines
Section titled “Machines”Open Integrations → Machines (/admin/settings/machines) when machine credentials are enabled. Machines record headless sessions from CI runners or agent sandboxes; they cannot administer the server or join projects.
Create a machine with kcap machine create <name>. WorkOS issues its credential once in the terminal; the console never displays it again. The registry shows each machine’s name, client ID, role, creation date, and Active or Revoked status.
Choose Revoke on an active machine and confirm to stop its access. Revoked machines remain in the registry for audit history.