GitHub
Opt-inLink repositories to a project so pull requests, commits and issues attach themselves to the task or bug their branch names. Agents get the code context too.
Your code, on the work it belongs to.
Pull requests, checks and deploys land on the task, the bug and the overview.
Name a key, and it links itself
Put a task key in the branch, the title, or a closing phrase in the body, and the pull request attaches itself. A bare key mentioned in prose deliberately does not link. The closing verb is the signal, which is what stops every key discussed in a review from attaching.
Live state, on the task
The task grows a linked-pull-request list with review and check state, so whether the work is actually finished is answerable without a second tab. References stay internal, so a client on the same project never sees them.
What shipped, on the overview
Merges, pushes and deployments land on the project overview as an activity feed, with the latest successful deployment pinned in the header. The state of the codebase reads from the same page as the state of the work.
Also included
What else comes with it.
- Adds no tab of its own, and enriches the surfaces you already use instead
- Connect repositories in Settings → Integrations, per project
- Reference pull requests, commits and issues from any task, bug or comment
- Deployment and check failures surface on the overview rather than in an inbox
- Gives agents code context alongside the tracker over MCP
Availability
Opt-in, per project.
GitHub switches on per project in settings. Leave it off and it doesn't exist there: no tab, no placeholder, no empty screen. It's included on every plan, and turning it on never changes your bill.
Every module, on every plan.
Start with the core and switch the rest on as each project asks for them.