Project tools ship the agent, then race to ship the governance around it

The week in project-management

The pattern this week is one move repeated across every price point: the project tool is being made callable by an outside agent, then wrapped in the permissions that make that safe. Atlassian put Rovo inside Microsoft Copilot and Teams so work lands in Jira without anyone opening Jira; Resource Guru and Aha! both shipped MCP surfaces the same week Rize exposed an entire agency operating model through its own. The interesting half is no longer the agent, which everyone now has, but the machinery underneath it — role scoping, kill switches, audit trails, confirmation before a destructive write.

That governance thread is what separates the week's serious releases from the demos. Tability gave admins a switch to turn agents off and made AI Mode ask before it deletes; NocoBase back-ported an access-control bypass fix across two branches rather than holding it for the next major; SmartSuite started logging which human pressed the button that fired an automation. The tell is consistent. These products are past demonstrating that an agent can act and into the harder problem of proving, after the fact, exactly what it did and on whose authority.

Leaders

Atlassian leads on two sparks. Rovo now searches Atlassian context and fires Jira actions from inside Copilot and Teams, and the same week a Teamwork Graph connector pulled Teams conversations back the other way. Atlassian is separating where work is discussed from where it is recorded and claiming the second; Jira Planner and the move of budgeting into Jira hand the graph more structured data to act on.

Rize turned a personal time tracker into an agency operating system in a single release — profitability by client and project, resourcing and utilisation, invoicing, and the org roles and finance grants that had to ship alongside them. Every surface reached the API and MCP at the same moment as the app, which is the real point: Rize keeps monetising the same automatically-captured time one layer higher each time.

Resource Guru shipped two sparks pointing the same direction. Total Hours bookings change what a booking is — a quantity of work the scheduler fits around everything else, rather than a block a person dragged into place — and an MCP server makes the same schedule answerable by an assistant. Both aim the product at resolving intent instead of storing arrangements.

Aha! sparked MCP connectors that let its Elle assistant reach GitHub, Linear and Jira from inside the product, ending the stretch where Elle could only reason over Aha!-native data. Aha! keeps pairing each generative capability with a constraint — approved connectors, design systems, skills that encode a team's standards — and positions against the standalone builders on governance rather than raw speed.

SmartSuite added a Conditional Logic action, nestable two levels deep with its existing loop, which turns the automation engine from a trigger-action list into something with real control flow. Paired with Slack notifications that write back to a record and per-user attribution on button clicks, the buyer being served is plainly the administrator who has to defend an audit trail.

Wildcards

Redmine is the counter-example to the whole AI story: twenty years old, no assistant, and this week one maintenance release carrying five security fixes backported across three supported branches at once. For a large installed base, the product news that matters is not a new agent but whether last quarter's major release is now safe to adopt.

Scoro barely registers on velocity — its feed publishes headlines with almost no body — but it made the week's most distinct move: automatic triggers that let its ELI assistant fire on events rather than wait to be asked. After a year spent making the assistant reachable, this is the first change to when it acts, not who can reach it.

Themes that compounded

• MCP went from novelty to table stakes: Atlassian, Resource Guru, Aha!, Rize, Nifty, Ellie Planner and ClickUp all shipped or extended a server this window.
• Governance shipped in lockstep with capability — kill switches, role scoping, write confirmations and click attribution appeared wherever agents can now write.
• Security work was carried across maintained branches rather than deferred, in both NocoBase's ACL bypass fix and Redmine's three-branch backport.
• Passive or declared data is being converted into decisions: Rize's tracked hours into margin, Resource Guru's Total Hours into a solved schedule.
• The buyer keeps moving up-market — org roles, finance grants and audit trails all point at firm-level rather than individual purchase.

Watch this week

Most of what landed is a first move in a longer arc, and the follow-through is legible. Tability and SmartSuite both left obvious next constraints to lift — more object types AI Mode can write, SmartSuite's two-level nesting cap and its missing error handling for a branch that fails mid-loop. Rize modelled contracts and cost rates but stopped short of forecasting, and Resource Guru's auto-fitting covers new bookings but not rescheduling after a conflict. The thing to watch is whether the governance scaffolding keeps pace with the write access: the products that shipped kill switches and attribution this week are the ones to trust with the next capability, and the ones that shipped the capability without it are where the risk now sits.