Skip to content
CortexDocs

Connect GitHub to Cortex

Connect selected organization repositories through a GitHub App installation.

Workplace connections

GitHub

Content and access

Pull request, issue, and commit metadata from selected organization repositories. Cortex does not clone repositories and does not read file contents.

Before you begin

Use Cortex admin access and organization-wide connection requirements, plus these source-specific permissions:

Required

  • GitHub App installation authority

    Have someone allowed to install GitHub Apps for the GitHub organization. If a GitHub owner completes a setup link, that owner does not need a Cortex account.

Set up GitHub

  1. In Cortex, open Organization → Apps and add GitHub.
  2. Continue to GitHub and install the Cortex GitHub App for the GitHub organization. Personal GitHub accounts are not supported.
  3. During installation, choose the repositories Cortex may access.
  4. Complete the GitHub authorization step and return to Cortex.
  5. Select Test & preview. The preview lists repositories from the installed organization.

If you cannot install GitHub Apps yourself

  1. Select Add connection, then choose GitHub under Source.
  2. Enter the organization's URL handle, such as acme from github.com/acme. Use letters, numbers, and hyphens; display names are not accepted.
  3. Select Create setup link, then Copy setup link.
  4. Send the link to a GitHub owner. It works only for that organization and expires after 72 hours. The owner does not need a Cortex account.

When your organization enables context collection, Cortex can collect related issues, pull requests and commits through permitted MCP connections. The GitHub App connection alone does not enable this collection. Ask your administrator whether it is enabled.

Collect permitted context after capture
ActivityAI activityCaptured from a supported tool
SourceRelated GitHub recordsFrom permitted connections
ContextSeparate contextRecords and source references
Candidates are collected separately. The prompt stays unchanged.
When enabled, Cortex can collect related GitHub records through permitted connections. Collected context remains separate from the prompt sent to your provider.

Collection requires an identifiable conversation and uses that activity, available repository context, source access and the active capture policy. It may be skipped when these inputs are missing or a collection limit is reached.

Only configured, permitted sources are used. Queries and retained records are bounded, prioritizing recent supported GitHub records. A missing candidate is not proof that the source record is absent.

Records are stored locally first. With synchronization enabled, Cortex can upload source references, metadata and a limited preview, with secrets scrubbed. URLs containing credentials, query strings or fragments are excluded. The full source response and literal search query are not uploaded as context. Failed uploads remain on the device for a later attempt; local collection does not establish workspace delivery.

Context is kept separately from the conversation. It is not automatically inserted into your provider prompt, does not change the provider response and does not change a Smart Router decision. See Security and data for storage and access, or Search to find connected records and inspect answer evidence.

Manage this connection

  • Cortex stores the GitHub App installation, not a GitHub user's access token.
  • Repository access follows the repositories chosen for that installation. Change that selection in GitHub.
  • Revoke or Delete stops new token use. Remove the App under the GitHub organization's Settings → GitHub Apps.
  • Captured metadata stays under your organization's retention terms. Contact Chaos Labs to purge it.

See the shared connection management guide for Cortex connection controls.