Atlassian Team '26 Europe Founder Keynote: agents on the Jira board, then a power cut
Mihai Perdum
Author
8 min readOctober 9, 2026
Key takeaways
At 10:20 CEST the keynote showed a Jira board with a column of 7 unlinked agent sessions from Cursor, Codex and Claude Code. Atlassian calls it Agent Sessions: drag a session onto the board and Jira creates the work item. It's in closed EAP, Atlassian's invite-only early access, and the local IDE and terminal part is coming soon.
Part of that board you can use today. Jira's My agent sessions list, under For you, has been generally available since 8 July 2026 on Standard, Premium and Enterprise, and needs Rovo. Atlassian said in July that Jira Coding Agent is built into every paid Jira plan. The unlinked column and drag-to-create are the new part.
AMP, the Agentic Multiplayer Protocol, is Atlassian's collection of experiences, technologies and design patterns for agents working next to people. On stage at 09:10 it had three layers: real-time and async collaboration, identity and shared presence, context and governance. Atlassian said on 7 October it 'begins rollout today'. By 8 October we'd found design guidance, like the hexagon avatar reserved for agents, and no spec or SDK.
The power went out around the 90-minute mark, mid-sentence. A post from the venue at 11:45 CEST said the electricity was still out, and a diginomica report first published at 12:48 says proceedings resumed. From where I was, no presentation ran for about 1.5 hours.
If you run CogniRunner, Sentinel Vault or LeanZero Management, Monday's majors (7.0.0, 7.0.0 and 6.0.0 in Manage apps) need a site admin's approval, and this week's fixes only arrive after it. From Monday 5 to Thursday 8 October we made 10 production releases and 544 commits across the three.
At 10:20 on Wednesday 7 October, the Team '26 Europe Founder Keynote put a Jira board on the main screen. Seven agent sessions from Cursor, Codex and Claude Code sat in a column of their own. Drag one onto the board and Jira writes the work item for you. That was the part I liked most. A few minutes later the power went out mid-sentence. No presentation ran for about an hour and a half.
The board feature is in closed EAP, Atlassian's invite-only early access, so you can't switch it on yet. The rest didn't wow me much, but it was progress. Lots of Rovo on stage. AMP, Atlassian's new ground rules for agents and people working together, was quite cool too.
Below: the keynote from my seat in the hall, what's old and new on that board, and the power cut. Then the rest of our Wednesday, day 2 of Team '26 Europe: showing our three Forge apps to Atlassian's people, braindates, and what we shipped since. Part 1 is the hub with dates and times. Part 4 lists every Team '26 Europe announcement with its status, so I don't repeat those here.
Want to watch it? Atlassian's on-demand library opens on 12 October. I don't know yet if the recording has the last minutes.
The keynote in four frames. The first three times are from my phone, in CEST. The last panel is black on purpose: I have no photo of the cut, and Computer Weekly puts it around the 90-minute mark.
Six things from keynote day, and which ones you can use
Agent Sessions, the unlinked column with drag-to-create: closed EAP. Sessions from local IDEs and terminals: coming soon.
My agent sessions, under For you: generally available on Standard, Premium and Enterprise. Needs Rovo.
Jira Coding Agent: built into every paid Jira plan, Atlassian says. Claude Agent for Jira: beta Marketplace app.
End-User Agents in Jira Workflows: EAP with a public sign-up, from early November.
Rovo Code Search: shown on stage, no status, no date. Code context, the related Rovo feature: open beta.
AMP: on 7 October Atlassian said it 'begins rollout today'. By 8 October we'd found design guidance and no spec or SDK.
What the Founder Keynote showed: a lot of Rovo, and AMP
At 09:10 the AMP slide went up. Atlassian's AMP page calls it "the collection of human-centric experiences, technologies, and patterns" for how humans and agents work together. The founder update posted on keynote morning, The End of Single-Player AI, says "AMP begins rollout today."
The AMP slide at 09:10, cropped to the slide. The three labels match Atlassian's AMP page almost word for word. The founder update names the first layer In-the-Flow Collaboration.
In plain words, agents get their own identity. They show up next to people, wherever the work is. The Teamwork Graph, Atlassian's map of your work data, gives them context. Admin controls, Atlassian Guard and permissions decide what they reach. And the hexagon matters. Atlassian's AMP design patterns want every agent shown with "a hexagonal avatar, a shape reserved only for agents."
It's not a protocol you implement like MCP. Mike Cannon-Brookes is quoted by diginomica saying to think of it "more as a diplomatic protocol than a technical protocol", and that "it builds on A2A and MCP and other things." Developers: read the design patterns.
Rovo was everywhere on stage. In the written posts it moved into product names: Rovo Code Search, Rovo Work, Rovo Insights, Rovo Chat.
Rovo Code Search, shown on stage with no status yet
At 09:29 the screen showed code-search-portal.atlassian.com, searching "dark mode theme" with a filter labelled Search Mode: HYBRID. Atlassian's platform post calls it the new Rovo Code Search app. It has no status and no date. Code context, the Rovo feature that searches code in your Bitbucket Cloud and GitHub repos, is rolling out gradually to paid customers in open beta. My reading of HYBRID is lexical plus semantic search, as Atlassian's code context doc describes. The screen didn't say.
Code Search at 09:29. Look at the Search Mode button on the left: HYBRID. The repositories look like Atlassian's own demo set, not a customer's.
Agent sessions on a Jira board: Cursor, Codex and Claude Code
Down the left ran a column titled Unlinked agent sessions 7. It looked like a side bar. It's a board column. Every row had a hexagon avatar. Five named their tool: Codex twice, Claude Code twice, Cursor once. Two showed only a pull request number, and the hover card on one of those says Cursor. Then came To do 5, In progress 3, In review 2 and Done 2. The toolbar had a Needs input button. Card footers read Working, Finished and Jira Coding Agent with Liam. Liam looks like a demo account. Atlassian's pattern is the agent first, then the human who assigned it.
The board at 10:20, from my seat. Notice the hexagons on every session row, and the footers that show which agent is working on which card.
Atlassian's post on AI in software delivery describes exactly this. If an agent starts on something before a ticket exists, "the developer can drag the session onto the board and Jira creates the work item from its context." There's also a view "with filters for work that needs input, work ready for review, and work that's done." So tickets do get created for you. A person still does the drag.
The same post gives the status. "Agent Sessions and Interactive PR Reviews in Loom are in closed EAP." Sessions from IDEs and terminals are marked coming soon. I found no sign-up page and no support doc for the column yet.
What you can use today is the older half. My agent sessions, under For you in Jira, lists sessions as needs input, working or finished. It needs Rovo switched on and a Standard plan or above. Agents in Jira consume Rovo credits. Claude Agent for Jira is a beta Marketplace app from June, and Atlassian said in July that Jira Coding Agent is built into every paid Jira plan.
Illustration, generated locally with FLUX. Drag a session onto the board and Jira writes the ticket. Here the robot does the drag. In Jira a person still does.
I also liked that agents could be linked to other agents' cards. Atlassian's nearest description is in its AMP design patterns: a card can show a session from an agent that isn't its assignee. Separately, Atlassian opened a public sign-up for an EAP for End-User Agents in Jira Workflows. It will let team members attach their preferred agents, from Rovo to third-party ones, to workflow statuses from the board. It kicks off in early November 2026 for 10 to 15 customers.
For Forge builders like us, there's already a route. Sessions from Forge remote A2A coding agents and Forge-based Rovo agents from the Marketplace link to work items, per Atlassian's Agents dashboard doc. The same doc says local coding agents need the Teamwork Graph CLI installed. Does that fill the unlinked column? No Atlassian page says. If you build coding agents on Forge, as we do in CogniRunner, that doc is the one to read.
The power cut: about an hour and a half with no presentations
It was right at the end. The Jira Guy was watching the stream. He wrote that "the venue lost power" and the feed cut out on "a living nervous system that connects your a-". Computer Weekly says the keynote "ended abruptly around the 90-minute mark with a power outage."
After that, no one could present anything. The hour and a half is my figure. At 11:45 a Community Champion posted from the venue that the electricity was out. diginomica's report, first published at 12:48, says "proceedings have resumed." So the window runs from about 10:30 to some time after 11:45. I found no Atlassian statement and no cause.
Illustration, generated locally with FLUX. The keynote stopped mid-sentence. The candles are artistic licence.
Taking our Forge apps to Atlassian's people
Then we went through the gauntlet of Atlassian representatives on site, to talk about Forge, Atlassian's app platform, and to explain our apps. Good reception overall. Towards the end we were met with a fair bit of boredom, so not necessarily the best ending. We vibed with a lot of interesting people, though.
Braindate feedback on CogniRunner, Sentinel Vault and LeanZero Management, and what we shipped
The other thing that came out of the day was feedback from our braindates, the small attendee-run meetups. We got it on all three apps, and we've worked hard to fix what came up. Thanks to everyone who joined and brought ideas. I can't map each fix to one conversation. Some were already in flight. This is what reached production between Wednesday and Thursday evening.
CogniRunner 7.3.0 in Manage apps (our release 1.31.0) let you keep restore points you choose and added a Put back exactly restore. Coder conversations now start private, and the AI agents stay out of projects an organisation admin puts off limits. 7.4.0 (1.31.1) made the admin panel and rule editor fit phones and tablets. 7.5.0 (1.31.2), on Thursday, opens the admin page faster. Sentinel Vault7.1.0 stopped cutting file names short on phones and shows names instead of raw account IDs in API access and the Activity report. LeanZero Management 6.1.0 (our release 4.18.1) stopped the timeline hiding under the plan header on short screens, and put the Save button back on phones.
If you admin one of these, check Manage apps. Monday's majors, CogniRunner 7.0.0, Sentinel Vault 7.0.0 and LeanZero Management 6.0.0, each add one permission, so each one waits for a site admin to approve it. The new permission lets the app report to Atlassian which accounts it holds data for and learn which of them have been closed, so it can erase what it can for those. The majors also drop 6 permissions from CogniRunner and 12 from Sentinel Vault. The fixes above are minor versions on top of them, so your site only gets those once the major is approved.
Counting from Monday, we made 10 production releases and 544 commits across the three apps. New stuff is coming to Sentinel Vault and CogniRunner soon. I'll leave it at that until it ships.
Verdict: not much wow, but progress
The feature I liked most, Agent Sessions, isn't something you can switch on yet. Running coding agents in Jira? Ask your Atlassian contact about the Agent Sessions EAP, and use My agent sessions meanwhile. The End-User Agents EAP has a public sign-up. My colleague Gabriela's recap of the whole week comes in part 6 on Saturday 10 October.
