AI Project Management: Tools, AI Credits and Agents That Do the Work
AI project management means using AI to plan, schedule, report on and increasingly carry out project work. Today that covers three kinds of tools: AI assistants built into trackers like Asana, Jira and ClickUp, schedulers like Motion that plan your calendar, and coding agents such as Claude Code that take a ticket and finish it.
Most guides stop at the first kind. This one covers all three, what each vendor charges for its AI as of November 2026, and what changed for us once agents started opening and closing tickets on their own. Every price and AI feature below was checked on the vendor's own page on November 3, 2026.
Key takeaways
- Three kinds of AI, three jobs. Assistants summarize and draft inside the tracker, schedulers decide when work happens, and agents do the work itself.
- AI is now billed in credits. Asana, Jira, ClickUp and Motion each meter AI with their own credit pools, and none of them map one credit to one task.
- Agents connect over MCP. Asana, Jira and Linear each run an official Model Context Protocol (MCP) server that Claude Code, Codex or Cursor can use.
- The missing record is cost per ticket. Trackers log that a task changed, not which model changed it, how long it ran or what it spent.
- Proof on close matters most. In our workspace, 18 agent closing notes were too thin to accept and had to be rewritten.
What is AI project management?
AI project management is the use of AI models to handle parts of managing a project: breaking goals into tasks, estimating and scheduling, flagging risk, writing status updates and, with agents, doing the tasks. The project manager still owns scope, priorities and sign-off.
The term covers very different products. A summary button in a task tool and an agent that ships a pull request both get called "AI project management", which is why most tool lists feel like they compare apples and forklifts.
What can AI do in project management?
AI handles six jobs well today, and each one belongs to a different kind of tool.
| Job | What the AI does | Usually done by |
|---|---|---|
| Planning | Breaks a goal or brief into tasks and subtasks | Assistant or agent |
| Scheduling | Places tasks around deadlines, meetings and capacity | Scheduler |
| Resource balancing | Flags people with too much assigned this week | Assistant |
| Risk flags | Spots overdue dependencies and slipping dates | Assistant |
| Status reporting | Drafts weekly updates from task activity | Assistant |
| Doing the task | Writes the code, the doc or the fix, then updates the ticket | Agent |
The first five save a project manager hours a week. The sixth changes who's on the team, which is why the rest of this guide spends time on agents.
What are the types of AI project management tools?
There are three, and you probably need to know which one you're buying before you compare prices.
| Type | What it does | Examples | Who runs it |
|---|---|---|---|
| Assistant in the tracker | Summarizes tasks, drafts updates, suggests subtasks, answers questions about the project | Asana AI Studio, Atlassian Rovo, ClickUp Brain | Your tracker vendor, on its credits |
| AI scheduler | Plans when each task happens around meetings and deadlines | Motion | The scheduler, on your calendar |
| Agent that does the work | Takes a ticket, writes code or content, updates the ticket, closes it | Claude Code, OpenAI Codex, Cursor, plus agents assigned inside Asana, Jira or Linear | An agent, connected over MCP or API |
The first two make a project manager faster. The third changes who sits in the assignee column. That's where the tooling is thinnest.
Which AI project management tools are worth a look?
These six cover the field for software and business teams. Prices are list prices from each vendor's pricing page as of November 2026.
| Tool | Best for | AI on offer | How AI is billed (Nov 2026) |
|---|---|---|---|
| Asana | Cross-team plans, portfolios, request intake | AI Studio workflows, AI Teammates you assign tasks to | AI Studio credits per billing account: 50K on Starter, 75K on Advanced, 200K on Enterprise each month; Teammates 5 requests per user a month |
| Jira | Software teams running sprints | Rovo chat and agents, assignable on work items | Rovo credits per user each month: 25 Standard, 70 Premium, 150 Enterprise, pooled |
| ClickUp | Teams that want docs, tasks and chat in one place | ClickUp Brain across tasks and docs | Credits per user each month, pooled: 1K Core, 1.5K Business, 3K Enterprise; extra credits about $10 per 10K |
| Linear | Fast software teams | Delegate issues to agents from its integrations directory | Linear says agents are not counted as billable seats |
| Motion | Individuals and small teams who want auto-scheduling | AI task planner, calendar, docs | Credits per seat: 7,500 on Pro AI, 15,000 on Business AI each month |
| Jenzo | Teams where coding agents do much of the work | Agents open, work and close tickets over MCP; each ticket records agent time, tokens and cost | n/a (tracks the agent's own token spend) |
Wrike, monday.com and Notion also ship AI features and show up on most lists; we left them out of the table because their AI is assistant-style, like Asana's and ClickUp's. Seat prices vary more than AI allowances do. As of November 2026, Asana lists $10.99 to $24.99 per user a month on annual billing for Starter and Advanced, Jira about $8.50 to $15.50 for Standard and Premium, ClickUp $9 to $17 on yearly billing for Core and Business, and Motion $19 to $29 per seat.
How does AI project management work in practice?
In practice, it runs as a loop: the AI reads project data, proposes or takes an action, and a human approves the parts that matter. The difference between tools is how much of that loop the AI owns.
- Read. The AI pulls tasks, comments, dates and owners from the tracker.
- Suggest. It drafts a plan, a status update, a risk list or a schedule.
- Act. Assistants usually stop at suggesting. Agents create subtasks, change status, write code or post comments.
- Prove. Someone, or something, checks the result and closes the item with evidence.
Step 4 is where teams get burned. An assistant's bad summary costs a few minutes. An agent that marks 20 tickets done without proof costs a week of re-checking.
How do AI agents connect to project management tools?
Through the tracker's API, or more often now through its Model Context Protocol (MCP) server. MCP is an open standard (modelcontextprotocol.io): you give Claude Code a URL, sign in once, and it can read and edit your tasks without anyone writing integration code.
Asana, Atlassian and Linear each host one:
| Tracker | Official MCP endpoint | Sign-in |
|---|---|---|
| Asana | https://mcp.asana.com/v2/mcp |
OAuth |
| Jira (Atlassian Rovo MCP) | https://mcp.atlassian.com/v2/mcp |
OAuth 2.1; calls use Rovo credits |
| Linear | https://mcp.linear.app/mcp |
OAuth; read-only at /mcp/readonly |
Asana's MCP docs list Claude Code, Codex, Cursor and VS Code by name. One date to note: Asana's old beta URL, https://mcp.asana.com/sse, shuts down on November 5, 2026. On the Jira side, read the cost section of Atlassian's MCP guide before you roll it out:
"credit usage is per call"
In Claude Code, each one is a single command (Claude Code's MCP docs have the flags):
claude mcp add --transport http asana https://mcp.asana.com/v2/mcp
claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp
claude mcp add --transport http linear https://mcp.linear.app/mcp
We wrote setup guides with agent rules for Jira MCP and Linear MCP.
Agents can also be assignees now. In Jira you pick an agent on a work item, including partner agents such as GitHub Copilot's coding agent. Asana describes its AI Teammates as:
"Prebuilt AI agents that work alongside your team inside real workflows"
What does AI project management cost?
You pay twice: once in the tracker's AI credits and once in the model tokens your agents burn. Tracker credits are easy to read off a pricing page. Token spend is the cost that surprises teams, because no tracker shows it per task.
One real session from our own workspace: Claude Code on claude-opus-5-5 worked a ticket for 3 minutes and used about 2.4 million input tokens and 160,000 output tokens. Multiply by a few hundred tickets a month and you'll want a per-ticket number before you set a budget.
The second lesson came from a guard rail. One of our agent sessions ran until it hit a 4-hour cap and was stopped automatically. Without that cap, it would have kept counting time against a ticket nobody was watching.
A quick way to estimate your own cost:
AGENT COST ESTIMATE (per month)
tickets handled by agents ............ T
average input tokens per ticket ...... I (measure 10 real tickets)
average output tokens per ticket ..... O
input price per 1M tokens ............ Pi (your model's price page)
output price per 1M tokens ........... Po
model cost = T x (I x Pi + O x Po) / 1,000,000
credits left = credits included in your plan - credits used this month
What changed when agents started running our tickets?
The tracker had to start recording things a human-only tracker never needed. In October we moved 3,528 tickets and 2,614 comments out of ClickUp over its API, keeping original dates and comment authors. From October 17 to November 3, 2026, 316 tickets were created natively, most of them by agents, and 157 of those are done.
Three things stood out:
- Agents write thin closing notes. We had 80 tickets closed with proof attached, and 18 closing notes were refused as too thin and rewritten. Without a gate, those 18 would have read "done" with nothing behind them.
- Agents make decisions people need to see. Our agents logged 7 decisions for human approval, such as a library choice or a scope cut. A person rejected one. That rejection would have been invisible in a comment thread.
- Plans survive only if they live on the ticket. Agents moved plan steps 44 times across 3 plan tickets. When a long chat was compacted, the plan on the ticket was what let the agent pick up where it stopped.
Jenzo, which we make, records all three. Agents open, update and close tickets over MCP or the API; every ticket shows which agent and model worked it, for how long, and its tokens and cost; and a ticket can't close without a link or a real closing report. Humans approve decisions and unblock agents. If your team doesn't use coding agents yet, a tracker with a good assistant will serve you better.
What are the limitations of AI in project management?
AI is good at drafting and at repetitive updates, and weak at judgment calls, stakeholder politics and anything it can't see in the data. Each limit has a practical control.
| Limitation | What it looks like | Control |
|---|---|---|
| Wrong or invented details | A status update cites a task that slipped last week | AI drafts, a person sends |
| Missing context | The plan ignores a dependency agreed in a meeting | Write decisions on the ticket, not in chat |
| Silent changes | An agent edits 30 tasks under your account | Start agents read-only; log every write |
| Unclear cost | The credit pool runs out mid-month | Measure 10 tickets before rollout |
| Closed without proof | "Done" with no link or report | Require a link or closing report to close |
| Over-trust | Reviews get skipped because the summary looks clean | Spot-check a sample every week |
Will AI replace project managers?
No. It takes over the clerical half of the job first: status reports, meeting notes, grooming the backlog, moving dates when something slips.
Someone still has to decide what matters this week, say no to a stakeholder and sign off on a risky change. On our own team, that person now spends a chunk of each day reading agent closing reports and answering the questions agents leave on tickets. Chasing people for updates has mostly gone away.
AI project management tool scorecard (copy this)
Score each tool 0 to 2 per line. Rule out any tool that scores under 10.
AI PROJECT MANAGEMENT SCORECARD Tool A Tool B
1. AI drafts updates from real project data [ ] [ ]
2. Agents can take an assignment in the tool [ ] [ ]
3. Official MCP server or API for Claude Code/Codex [ ] [ ]
4. Read-only mode for agents [ ] [ ]
5. AI pricing is published (credits per plan) [ ] [ ]
6. Agent time and tokens visible per task [ ] [ ]
7. Closing a task needs proof (link or report) [ ] [ ]
8. Human approval step for risky agent actions [ ] [ ]
9. Every AI action is logged and attributable [ ] [ ]
10. Non-technical teammates can use it day one [ ] [ ]
TOTAL (out of 20) ___ ___
30-day AI project management pilot checklist
- Pick one team and one project with 30 to 60 open tasks.
- Write down today's baseline: hours on status updates, tickets closed per week.
- Turn on the tracker's assistant; connect one agent read-only over MCP.
- After a week, give the agent write access on one ticket type only (for example bugs labeled
agent-ok). - Require a link or closing report on every task the agent closes.
- Record tokens and time for 10 agent tickets; run the cost estimate above.
- Review every agent decision that touches scope, data or customers.
- On day 30, compare against the baseline and decide: expand, keep or drop.
Which AI project management tool should you choose?
| If you are... | Start with | Why |
|---|---|---|
| A business team planning across departments | Asana | AI Studio and AI Teammates inside an easy tool |
| A software team on sprints | Jira | Rovo agents on work items, deep agile features |
| A team that wants one workspace for docs and tasks | ClickUp | Brain across tasks and docs, pooled credits |
| A fast software team that delegates to agents | Linear | Agents don't take billable seats |
| A solo operator drowning in calendar | Motion | Auto-scheduling around meetings |
| A team where coding agents do much of the work | Jenzo | Agent time, tokens, cost and proof on every ticket |
More guides are on our blog.
FAQ
Which AI tool is best for project managers?
It depends on the team. For cross-functional business projects, Asana's AI Studio and AI Teammates are the most rounded. For software teams, Jira with Rovo agents, or Linear with delegated agents. For personal scheduling, Motion. If coding agents like Claude Code already do much of your work, choose a tracker that records each agent's time, tokens and proof on the ticket.
How does AI project management work?
The AI reads tasks, dates, owners and comments from your tracker, then drafts plans, status updates or schedules. Agents go further: they take an assigned ticket, do the work, update the ticket and close it. Teams keep a person in the loop for priorities, risky decisions and sign-off, and require proof such as a link or closing report before anything is marked done.
Can Claude or ChatGPT manage projects?
They can do project work but they need a tracker to hold state. Connected to Asana, Jira or Linear through MCP, Claude Code or Codex can read tasks, create subtasks, update status and post comments. On its own, a chat forgets the plan once the conversation ends, so keep the plan, decisions and handoff notes on the ticket.
How much does AI project management software cost?
As of November 2026, seat prices run about $9 to $30 per user a month for paid tiers of Asana, Jira, ClickUp and Motion, with AI metered in credits on top or included in an allowance. Agents add model costs: one of our 3-minute sessions used about 2.4 million input tokens. Measure 10 tickets before you budget.
What are the limitations of AI project management?
AI can invent details, miss context agreed outside the tool, make silent changes under your account and spend credits faster than planned. It is weak at judgment, prioritization and stakeholder trade-offs. The controls are simple: start agents read-only, log every write, require proof to close and keep humans on approvals.
What are the types of AI project management tools?
There are three. Assistants built into trackers, such as Asana AI Studio, Atlassian Rovo and ClickUp Brain, summarize and draft. Schedulers such as Motion decide when each task happens. Agents such as Claude Code, Codex and Cursor take a ticket and do the work, connected to the tracker over MCP or an API.
From our own experience
The ClickUp export took an afternoon. Getting agents to leave a trail a person could check took most of October: 18 closing notes sent back, one decision rejected, one session cut off by the 4-hour cap. If you give an agent its first ticket next week, set up proof on close and a place to log its decisions before you do.
Let your agents keep the board.
Claude Code, Codex and Cursor open their own tickets, log hours and tokens, and close them with the commit.
Connect your agent