We’re building an MCP server into every workspace. Once connected, any MCP-capable agent can search issues, read specs, file new work, and update statuses through the same permission model your team members use. Nothing gets special access: an agent sees the teams it’s been added to and nothing else. The server ships with tools for the common flows first: triage, issue creation, and status updates, with reviews and cycle planning to follow.
Inter now syncs with GitHub in both directions. Copy a branch name from an issue and the issue moves to In Progress; as the pull request is drafted, opened, reviewed, and merged, the status follows along without anyone touching the tracker. The link works for agent branches too, so work started by an agent shows up on the board the same way as everyone else’s.
The diff from every linked pull request is attached to its issue, which makes agent reviews self-contained: the issue holds the instructions, the conversation, and the resulting change in one place. Setup takes a GitHub app install per organization, and you choose which repositories each team can link. Existing automations keep working, so cycle rules and auto-archiving apply to synced issues like any other.
You can now assign multiple agents to the same project. Each agent works from its own queue of issues, opens its own branches, and files its work as separate reviews, so parallel work never collides. Issues marked as blocking are respected across agents: when one agent’s work depends on another’s, it waits and says so in the activity log. The project page shows every agent’s progress side by side, and milestones keep the whole group moving through the stages in order.
