GitHub
Code, pull requests, and repository truth
Repository structure, issues, pull requests, review comments, and checks can shape the work with project scope attached.
Context Connectors
Connect the context your agents need to operate intelligently.
A Context Profile decides which of these sources a specialist works from, so one connection can serve a security review and a frontend build without either of them reading everything.
Linear
Product and issue context
The team and issue context around an objective follows it into the thread, so the work is scoped against what your team already wrote down.
Coming soon
Notion
Specs, runbooks, and product decisions
A planned connector would bring selected pages and databases into governed context for product and engineering work.
Coming soon
Figma
Design intent and component behavior
A planned connector would carry selected design files, product flows, component behavior, and review context into the work.
Coming soon
Bitbucket
Repositories, pull requests, and pipelines
A planned connector would bring repository structure, pull requests, and pipeline results into governed context for teams that host their code here.
Coming soon
Jira
Epics, tickets, and delivery priority
A planned connector would carry selected projects, epics, and ticket priority into the objective a specialist works against.
Coming soon
Slack
Decisions and incident context
A planned connector would bring selected channels, decisions, handoffs, and incident threads into governed context.
Coming soon
Confluence
Architecture notes and team docs
A planned connector would bring selected spaces, architecture decisions, ownership notes, and team documentation into the work.
Coming soon
Mintlify
Product docs and API references
A planned connector would ground implementation work in selected product behavior, API contracts, examples, and customer guides.
Source Boundaries
Outside context enters through a governed boundary.
A ticket, pull request comment, README, or design note can now shape what an agent believes. Codespeed treats outside context as evidence with scope, attribution, and revocation attached.
Explore Codespeed governance controlsProject scope comes first
A connected source becomes available only to the projects and workspaces your organization allows.
Profiles decide who can use it
Each Context Profile can inherit the sources its role needs for the work.
Sources stay attributable
Teams can see which external systems feed a profile and which source shaped a work decision.
Revocation stays available
A connector can be restricted, disconnected, or removed from a profile when the source should stop shaping work.