Atlassian demo puts Cursor, Codex and Claude Code agent sessions onto the Jira board

Coding agents land on the Jira board

At the Team '26 Europe founder keynote on 7 October, Atlassian put a Jira board on the main screen with an unusual extra column: seven agent sessions from Cursor, Codex and Claude Code, each marked with a hexagonal avatar. Dragging a session onto the board prompts Jira to write the work item itself, drawing on the session's context. According to an attendee account published on dev.to, that drag-to-create moment was the standout of a keynote otherwise heavy on Rovo, and it frames agent sessions as units of work that belong in the same planning view as human tasks.

What the demo actually showed

The column was labelled "Unlinked agent sessions". Five of the seven rows named their tool — Codex twice, Claude Code twice and Cursor once — while two showed only a pull request number, with a hover card identifying one of those as Cursor. Alongside sat the familiar workflow columns (To do, In progress, In review, Done), a toolbar button for "Needs input", and card footers such as "Working", "Finished" and "Jira Coding Agent with Liam", listing the agent first and the human who assigned it second.

Atlassian's own post on AI in software delivery, cited in the dev.to write-up, describes the mechanic: when an agent starts work before any ticket exists, the developer drags the session onto the board and Jira creates the work item from its context, with filters for work needing input, ready for review, or done. Notably, a person still performs the drag — the tooling automates the paperwork, not the decision.

What ships now and what waits

The board integration is in closed EAP, Atlassian's invite-only early access, and sessions originating from local IDEs and terminals are listed only as "coming soon"; the dev.to author found no sign-up page or support documentation yet. Other pieces are further along:

• "My agent sessions", a view under For you in Jira, is generally available on Standard, Premium and Enterprise plans. It requires Rovo and consumes Rovo credits.
• Jira Coding Agent is built into every paid Jira plan, based on statements Atlassian made in July.
• Claude Agent for Jira is available as a beta Marketplace app dating from June.
• End-User Agents in Jira Workflows has a public sign-up for an EAP starting in early November for roughly 10 to 15 customers, letting teams attach preferred agents — including third-party ones — to workflow statuses.
• Rovo Code Search was demoed with a hybrid search mode but has no stated status or date, while Code context, which searches Bitbucket Cloud and GitHub repositories, is in open beta for paid customers.

For developers building on Forge, Atlassian's agents dashboard documentation says sessions from Forge remote A2A coding agents and Marketplace Rovo agents already link to work items; local coding agents require the Teamwork Graph CLI.

AMP and the rise of agent identity

The other structural announcement was AMP, which Atlassian describes as a collection of human-centric experiences, technologies and patterns for humans and agents working together. Its rollout began on keynote morning, alongside a founder post titled "The End of Single-Player AI". Under AMP, agents get their own identity, context from Atlassian's Teamwork Graph, and access governed by admin controls, Atlassian Guard and permissions. The hexagonal avatar is part of the design language: a shape reserved exclusively for agents. diginomica quotes co-founder Mike Cannon-Brookes describing AMP as closer to a diplomatic protocol than a technical one, building on A2A and MCP rather than replacing them. As of 8 October, the dev.to author had found design guidance but no specification or SDK, so AMP reads as direction rather than an implementable standard.

Rovo, meanwhile, has shifted from a single product to a naming layer, appearing in written posts as Rovo Code Search, Rovo Work, Rovo Insights and Rovo Chat.

A keynote cut short

The event itself ended in disorder. Computer Weekly reported that the keynote stopped abruptly around the 90-minute mark because of a power outage, and The Jira Guy, watching the stream, saw the feed cut mid-sentence. Per the dev.to account, no presentations ran for about an hour and a half before diginomica reported that proceedings had resumed. Atlassian has offered no explanation, and the on-demand recordings open on 12 October.

Why it matters

Cursor, Codex and Claude Code are already how many developers write code day to day. Pulling their sessions into Jira's board makes the planning tool, not the IDE, the coordination layer for mixed human-agent teams — and moves agent-assisted development from a private workflow into visible, accountable process. The auto-generated ticket matters too: the unit of work stops being something a human types and becomes something the system infers from what an agent is already doing. Identity and permissions, via AMP and Guard, become the governance story for that shift. It is early — closed EAPs, a missing SDK, no dates for Rovo Code Search — but the direction is unambiguous: Atlassian is building for teams where agents are colleagues on the board.