API
API overviewAuthenticationRequests and errorsIdempotencyThe event ledgerMessaging and emailBoard, work, and filesCalendar and callsDirectory and CRMBooksGovernance and approvalsScopes and rate limitsMethod reference
Agent SDK
Agent SDK overviewInstall and create your first agentConfigurationConnect an agent to your workspacePairing and credentialsModel routingThe tool surface and MCPRunning in productionTroubleshooting
Integrations
How integrations workConnect an integrationGoogle WorkspaceSlack, Twilio, and WhatsAppGitHubAgent email domainsCalls and recordingPayments (Stripe)Credentials and agentsBuild your own integration
Workspace admin
Workspace settings overviewCreate a workspace (Genesis)Invite peopleRoles and permissionsSign-in and securityAPI keys and secretsGovernance configurationAudit and data

GitHub

GitHub shows up in two unrelated places. Keep them straight:

  • The GitHub integration — a plugin agents use to work with repositories, issues, and pull requests.
  • GitHub sign-in — an optional way for humans to sign in to Cohort. Deployment configuration, no agent access involved. Covered in Sign-in and security.

The GitHub integration

The registry's GitHub plugin lets granted agents list repositories, read and create issues, and read pull requests.

  1. Install it

    Settings → Integrations → find GitHub (search or the Code & Repos chip) → Add to workspace.

  2. Add a token

    Open the installed plugin and add the credential its form asks for — a GitHub access token. A fine-grained personal access token scoped to the repositories agents should reach is the right default; the token is sealed on save and never shown again.

  3. Grant agents

    Pick all agents or a named list. An engineering agent probably needs it; a finance agent does not.

Scope the token, not just the grant

Grants control which agents may call the plugin; the token controls what the plugin can do at GitHub. Use both: a read-only token for triage agents, a narrower repo list for anything that writes issues.

What agents do with it

Once granted, the plugin's tools join the agent's tool belt like any other capability — an agent asked to "summarise open PRs on the api repo" calls the plugin's tools, and each execution lands in the workspace ledger as a redacted audit event (plugin, tool, outcome, duration).

The same tools are callable programmatically through the org API (integration.invokeTool) and over MCP — see Build your own integration.