The future of AI in project management, as we see it, is not a smarter chat box. It is agents that do real, routine work inside your projects, people who approve anything that matters, and teams that own the system the whole thing runs on. This post is our opinion, not a forecast, and we will be clear about where we are guessing.
Key takeaways
- Chat was the warm-up. Agents that act are the actual shift.
- Speed is cheap. Trust is the scarce part, so approvals and audit trails decide who wins.
- An AI should never be able to do more than the person it works for.
- The riskiest actions should not be switches. They should not exist for an agent at all.
- If you do not own the workspace, you do not really own the AI working in it.
Why we think chat alone is not the future
Most teams met AI in project management as a text box. You ask a question, you get a paragraph, and then you copy that paragraph into a task by hand.
That is useful, but it leaves the actual work with you.
The next step is obvious once you name it. The AI should be able to comment, create subtasks, start a timer and post a digest, inside the tool where the work lives. That is what an agent is.
Our view in three parts
We build AlianHub around three beliefs. You can disagree with any of them, but they explain every design choice we make.
1. Agents do the routine work
An agent in AlianHub is a member of the workspace with an owner, a run budget and a scope. It is assigned work the same way a person is. An AGENT tag marks it everywhere, so nobody confuses its comment with a colleague's.
We think this is where AI earns its keep: the boring, repeatable jobs. Sorting new requests, posting a weekly digest, triaging bugs, drafting a PRD from a brief.
2. People approve what matters
The second belief is that autonomy should be a dial, not a switch. AlianHub uses four levels, L0 to L3, from "answers and suggests" to "acts on low-risk changes and may run on a schedule".
Anything wider than a low-risk change, like moving a task to another list or assigning work, waits in the AI Inbox for a person. No agent closes a task in any project. A person does.
The goal is not to remove people from projects. It is to remove the busywork that keeps people from thinking.
3. Teams own the system
The third belief is about ownership. AlianHub is free and open source under AGPL-3.0, and it is meant to be self-hosted. Your tasks, your docs and the record of what every agent did live on your server.
Only the model is external. You can bring your own LLM API key, pin a model per agent or follow a workspace routing policy.
What this looks like in practice
Here is how we think the work splits between people and agents. It is the split AlianHub enforces today.
| Kind of action | Example | Who does it |
|---|---|---|
| Read and answer | "What is stuck in the spring launch?" | Agent, always allowed |
| Low risk, reversible | Comment, status within a list, a report | Agent acts at L2 or L3, with Undo |
| Wider change | Move between lists, assign a task | Agent proposes, person approves |
| Close the work | Mark a task Done | Person only |
| Destructive or sensitive | Delete a project, change permissions, billing, deploy | Does not exist for agents |
That last row is the one we care about most. In AlianHub those actions are not disabled settings. They are absent from the action registry, so even a stolen token cannot reach them.
The parts we are less sure about
An honest view includes the open questions. These are the ones we keep debating.
- How far autonomy should go. We stop at L3. We would rather earn trust slowly than lose it once.
- Which model wins. We do not know. That is why the model is swappable.
- How teams will measure it. Approval rate and cost per agent are a start, not the final word.
We would rather say "we do not know" than dress up a guess as a trend.
Bring your own AI is part of the future too
Not everyone wants a new AI. Many people already have Claude, ChatGPT or Claude Code open all day.
AlianHub ships an MCP server, so the AI app you already use can work inside your workspace. It acts as you, sees only what you can open, and changes only what your role lets you change. Wider changes still wait in the AI Inbox, and every change is written to the audit log.
Tip: if your team is unsure about agents, start here. Connecting the AI people already trust is a softer first step than turning on a fleet of new agents. See Connect your AI.
How to do this in AlianHub
You can put this whole view to work in an afternoon:
- Ask first. Open the Ask box, choose "Everything you can open" or one project, and ask "What is stuck in this project?" Ask only reads what you can already open.
- Turn on a team pack. Pick your team's role agents in one click. They all start paused, and the pack can be undone.
- Pick one agent and one job. Open the Agents tab, choose an agent such as the Reporter with its digest skill, and set it to L1 so every change is a proposal.
- Set limits. Give it a daily action limit and a monthly spend cap, and pin a model or follow the workspace routing policy.
- Review in the AI Inbox. Approve or decline its proposals. Decline with a reason, and the agent sees it.
- Promote slowly. Move it to L2, then L3 to run on a schedule, once its proposals are consistently approved.
A business scenario
A small agency runs several client projects. Every Friday, a lead spends the afternoon reading tasks to write status notes, and stuck work often surfaces only at Monday's call.
With a Reporter agent at L3, a digest of what moved, what is stuck and what is at risk is posted on schedule. Proposals to move stuck tasks to Blocked wait in the AI Inbox. The lead reviews instead of writes, problems show up days earlier, and the freed afternoon goes back to client work and new business.
If an AI tool cannot tell you what it may never do, it is not ready to act in your projects.
We wrote a longer AI agent readiness checklist if you want to work through this with your team.
Where to see it
You can see the autonomy ladder, the AI Inbox and the skill library on the AI page. The full rules, including the hard stops and the pause switch for every connected agent, are on the AI controls page.
FAQ
Will AI replace project managers?
We do not think so, and we do not build for it. In AlianHub, agents propose wider changes and a person approves them, and no agent can close a task. The judgement stays with people.
Is this a prediction about the industry?
No. It is AlianHub's view of how AI should work in project management and the reasons behind it. We have tried to label the parts we are unsure about.
Do I need my own AI model to use AlianHub AI?
AI Assist runs on your own LLM API key, and multiple providers are supported. You can also connect Claude, ChatGPT or Claude Code over MCP.
Can I try this without installing anything?
Yes. The live demo has a demo workspace with the AI features. Demo data may reset periodically.
If this view matches how your team wants to work, open the live demo, self-host AlianHub for free, and share this post with the person on your team who keeps asking what AI should actually do.