Issues
From Linear, GitHub and Jira.
06 / 06Integrations
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.
- GitHubPRs · issues · code refs · commitsLive
- Slackthreads · decisions captured inlineLive
- Notiondocs · runbooks · indexed pagesLive
- Lineartickets · plans · ownershipBeta
- Buzzshared project context · agent handoffsOpenBeta
- Jiraissues · sprint contextComing soon
- Local filesREADMEs · runbooks · code shapeLive
01What gets imported
Source artefacts become Stream items.
We don’t copy the contents of your repos and docs. We read their shape, keep the durable artefacts and link each one back to its source. Every fact has a citation.
PRs
From GitHub.
Docs
From Notion and READMEs.
Threads
From Slack.
Decisions
Derived from threads.
Lessons
Derived from PR retros.
Tasks
From Linear and GitHub.
Comments
PR and thread context.
02Source-backed memory
Every durable fact links to its source.
No untraceable summaries and no phantom decisions. If a Stream item can’t be traced to a real PR, doc, thread or session, it doesn’t stay.
Source
github.com/streambox/api · PR #284
Stream item · Decision
Row-level security for tenant isolation
Atlas node
decision:auth-rls · 7 edges
03Scope and review
You decide what crosses the boundary.
Project scope
Each integration imports into one project scope by default, not the whole workspace.
Review queue
Captured candidates land in review. Promote, edit or drop them before they reach agents.
Time-boxed re-index
You set how often a source is read again. Idle sources stop using cycles.
Connect your first source.
Point ContextStream at one repo, doc or workspace, and its project knowledge becomes reusable context.