Atlassian and Hive lead a project-management week defined by agents, MCP servers, and human-in-the-loop guardrails
The week in project-management
The loudest move came from Atlassian, which landed three substantial releases inside 48 hours. Jira Automation can now trigger GitHub Copilot, Cursor, or Claude Code as a step in any rule, so a ticket that meets defined conditions hands work to a coding agent instead of a person prompting one. The Forge LLMs API went generally available, giving any app developer model access as a platform primitive. And Trello picked up seven AI features at once, shipped to every paid tier rather than reserved for the top one. The through-line is Atlassian building the layer beneath other people's agents rather than matching them feature for feature: Automation becomes the dispatcher, Forge becomes where third-party apps get inference, and Rovo becomes the retrieval surface over documents Atlassian does not host.
The other velocity leader, Hive, spent its week going deep on two modules rather than wide across the product. Its Buzz assistant now decomposes a complex request into focused sub-tasks and works the independent parts in parallel, while anything consequential stays in the main thread for a human to approve. The more telling detail sits in AI Proofing: a reference-document picker that had been removed is back, with automatic selection now an explicit opt-in. That is an AI feature walked back toward human control, and across the sector this week that instinct showed up again and again.
Leaders
Atlassian posted five sparks, the most in the sector. Beyond the coding-agent dispatch and the Forge GA, it rebuilt Rovo Chat around a single long-horizon reasoning engine, discarding the multi-agent router that used to fan work out to separate Jira, Confluence, and Slack agents. Shipping Trello's AI to all paid tiers reads as a decision to treat AI as table stakes, not an upsell.
Hive paired three sparks with a dozen improvements. Alongside Buzz, its AI Proofing now runs later proof rounds as an audit rather than a fresh review, walking each prior human comment and judging whether the new version addressed it, and it can learn a durable rule from a reviewer's annotation. Underneath the AI work, a 13-week resource-estimates grid separates planned capacity from committed assignments.
Notion put nearly every release behind one construction: Custom Agents, the Workers that run their code, and the surfaces they reach. Notion 3.6 pulls agents that live in CLIs, IDEs, and other vendors' apps onto a shared board the whole team can assign work to, and a Meeting-note-summarized trigger lets an agent start on its own without anyone opening a chat. Workers gained shared access and a metered usage line, which is the shape of a platform.
NocoBase is running two release trains at once and building an AI-employees layer inside a no-code platform. Its standout is an embeddable AI chat block with scoped conversations plus frontend AI tools callable from JavaScript blocks, so an app builder can drop an agent onto a page and wire it into the app's own scripting rather than sending users elsewhere. A published guide for defining AI-employee tools and skills as plugins turns that layer into an extension point.
Resource Guru shipped its first MCP server, letting an AI client query bookings, availability, and utilisation in plain English with no report builder in between. Its other releases this window are view-layer control, colour-coding by custom field, a configurable Projects view, and a digest of unassigned placeholder work, all pointing at a product betting its value sits in the scheduling data, not the interface around it.
Wildcards
Nifty spent most of 2026 in a self-declared rearchitecting pause, shipping little beyond bug fixes, then ended it on July 27 with an MCP server that hands outside assistants read access to projects, tasks, and docs, and write access with permission. The pitch is not a sidebar chatbot but agents from different collaborators sharing one workspace context, the first thing its AI-first rebuild has produced.
Nimbus, now trading as FuseBase, is drifting from a document-and-portal store toward a place where agents build software. FuseBase Flow wraps phases, slices, and review gates around AI coding, aimed at client-facing businesses whose AI-built apps stall before they ship. Its marketing has not caught up, still chasing buyers shopping for a Notion or Quip replacement.
Themes that compounded
- MCP as the default new surface: Resource Guru, Nifty, MeisterTask, Bonsai, and Process Street all exposed their data to assistants this window, joining Trello's MCP from Atlassian.
- Human-in-the-loop as a design stance: Hive walked automatic reference selection back to opt-in and kept commitments with a human, while Aha! moved its AI Builder past generation into virtual-user testing that critiques its own output.
- Agents as platform infrastructure, not chat widgets: Notion Workers and NocoBase AI employees are both being built with access models, metering, and plugin extension points.
- Trust boundaries arriving with autonomy: Tracecat made its Action Gateway mandatory and stopped forwarding auth to user MCP servers in the same candidates that expanded what its agents can do.
- Governance-first AI for regulated buyers: SmartSuite centralized LLM keys into an admin-controlled AI Control Center and shipped effective-permission maps aimed at ITSM, GRC, and PMO teams.
Watch this week
The MCP wave is now broad enough that a server is becoming the entry ticket rather than the headline; the next differentiator is what agents are allowed to do once connected, and who approves it. Watch whether Atlassian's coding-agent dispatch and Notion's trigger-started agents hold up outside launch demos, whether Hive's opt-in walk-back is an isolated correction or a pattern others copy, and whether Nifty's rearchitecting bet converts a long quiet stretch into sustained shipping.