Project tools stopped competing to be the agent and started competing to be the system agents write into.

The week in project-management

The defining move this week was positional. Rather than shipping their own chat assistant and calling it AI, the sector's most active products spent the window making themselves the durable place other companies' agents operate. Atlassian set the tone with four sparks in four days, led by naming Jira the system of record for OpenAI Symphony, the orchestration layer behind Codex. That is the first outside orchestrator persisting its agent state into Jira, and it lands on top of a Summer 2026 Jira release whose center of gravity is the agent-facing surface — expanded MCP capabilities and a generally available Teamwork Graph CLI — not the human UI.

The same instinct showed up one tier down, in smaller products with narrower scopes. Tability, NocoBase, and Notion all shipped work that treats the agent as an addressable actor the platform hosts and governs, and each kept a human in the approval seat. The pattern that separates this week from generic AI feature-drops is the guardrail arriving in the same release as the reach: delegation with review gates, skills scoped per actor, execution tools fenced by isolation work. The sector is converging on hosting and recording agent execution rather than authoring it.

Leaders

Atlassian was the clear lead. Beyond the OpenAI Symphony tie-up, it opened Forge container services to production and the marketplace — removing the function-runtime ceiling on what a third party can build inside Forge — and published the run-up guidance for Connect end of support, leaving Forge as the sole runtime for third-party code just as external agents arrive to use it. Read together, the four sparks describe one platform bet: Jira as the state layer beneath other vendors' coding agents.

Tability shipped a single dated train on August 6 that reads as the clearest small-vendor version of the same idea. Its spark lets you assign an AI manager to an active goal and have it prepare the work, with proposals, decisions, access requests, and blockers all routed back to a human before anything commits. Around it came an AI spreadsheet importer, a wider AI Mode context, and a Skills Library for Claude and ChatGPT — the tool holding the structured record while the reasoning happens elsewhere.

NocoBase turned its plugin system into the skill supply for in-app AI employees: skills are now assigned per employee from the settings page and built from plugins, and conversations became portal-scoped with unread counts. That makes an AI employee an addressable actor inside a portal rather than a chat widget, and it makes NocoBase's existing extension ecosystem the registry of what its agents can do.

OpenProject was the week's standout non-AI move, a useful counterweight to the agent story. Version 17.7 introduced a Resource management module and the organizational data it needs — hierarchical departments with optional LDAP sync, job-title and skills attributes, and per-user work schedules with availability factors — then built a Resource planner on top for allocation and utilization. It is structure the product never modeled before, extending its recent annexation habit from documentation into staffing.

Asana kept two tracks running. The visible one is editor work — this week it shipped rich text in custom fields and threaded comments across tasks, goals, and messages. The structurally significant one is its relaunch of Notes as Pages, a collaborative document surface with co-editing, version history, and task creation, and AI Teammates that can now audit and author a project's automation rules behind a review gate. Asana is trying to keep both the planning document and the automation layer inside its own product.

Wildcards

RentRedi is a property-management tool that lands in this sector, and its first AI feature is off-pattern in a useful way: an AI maintenance helper, in beta, that works both ends of a request. Tenants get one clarifying question and a suggested category, priority, and cleaned-up summary; landlords get the request pre-triaged with a likely cause and a draft reply. Nothing sends automatically — every output is a proposal a human approves. It picks messy human intake, not the back office, as the beachhead.

Tracecat comes at agents from the security-automation side. Its latest release candidate gives agents workflow execution tools — the ability to run the platform's own automations — alongside an AI security architecture, deferred tool loading in the Claude runtime, and isolation work in the same candidate. It is the release where the agent stops advising on the SOAR platform and starts operating it, with the guardrails shipped in lockstep.

Themes that compounded

• Agent-as-tenant: the platform hosts and records an external or in-app agent's state rather than being the agent itself — most explicit at Atlassian, echoed by NocoBase and Notion.
• Human-in-the-loop as a shipped feature: Tability, RentRedi, and Asana all gate agent output behind an explicit review step.
• MCP as the connective tissue: Jira's expanded MCP surface at Atlassian and Tability's Skills Library at Tability both route capability through the same protocol.
• Reach paired with a constraint in the same release, clearest at Tracecat, where execution tools ship alongside isolation and audit work.
• Non-AI capability still shipping: OpenProject's resource module and incremental field work from SmartSuite and Hive show the core surfaces are not standing still.

Watch this week

The near-term signals are concrete. Notion moves Workers onto paid credits on August 11, so expect its next cluster to stay on usage visibility and cost controls. Atlassian has established a repeatable Jira-as-system-of-record pattern with one orchestrator live, which makes a second integration or Teamwork Graph context exposed directly through MCP the obvious follow-on. And watch whether the human-in-the-loop products — Tability and RentRedi especially — start moving their agents from preparing work to posting it on a schedule, which is the step their current review-gated flows are built to enable.