06 / 06Integrations · sources for the Stream

Bring project knowledge in from the tools where work happens.

Connect code, docs, tickets, issues, threads, and project notes so ContextStream can capture decisions, lessons, tasks, and source-backed context.

● live

GitHub

creates · PRs · issues · code refs · commits

● live

Slack

creates · threads · decisions captured inline

● live

Notion

creates · docs · runbooks · indexed pages

◐ beta

Linear

creates · tickets · plan · ownership

◷ soon

Jira

creates · issues · sprint context

● live

Local files

creates · READMEs · runbooks · code shape

01 What gets imported

Source artefacts become Stream events.

We don't dump the contents of your repos and docs. We read the shape, capture the durable artefacts, and link them back to source. Every fact has a citation.

Issues
Linear, GitHub, Jira
PRs
GitHub
Docs
Notion, READMEs
Threads
Slack
Decisions
derived from threads
Lessons
derived from PR retros
Tasks
Linear, GitHub
Comments
PR + thread context
02 Source-backed memory

Every durable fact links to its source.

No untraceable summaries. No phantom decisions. If a Stream event can't be traced back to a real PR, doc, thread, or session, it doesn't survive.

source · stream · atlas
Source
github.com/streambox/api · PR #284
Stream event
◇ row-level security for tenant isolation
Atlas node
decision:auth-rls · 7 edges
03 Scope and review

You decide what crosses the boundary.

Project scope

Each integration imports into a specific project scope by default — not the whole workspace.

Review queue

Captured candidates land in review. Promote, edit, or drop before they reach agents.

Time-boxed re-index

You set how often a source is re-read. Idle sources stop pulling cycles.

Connect your first source.

Point ContextStream at one repo, doc, or workspace. Watch project knowledge become reusable context.

Read integration docs