Using GitHub Files in Contexts

Once you've connected a GitHub account →, you can browse your repositories and select individual files to include in agent contexts. READMEs, architecture docs, runbooks, API references, and any other text-based file can be indexed and retrieved during meetings.

→ Open Data Sources →

Selecting GitHub files in a context#

1. Open or create a context in Data Sources →
2. In the Files section, expand the GitHub panel
3. Click your connected GitHub account to open the file browser
4. Select a repository from the dropdown — you can search by name
5. Navigate the folder structure using the breadcrumb trail
6. Check the files you want to include
7. Save the context — selected files are downloaded and indexed automatically

The file browser shows the default branch of each repository. Folders navigate one level at a time — click a folder to go deeper, use Back or the breadcrumb to go up.

Supported file types#

GitHub files are downloaded as raw text. Any file containing readable text is supported, including:

Code and config: .ts, .tsx, .js, .py, .rb, .go, .rs, .java, .cs, .sh, .yaml, .yml, .json, .xml

Documentation: .md, .mdx, .txt, .html, .htm, .csv

Documents: .pdf, .docx, .xlsx, .pptx

Binary files (images, compiled outputs, etc.) are not useful for text retrieval and should not be selected.

Plan limits#

The number of GitHub files you can index is tracked separately from your uploaded and Drive files:

The limit applies across all your connected GitHub accounts combined.

Automatic daily sync#

CoAgentor checks all your selected GitHub files for changes every 24 hours. When a file's content has changed (detected by Git blob SHA comparison), CoAgentor re-downloads it and re-queues it for re-processing automatically.

Files that have been deleted or moved in the repository are marked as failed with a clear 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. The result shows how many files were updated versus unchanged

Tips#

✅ Select README.md files for quick repo overviews — they're usually a concise summary of what a codebase does

✅ Architecture docs and decision records (docs/, ADR/) are high-value context for technical meetings

✅ Use manual sync after a significant push if you need changes available before the daily window

❌ Avoid selecting auto-generated files (lock files, compiled output, migration files) — they add noise to retrieval without useful content

❌ Don't select the same file via multiple connected accounts — it will be indexed twice and consume quota on both

→ Connecting GitHub → → Contexts and Scopes →