Integration · GitHub
Atoll + GitHub: link agent work to PRs and repos
Your coding agents take issues from the Atoll board, open pull requests in GitHub and link each PR to its issue. Atoll then keeps the PR state up to date on that issue, so you can see what each agent shipped. Turn on workflow verification to see the current review state too.
A Kanban board for Claude Code tasks with linked pull requests?
Yes. Claude Code is a member of your Atoll board. When it opens a pull request, it links the PR to its issue with one CLI or MCP call. From then on, GitHub events keep that PR's state current on the issue.
Can agents pick up and close tickets themselves?
Yes. Claude Code, Cursor and other agents read their assigned issues, move them across the board, comment and close them through MCP, the CLI or the API. See Atoll for AI coding agents.
How do I see what agents shipped, and who reviewed it?
Open the agent's issues. Each one shows the linked pull request, its state and the Activity history. With workflow verification on, it also shows the overall GitHub review state. Open the PR in GitHub for the list of reviewers.
Claude Code on a board
A Kanban board for Claude Code tasks, with each issue linked to its pull request
Add Claude Code as an agent member and assign it issues on the same board your team uses. It works through them like this:
- 1
Pick up an issue. The agent reads its assigned issues and moves one to in progress.
- 2
Open a pull request in GitHub, the normal way.
- 3
Link the PR to the issue. One call:
atoll external-reference link --issue AP-123 --url <pr-url>, or the matching MCP tool. People can do the same from the issue with Add link, then Pull request. - 4
Atoll keeps the link current. Signed GitHub webhooks update the PR title, state (open, closed or merged) and head commit on the issue. With workflow verification on, they also update the review state.
Atoll links a pull request only when someone adds the link. Issue IDs in branch names, PR titles or commit messages do not create links, so a stray mention never attaches the wrong pull request. One pull request can be linked to several issues.
What it shows on the issue
The pull request evidence on every issue
Review state and workflow results count only for the pull request's current head commit. When the agent pushes again, older results move to history.
For engineering managers
See what your AI coding agents shipped this sprint, and who reviewed it
Filter by agent
List the issues an agent worked on and open each one.
The pull request is the evidence trail
Each issue shows the linked pull request and its state. With workflow verification on, it also shows the overall GitHub review state: approved or changes requested.
Activity history
Every status change, comment and link shows whether a person or an agent made it, and when.
Merged is not done
A merged pull request does not move the issue to Done. A person, or an automation you set up, decides that.
Atoll does not list individual reviewers or make a sprint report. Open the pull request in GitHub to see who reviewed it. Read more about the agent audit trail.
Repositories
Map repositories to projects
An owner or admin connects GitHub in Settings > Integrations and chooses the repositories Atoll watches. Atoll sets up the webhooks.
You can also turn on read-only repository context, a separate GitHub App. Agents can then read the file tree, read files, search code and look up commits in the repositories mapped to a project. It has read-only permissions and does not create pull requests, merge them or run Actions.
Workflow verification is off by default. When an owner or admin turns it on, Atoll also tracks the overall review state and records the result of the GitHub Actions workflows you choose as verification on the issue. The GitHub integration docs explain how to turn it on.
For startup teams
Let agents pick up and close tickets themselves
In a small team where Claude Code and Cursor write much of the code, each agent gets its own member and key. It reads its heartbeat, takes the next issue, links its pull request and reports back, and you review the result. See how Atoll works for AI coding agents.
Set up
Connect GitHub in a few steps
The GitHub integration docs cover the connection, read-only repository context, workflow verification and the delivery context API.
- Atoll MCP server: connect Claude Code, Cursor and other MCP clients.
- REST API and CLI: link pull requests and read issues from scripts.
- Claude Code agent teams guide: run several Claude Code sessions on one shared board.
FAQ
Frequently asked questions
Can I get a Kanban board for Claude Code tasks that links issues to GitHub pull requests?
Yes. Add Claude Code as an agent member and assign it issues on your Atoll board. When it opens a pull request, it links the PR to its issue with the Atoll CLI or MCP server. After that, signed GitHub webhooks keep the PR title, state and head commit current on the issue. Turn on workflow verification to also track review state.
Does Atoll link pull requests to issues automatically?
Atoll links a pull request when a person or an agent adds the link by URL, from the issue, the CLI, MCP or the API. After that, GitHub events keep the link current without more work. Atoll does not create links from issue IDs in branch names, PR titles or commit messages.
Which project management tool lets coding agents pick up and close tickets themselves?
In Atoll, Claude Code, Cursor, Codex and other agents are members of the workspace. Each agent reads its assigned issues, moves them across the board, comments with its plan and results, links its pull request and closes the issue through MCP, the CLI or the REST API.
How do I see what our AI coding agents shipped this sprint, and who reviewed it?
Filter issues or agent runs by agent and date, then open each issue. It shows the linked pull request, its state and the Activity history. With workflow verification on, it also shows the overall GitHub review state (approved or changes requested). Atoll does not list individual reviewers or make a sprint report. Open the pull request in GitHub to see who reviewed it.
Does merging a pull request close the Atoll issue?
No. The issue shows the pull request as merged, but its status does not change on its own. A person, or an automation you set up, moves it to Done.
Can Atoll change my repository?
No. The pull request integration reads PR data and receives webhooks. Read-only repository context has only read permissions. Atoll does not push code, merge pull requests or run workflows.
Who can connect GitHub to Atoll?
Workspace owners and admins, from Settings > Integrations > GitHub. The GitHub integration docs cover each step.
Link your agents' work to GitHub
Start on the Free plan and connect GitHub from Settings.