Connected sources
What ctx| can connect today, how source content is scoped, and where agent access fits.
ctx| connects source systems, scopes what should be used, and ingests the result through Git-backed pipelines. GitHub is the foundation: it gives ctx| access to code, and it provides the target repositories used when other sources need to become visible, reviewable context.
Available today
| Source | How it works |
|---|---|
| GitHub | Primary source connection for code search, file reads, cross-repo understanding, and knowledge graph ingestion. |
| Confluence | Select spaces and pages, sync them into a chosen GitHub repository, then ingest that repo-backed content into ctx |
| Slack | Mention the bot in a thread (app_mention) to capture that specific thread as Markdown into a chosen GitHub repository — intent-based capture, not a continuous channel mirror. |
| Linear | Select workspace scope, review draft linear/config.yaml on a pull request branch, then make that YAML live on the target branch by merging it. The connection config keeps the repository binding. |
| Notion | Select pages and databases, review draft notion/config.yaml on a pull request branch, then make that YAML live on the target branch by merging it. The connection config keeps the repository binding. |
| Repo-native docs | README files, docs/**, ADRs, AGENTS.md, skills, and similar files are ingested with the repository. |
What belongs in Git
Keep standards, decisions, and agent instructions close to the code when possible. Good examples include:
README.md,CONTRIBUTING.md, and files underdocs/**.- Architecture decisions such as
ADR-*.md. - Agent instructions such as
AGENTS.md. - Skills and other maintained team guidance.
This gives agents a better chance of finding the same source of truth your team uses, instead of relying on duplicated notes or stale chat history.
Agent access is separate
MCP clients are not source connections. Cursor, CI agents, and other MCP clients connect to ctx| through the MCP endpoint, then ask ctx| for context from the sources your organization has connected and ingested.
For agent setup, see ctx| MCP.
Roadmap
We expect more source connections over time, especially for engineering systems that hold operational context. Examples include:
- Additional issue and project tracking systems, such as Jira.
- Incidents and on-call, such as PagerDuty.
- Error tracking and observability, such as Sentry.
Availability may differ between fully managed and self-hosted deployments. Self-hosted operators must configure provider-owned OAuth applications and webhooks before the corresponding connector is available — see Self-host Confluence & Atlassian, Self-host Slack, Self-host Linear, and Self-host Notion.
How Git-backed source connections fit together.
Why GitHub is the foundational source connector for ctx|.
Sync selected Confluence spaces and pages into Git-backed context.
Capture specific Slack threads on demand into Git-backed Markdown.
Mirror reviewable Linear workspace context into a GitHub repository.
Mirror reviewable Notion pages and databases into a GitHub repository.
How agents connect to ctx| after sources are ingested.