Project management's week was agent plumbing: MCP surfaces and autonomous triggers replaced net-new features.

The week in project management

The sector's direction this week is not a feature, it is a substrate: MCP and agent plumbing. Of 17 sparks across the 28 products that shipped, most describe the same move — wiring the product into AI agents, or turning its own assistant from something you invoke into something that acts on its own. Atlassian indexed entire codebases into its Teamwork Graph for agents to read; Rize, Notion, Bonsai, MeisterTask and Aha! each shipped a version of the same idea. The second, quieter thread is capacity: Resource Guru and OpenProject both moved the scheduler from recording where work goes to deciding it.

The tell is that the work is unglamorous — triggers, permissions, metering, write-back paths — rather than new surface. Ninety-nine improvements against 17 sparks reads as a sector consolidating: teams are hardening the agent story they started earlier this year rather than opening new fronts. And a large share of the tracked feeds carry no product signal at all — SEO blogs and comparison mills like Everhour, TimeCamp and BigTime — so the real activity concentrates in about a dozen names.

Leaders

Atlassian shipped Code Context, an index of an organization's repositories exposed to Rovo and third-party coding agents through the Teamwork Graph. It is the clearest statement of the week's thesis: sell the context layer agents read from, not the agent itself. Paired with Jira wired in as the system of record for OpenAI's Symphony, Atlassian is positioning its graph under other vendors' agent runtimes rather than beside them.

Rize crossed from asking to delegating. Its August Agent Toolset adds Routines that run scheduled prompts, AI Reports that turn a prompt into recurring client-profitability analysis, and Shared Skills that make one person's prompt into team infrastructure — all callable over API and MCP. The analysis now happens whether or not anyone opens the app.

Notion added a meeting-note-summarized trigger to Custom Agents, so an agent fires the moment an AI Meeting Note finishes. That single event turns agents from something you ask into something that runs on its own, and the permission and metering work shipped in the same window follows directly from it.

Resource Guru shipped Total Hours bookings: commit a number of hours across a date range and the scheduler distributes them around existing commitments, re-fitting when the surrounding schedule changes. It changes what a booking is — an amount of work to be placed rather than a fixed block someone placed — and sits alongside the MCP server it shipped days earlier.

RentRedi put its first model-facing feature at the tenant boundary. The AI Maintenance Helper gives a tenant one clarifying follow-up, then a suggested category, priority and cleaned-up summary; the landlord receives a request already triaged instead of a one-line complaint. It sits exactly where unstructured text enters the system, on top of the Portfolios primitive the rest of the product is now built around.

Wildcards

Tracecat is the sector's outlier: a security-automation (SOAR) platform eight release candidates deep in a beta.52 train. Its beta.51 spark made the Action Gateway mandatory — a breaking change routing every action through one enforced path — and the RCs since have been agent-in-comments plus relentless sandbox tuning, with the socket budget raised RC after RC. Off-pattern in shape and pace, same agent destination as everyone else.

NocoBase runs two release trains — a 2.2.0 beta and a 3.0.0 alpha — in parallel, and wired its AI employees into the plugin system: skills are now built as plugins and scoped to Portals, the container the employees live in. Treating AI Portals as backup-worthy state signals it is building agents as durable, hostable objects, not chat widgets.

Themes that compounded

• MCP is now table stakes: Resource Guru, Rize, Bonsai and MeisterTask all expose their data to AI clients over the protocol this window.
• Agents are shifting from invoked to autonomous — Notion event triggers, Rize scheduled routines, Aha! customer-authored skills.
• Governance and metering ride alongside capability: permission models, credit dashboards and audit paths land in the same releases as the agents themselves.
• Write-back beats read-only: Hive now drives Jira workflow transitions from its list view, turning a mirror into a control surface.
• Capacity planning is the non-AI throughline — Resource Guru's adaptive bookings and OpenProject's resource-management module both add real staffing structure.

Watch this week

The next moves are already implied by this week's data. Atlassian's governance essays point to an admin console for agent access sitting on the same Teamwork Graph; expect it to move from argument to shipped surface. Notion's Workers beta ending is the nearest dated event, with pricing the likely announcement. Rize's Routines should gain triggers beyond a schedule, and Resource Guru's placement engine looks set to extend past Total Hours to other booking types. The through-line to watch: whether these MCP surfaces stay read-only or gain write access — the difference between an agent that reports and one that acts.