GitHub

Connecting GitHub lets CoAgentor index files from your repositories — documentation, code, configs, READMEs, architecture decision records — so your agents can reference them during live meetings.

→ Connect GitHub →

What access CoAgentor requests#

CoAgentor uses a GitHub OAuth App that requests read-only access to your repositories. It can list repos, browse file trees, and download individual file content.

CoAgentor never pushes commits, creates branches, opens pull requests, or modifies any repository content.

Connecting your account#

1. Go to Integrations → and click the Data Sources tab
2. Click Connect GitHub
3. You'll be redirected to GitHub to authorise the application
4. Grant access — you can choose between all repositories or select specific ones
5. After authorising, you're returned to your Integrations page with a Connected badge showing your GitHub username

How file selection works#

After connecting, you select specific files from your repositories when building a context:

1. Open or create a context in Data Sources →
2. Expand the GitHub section in the file picker
3. Select a repository from the dropdown
4. Navigate the folder tree and check the files you want
5. Save the context — selected files are downloaded and indexed

Files are downloaded from the default branch. You can navigate folders one level at a time using the breadcrumb trail.

→ Using GitHub files in contexts →

Automatic daily sync#

CoAgentor checks all your selected GitHub files for changes every 24 hours. Change detection uses Git blob SHA comparison — only files whose content has actually changed are re-downloaded and re-processed.

Files that have been deleted or moved in the repository are marked as failed with a descriptive message. Remove them from the context and re-select at the new path if needed.

Manual re-sync#

To pull in changes immediately without waiting for the daily cycle:

1. Go to Integrations → Data Sources →
2. Click Sync next to your GitHub account
3. Updated files are re-downloaded and re-processed automatically

Token handling#

GitHub OAuth Apps issue non-expiring access tokens. This means your connection stays active indefinitely — there's no token refresh or 90-day expiry to worry about. The only way the token becomes invalid is if you manually revoke the OAuth app in your GitHub settings.

If the token is revoked, the connection status will show an error and you'll need to reconnect.

Connecting multiple GitHub accounts#

On higher plans, you can connect more than one GitHub account — useful if you have separate personal and work accounts, or accounts across different GitHub organisations.

File limits by plan#

The number of GitHub files you can index is tracked separately from uploaded files and other data sources:

The limit applies across all your connected GitHub accounts combined.

→ View all plan limits →

Supported file types#

Any file containing readable text can be indexed. This includes code files (.ts, .py, .go, .rs, .java, etc.), documentation (.md, .txt, .html), config files (.yaml, .json, .toml), and even documents (.pdf, .docx, .xlsx).

Binary files like images, compiled outputs, and lock files are not useful for text retrieval and should not be selected.

→ Full list of supported formats →

Disconnecting#

1. Go to Integrations → Data Sources →
2. Click Disconnect next to the account you want to remove
3. Confirm the prompt

Disconnecting removes all files and embeddings sourced from that GitHub account. Any contexts referencing those files will stop retrieving them. The context itself is not deleted.

This does not revoke CoAgentor's access in GitHub — to fully remove the OAuth app, go to GitHub → Settings → Applications → Authorized OAuth Apps and revoke CoAgentor.

Troubleshooting#

"OAuth failed" error — This usually means the GitHub authorisation was cancelled or timed out. Try again from the Data Sources tab.

Repository not showing in the picker — If you chose "Only select repositories" during authorisation, the repo may not be included. Go to GitHub → Settings → Applications → Authorized OAuth Apps → CoAgentor → Configure, and add the missing repository.

Files stuck in Pending — File processing typically starts within 60 seconds. If a file stays in Pending for more than 5 minutes, try triggering a manual sync.

"Source file was deleted or moved" — The file's path changed or the file was removed from the repository. Remove it from the context and re-select at its new location.

→ Using GitHub files in contexts →