Agentic coding finally clicked for a lot of engineers when they stopped giving the model a chat box and started giving it a board. Tasks pulled from “Ready”, work done in a branch, PR opened, ticket moved to “In Review”. It works because the board is the same shape a junior engineer would expect: a queue, a status, a definition of done. The eight best apps for AI agent kanban boards below are the ones that actually let an agent read, write, and move tickets through an API that does not break every release.
The picks span fully hosted SaaS, self-hosted open source, and the few that occupy both ends. Each section explains the API story, the price, and where the app falls short when an agent is the user.
What to look for in an agent-friendly board
The features that matter for agentic use are not always the ones the marketing page leads with:
- Stable, documented API. The agent needs to list tickets, change status, comment, and link PRs. REST or GraphQL, just keep it stable.
- Webhook coverage. The agent should react to “ticket moved to In Progress”, not poll every minute.
- Branch and PR linking. First-class GitHub and GitLab links cut a lot of glue code.
- Custom fields. An “agent assignee” or “model used” field saves a lot of confusion downstream.
- Permissions. A scoped service account that can only touch what it needs to.
- Self-host option. For code work that lives behind a VPN, the board often needs to live there too.
- Audit history. Knowing which change came from which model on which date matters for retrospectives.
Quick comparison
| App | Best for | Free plan | Starting price/mo | API story |
|---|---|---|---|---|
| Linear | Engineering teams | Yes, generous | Around $8 per user | GraphQL, excellent docs |
| Plane | Open-source Linear-alike | Yes, self-host | Around $5 per user (cloud) | REST + GraphQL, open source |
| Trello | Casual boards | Yes | Around $5 per user | REST, mature, easy |
| ClickUp | Full PM suite | Yes | Around $7 per user | REST, broad coverage |
| Jira | Enterprise standard | Yes (free for 10 users) | Around $7.53 per user | REST + webhooks, very stable |
| Notion | Docs and boards together | Yes | Around $10 per user | REST + database API |
| Vikunja | Self-hosted with API | Yes | Free (self-host) | REST, open source |
| OpenProject | Self-hosted enterprise | Yes (Community Edition) | Free (Community) | REST, open source |
The apps
1. Linear, the cleanest API for agents
Linear’s GraphQL API is the cleanest in this list. Schemas are stable, the docs hold their shape across releases, and the webhook coverage is broad. Agents can list tickets in a project, comment, change status, set assignees, and link PRs without surprises. The free plan is generous and covers most small teams without a credit card.
Where it falls short: the issue model is opinionated. Custom workflows beyond the standard Backlog → Todo → In Progress → In Review → Done sometimes feel like swimming upstream.
Pricing: Free for small teams. Standard plan around $8 per user per month, with higher tiers for SCIM, audit log, and enterprise SSO.
Platforms: macOS, Windows, Linux desktop apps plus iOS, Android, and a web app.
Download: Linear
Bottom line: The best default for engineering teams running coding agents against a board. The API ergonomics carry the pick.
2. Plane, the open-source Linear alternative
Plane is the open-source project that most resembles Linear in feel. The hosted cloud is fully managed, and the Community Edition self-hosts cleanly via Docker. The REST API and webhooks are sufficient for agent work, and the project moves fast on community feedback.
Where it falls short: GraphQL coverage is partial. A few corners of the UI still feel like they are catching up with the Linear baseline.
Pricing: Free Community Edition (self-host). Cloud plans start around $5 per user per month.
Platforms: Web app and Docker self-host. Desktop apps for macOS and Windows.
Download: Plane
Bottom line: The right pick if you want the Linear-shaped workflow without the Linear bill and with the option to self-host.
3. Trello, the easy starting point
Trello’s REST API has been stable for over a decade, and the simplicity of cards-and-lists is well suited to small agent experiments. Power-Ups extend the surface, and the recently-improved AI Power-Ups handle summary and auto-prioritize tasks. The free tier supports unlimited cards on up to 10 boards.
Where it falls short: deeper PM features (custom fields, multi-project rollups) live on paid tiers. Performance on very large boards has improved but still lags the engineering-focused tools.
Pricing: Free tier with caps. Standard starts around $5 per user per month.
Platforms: macOS, Windows, Linux (via web wrapper), iOS, Android, and a web app.
Download: Trello
Bottom line: The right pick for personal projects, side experiments, and small teams where the shape of work is genuinely card-shaped.
4. ClickUp, the maximalist toolbox
ClickUp’s pitch has always been “one app for everything”, and the platform genuinely supports many workflows in one place: tasks, docs, whiteboards, sprints, time tracking. The REST API is broad, and the AI features are now reasonably integrated into the task workflow. Agents can move tickets, run searches, and post comments via the API.
Where it falls short: the UI is dense and onboarding curves are steep. Some teams find the “one app for everything” pitch becomes “one app that does many things in a mediocre way”.
Pricing: Free with caps. Unlimited starts around $7 per user per month.
Platforms: macOS, Windows, Linux desktop apps plus iOS, Android, and a web app.
Download: ClickUp
Bottom line: Worth a look if you want one app for tickets, docs, and sprint planning. Pair only with agents that have permissions scoped tightly.
5. Jira, the enterprise default
Jira is the default in larger organizations, and the API is the most stable surface in this list (10+ years of guarantees behind it). Webhooks, automation rules, and the new Atlassian Intelligence features integrate cleanly. The free tier (up to 10 users) is enough for small open-source projects.
Where it falls short: UX has always been heavier than Linear or Plane. The cost ramps significantly with seat count.
Pricing: Free for up to 10 users. Standard starts around $7.53 per user per month.
Platforms: Web app, mobile apps, and a Confluence-integrated workspace.
Download: Jira
Bottom line: If the team already uses Jira, agents fit in cleanly. Do not migrate to Jira just for agent work, the lighter tools are easier to point an agent at.
6. Notion, the docs-and-boards hybrid
Notion’s database API is sufficient for treating a database view as a kanban. The agent can read tickets, write comments, change status, and link to the page itself. The strength is the document context around each ticket; the writeup, decision log, and PR review can all live next to the card.
Where it falls short: pure kanban performance on large boards is weaker than Linear or Jira. The API rate limits matter for high-volume automation.
Pricing: Free for personal use. Plus plan around $10 per user per month.
Platforms: macOS, Windows desktop apps plus iOS, Android, and a web app.
Download: Notion
Bottom line: A good fit when the documentation around each ticket is as important as the ticket. Less good when you need fast, dense ticket movement at scale.
7. Vikunja, the self-hosted underdog
Vikunja is a small, fast, open-source PM tool with a clean REST API and a Docker deploy that runs on a single small VM. Lists, kanban, gantt, table, and calendar views all sit on the same data model. The 2026 releases tightened the API and added webhook support that makes agent work workable.
Where it falls short: a smaller community than Plane, fewer third-party integrations, and the UI is functional rather than polished.
Pricing: Free, open source under GPL.
Platforms: Web app and Docker self-host plus iOS and Android apps.
Download: Vikunja
Bottom line: The right pick for a small self-hosted team that wants a stable API to drive from a script or agent.
8. OpenProject, the enterprise-grade open source
OpenProject Community Edition self-hosts cleanly and ships with a REST API, work packages, agile boards, gantt views, and a permission model serious enough for regulated environments. Agent use is straightforward through the API; webhooks cover state changes.
Where it falls short: heavier to deploy than Vikunja or Plane. UI carries more enterprise baggage than the others in this list.
Pricing: Free Community Edition (self-host). Cloud and Enterprise plans available.
Platforms: Web app on self-hosted infrastructure.
Download: OpenProject
Bottom line: The right pick for organizations that need an enterprise-grade self-hosted board with auditability and SSO.
How to pick the right one
- If you want the cleanest API to point an agent at, pick Linear.
- If you want Linear’s feel as open source, pick Plane.
- If you want a stable API with the broadest enterprise footprint, pick Jira.
- If you want everything in one app, pick ClickUp.
- If you want docs and tasks together, pick Notion.
- If you want a tiny self-hosted board with a good API, pick Vikunja.
- If you need enterprise-grade self-host, pick OpenProject.
Most teams settle on Linear or Plane for the engineering work and keep their existing PM tool for the rest of the company.
FAQ
What is the best kanban board for AI coding agents?
Linear, for the GraphQL API and webhook stability. If you need self-host, Plane is the closest open-source equivalent and works the same way at the API level.
Can I use Jira with an AI coding agent?
Yes. Jira’s REST API is one of the most stable in the industry, and automation rules combine well with agent webhooks. The trade-off is UX heaviness; for net-new projects, Linear or Plane are lighter.
Is there a fully open-source kanban with an API that fits agent workflows?
Plane, Vikunja, and OpenProject all qualify. Plane is the closest to Linear in feel, Vikunja is the lightest to self-host, OpenProject is the most enterprise-ready.
How do I keep an agent from running away with a board?
Use a scoped service account, lock it to a single project, deny destructive permissions (delete card, archive board), and require a webhook-driven approval gate before transitioning cards into terminal states. Audit the log weekly while the workflow is new.
