Summer AI can read selected code to help explain how your product works. For example, it can inspect the logic behind an order tracker while investigating a customer's report. Your customer records and company policies remain separate sources.
Connect your company
- Open Settings → Integrations → GitHub and choose Production or Staging.
- Select Connect GitHub. Sign in to GitHub, select the repositories the Summer AI App may access, and authorize its read-only access.
- Back in Summer AI, choose a repository and its branch or exact commit.
- Keep Whole repository selected, or use Choose folders to share specific folders. You can open a folder to select its children.
- Select Save access and sync. Wait for the cached commit and file count to appear before using the code in an investigation.
GitHub grants repository access. Summer AI enforces your additional folder selection before code is cached or provided to an agent. Keep confidential material in a separate repository if you need GitHub itself to enforce that boundary. The connection cannot write code, create issues, merge pull requests or deploy your product.
Code is cached once and loaded when needed
Summer AI saves a compressed copy of the selected text files in private storage. New Ops sandboxes do not clone repositories, pull GitHub or receive an automatic copy of the code. The investigator can load the existing cache when application code is useful, then search it with its normal file tools.
Each source shows its cached commit and sync time. This identifies the code Summer AI read; it does not establish which commit you have deployed. Select an exact deployed commit when that distinction matters.
GitHub push events refresh a selected branch's cache. Sync now also checks for changes and reuses an unchanged commit. Failed syncs leave the prior dated cache visible and retry in the background; they do not silently label it current. Binary files, environment files and detected credentials are not included. Large selections may need fewer folders.
Change or remove access
Changing saved folders removes the previous cached access and prepares the new selection. Disconnecting removes Summer AI's code cache for that company and environment. Removing repositories from the GitHub installation or suspending/uninstalling the App revokes their cached access when GitHub delivers the signed update.
Already retained investigation evidence is still historical evidence. Removing access cannot erase code an agent previously read from its retained history.
API, CLI and MCP
The same connection settings are available through github.connection.read, github.connection.start, github.repositories.list, github.folders.list, github.sources.save, github.sources.sync, github.sources.read and github.connection.disconnect. These operations require your delegated setup permission for the selected company and environment. GitHub authorization still happens in your signed-in browser; tools never accept an arbitrary installation ID as proof of access.