Move a card and the GitHub issue gets created and assigned. Open a pull request and the card moves to Review. Everything you did lands in a work log your AI agent can read.
01
A linked GitHub issue is created for it, so the work is tracked where the code lives.
02
Assign a teammate from the board, hand it to GitHub Copilot, or skip for now.
03
Reference the issue with Fixes #123 and the card moves to Review on its own.
04
Cards you handed to Copilot get a Copilot pull request review requested automatically.
Import open issues as cards, create or link issues from cards, and keep status in step through webhooks.
Cards stand on their own. Link one to GitHub when it becomes code work, and keep the rest of the plan on the same board.
Each card move lands in your work log. Tag entries with #hashtags and export for standups or client invoices.
Post to a Discord channel when cards move, get created or hit their due date.
An honest comparison, based on GitHub's documentation as of October 2026.
| Feature | What the HELL have i DONE | GitHub Projects |
|---|---|---|
| Price | $4 / user / month after the free tier | Included with GitHub |
| Starting work | Moving a card to In Progress creates the issue and assigns a teammate or Copilot | Built-in workflows set status when items are added; assignment happens on the issue |
| Pull requests | A PR that references the issue moves the card to Review; Copilot review for Copilot cards | Built-in workflows set Done when a PR merges or an issue closes |
| Views | Kanban boards | Board, table and roadmap views with custom fields |
| Work log | Every card action logged automatically, taggable and exportable to CSV/JSON | Per-issue timelines |
| AI agents (MCP) | Boards, cards, work log and project docs, with scoped tokens | GitHub's MCP server has an opt-in Projects toolset for reading and updating items |
| Docs | Markdown docs per project, plus browsing the Markdown files in linked repos | Repository Markdown and wikis |
| Chat notifications | Discord webhooks when cards move, get created or hit their due date | GitHub notifications, plus chat apps you install |
Authorize with OAuth. You can connect more than one GitHub account.
In board settings, connect the repo and turn on pull request automation.
Pull in open issues as cards, or start fresh and create issues as cards move.
We'd rather you pick the right tool than churn in a month.
Yes, once webhooks are set up on the repository: changes in GitHub show up on the board and card changes go back to GitHub. Without webhooks you can still import issues one way.
No. Cards are native to the board. Create or link an issue when a card turns into code work, and keep design, ops or client tasks on the same board without cluttering your repo.
When you move a card to In Progress you can assign it to GitHub Copilot. The linked issue is assigned to the Copilot agent, and when its pull request opens a Copilot review is requested automatically.
Yes. The built-in MCP server lets Claude, Cursor and other MCP clients list boards, read, create and move cards, log work and fetch project docs, with tokens limited to the tools you allow.
Free for 1 project and 2 boards. The paid plan is $4 per user per month for unlimited projects, boards and collaboration.
Connect a repository and import your open issues in a couple of minutes.
Get started — it's free