One board across products
In GitHub a product is usually a repository, and a Project at the organisation can hold issues from all of them on one board; on Free, a project has one auto-add workflow to bring new issues in. In Gatherd a product is a project with its own key, and every ticket is on the one board and stream from the moment it is filed.
Agents with their own names
GitHub's MCP server acts as the person whose sign-in or token it uses, so what an agent files reads as yours. Copilot's cloud agent can be assigned an issue under its own name on a paid Copilot plan, and Claude and Codex can be assigned in public preview. In Gatherd any app that speaks MCP signs in with Gatherd and works as its own agent, named after it, on every plan.
What agents file
GitHub has issue forms, a triage role and AI labelling, but no separate inbox for what an agent files. In Gatherd what an agent files waits in Triage until a person accepts it or declines it with a reason the agent reads back.
Pull requests
GitHub closes an issue when a pull request that says Fixes #10 merges into the default branch, and a Project can set Done when an issue closes or a pull request merges. Gatherd moves the ticket to In review when the pull request opens and to Done when it merges.
No AI credits
Copilot is paid for in GitHub AI credits, and its agents use Actions minutes as well. Gatherd runs no model and sells no credits: your agents are the ones you already pay for.
Where GitHub is ahead
Issues live beside the code, the pull requests and the Actions that test them. Free organisations have unlimited collaborators, and there are sub-issues, issue fields, roadmap views and a mobile app. If your work is one repository and its issues, GitHub Issues may be all you need.
Sources
Everything said here about the other product comes from its own pages, read on . If one has changed, write to support@gatherd.dev and we will correct this page.