The ultimate TEAM '26 Rovo announcement overview (and more)
You didn’t have a chance to attend TEAM ‘26 and do not want to scour each session from the On Demand Library? I did, so you don’t have to!
I went through each session and tried to find the feature level announcements that you can’t find in any of the major announcement blog posts. I am focusing on Rovo. I know, virtually every announcement had something to with Rovo. I will not go into each Collection’s details but focus on Rovo as a Platform. The heart of all collections.
While I was at it, I’ve also added a few recent announcements that are technically not part of TEAM announcements. Hopefully that makes this list a more or less complete overview of all recent feature announcements and features that are already rolling out.
Rovo
A summary of all updates regarding Rovo itself.
Rovo makes AI-native teamwork real for the enterprise - Inside Atlassian
Rovo Desktop - Open Beta
In case you need Rovo to access your local files - now you can use Rovo Desktop. Rovo gets to work in the background: Scanning desktop files, pulling in company knowledge from the Teamwork Graph, connecting the dots. And, Rovo works not just in Atlassian, it also shows up in other AI assistants like Gemini or Copilot. No matter where the work happens — you have the same context, the same capabilities, and the same outcomes.
That’s the positive side of things anyway. Do we want Rovo to access ALL data?…
https://community.atlassian.com/forums/Rovo-articles/What-is-Rovo-Desktop-Open-Beta/ba-p/3232121
https://support.atlassian.com/rovo/docs/get-started-with-rovo-desktop/
New Rovo Studio & Rovo-coding Forge Apps - GA
This is not just a UI change and a rebranding from “Scenarios” to “Subagents”. This new Studio finally got the ability to Rovo-code Forge Apps. Yes. That has been announced last year already, now it’s rolled out. Build your own Confluence Macros or exhance your Jira Boards. You can also manage your Company Hub (Confluence Premium only) and Service Agents here. The Automations are a little funny: You can’t actually see existing Confluence/Jira rules. Sorry, flows. there. They are distinct rules that require an “App connection” to get started. A little odd if you ask me.
Note: With the Rollout every user has gotten the Studio User role automatically. Depending on your Studio settings, everyone can build Agents, Automations and Apps. Make sure to update access settings in the Org and in Studio.
Studio | Rovo | Atlassian Support
Build Atlassian Rovo Agents Faster with the New Studio Experience
The new, unified AI building experience for Rovo S... - Atlassian Community
Rovo implicit and explicit memory - Open Beta (apparently)
Shown and announced in the keynote, but there aren’t really resources available yet. Rovo currently uses some context from the active Chat, but doesn’t “remember” information for other Chat sessions. It knows who you are, based on live information from the Teamwork Graph and your profile - not, because you already explained it 10 times. This part is now called “implicit memory” and updated weekly based on your activity. The explicit memory uses data from your Rovo interactions. Each memory can be deleted - in case you want to re-invent yourself at work.
Max Mode in Chat - Waitlist/EAP
Max Mode is not just a new Reasoning Mode. It allows Rovo to break down your instructions into multi-step plans. Rovo will execute the plan without you having to go back and forth with multiple prompts. Sounds like Max Mode will be able to do some really cool stuff, but also take foreeeever. Still, very exciting.
Join the Waitlist for Max Mode in Rovo | Atlassian
Is your instance ready for Rovo Max Mode? Our Team... - Atlassian Community
Compare Rovo Chat reasoning modes | Rovo | Atlassian Support
Code Intelligence - EAP
In the keynote, Sherif found Mike’s open To-Dos in a Code Base in Jira Data Center from over 15 years back. This was done through one simple prompt that queried Atlassian’s connected code. Code Intelligence allows engineers and agents to ask intent‑level questions across large, multi‑repository codebases, combining the source graph with context from Jira, Confluence, and other tools to answer questions like “which services still use an outdated UI pattern and who owns the migration plan?” in one place, rather than going through each App’s code manually.
Code Intelligence shown in Keynote
Custom Skills for Rovo - Coming Soon
Create your own customized Rovo skill with the “Create a Skill” skill in Rovo Chat. Rovo will ask a few questions - the created skill will be available to all in Chat, Agents and Automations. This seems to be a new no-code interface for what is already available in Forge: https://developer.atlassian.com/platform/forge/manifest-reference/modules/rovo-action/#customer-created-agents It looks like skills are limited to creator but can be shared with others. In the presentation, they show the “Skill menu” where you can see your own skills and shared skills. This is an extension of what is available in Agent building already.
My question(s): Why is this a skill in Rovo Chat and not something available in Studio? Will be able to restrict who can use that skill and hence create new skills?
Other than the On-Demand Stream of the session (starting at 11:30 mins) there is no info available. This session is not available on Youtube.. https://events.atlassian.com/team-digital/v/s-4059841?i=bkoeN1wpyGW6lnxpzGftDx_jYglYL3OE
Anyone else got enough of the word skill now?
Data Insight & Dashboard Skill - Announcement
Rovo Chat can already create some pie and bar charts, but they are only available within Chat and cannot be used elsewhere (unless screenshot). The new skill creates a html page that includes multiple charts, can have custom colors etc. They unfortunately have not shown how/if it integrates with Jira Dashboards or how you can access it from outside of Chat but it looks promising.
https://youtu.be/5enK2N38rSM?si=DJKeNs6gKfrveRJX&t=2093
Audio Briefing Skill - Announcement
You already like Confluence Audio Briefings? Rovo Chat can now create an Audio briefing based on all context available. Unlike in Confluence, you can’t adjust length, tempo or voice but still quite cool.
https://youtu.be/5enK2N38rSM?si=2h3hE7v5ib9De9aW&t=2325
File Output
Looking at the two other skill announcements it looks like Rovo will finally be able to produce files that are downloadable for the user!!! Rovo already thinks it can do that, but produced links lead you to some AWS storage that you don’t have access to.
Not officially announced anywhere though.
Rovo Daily Briefings - EAP
Rovo Daily Brief is your new smart digest, surfacing important updates and suggested actions for each of your workstreams, right when you need them. Instead of digging through notifications or toggling between tabs, Daily Brief brings together your key updates, tasks, and insights in one place, so you can spend less time searching, and more time focusing on the work at hand.
EAP sign up here
🗞️ Want a smarter start to your day? Join the Rov... - Atlassian Community
Rovo CLI - Coming Soon
You may ask, why there are two CLI announcements. What is the difference between Rovo CLI and Teamwork Graph CLI? Honestly: i am at a bit of a loss here as well. My best explanation: Rovo CLI is directed at human users, TWG CLI is optimized for Agent use.
Similar to Rovo Dev CLI anyone can now run complex tasks—analysis, reporting, automation—using powerful skills, custom tools, and the Teamwork Graph, all from the command line. No setup or integrations needed, just download and go. Brings the same AI capabilities as Rovo Dev to the command line for any role — analysis, reporting, automation — powered by skills, custom tools, and the Teamwork Graph. With support for powerful skills and custom tools, teams can tailor the CLI to their specific needs — from generating reports to automating repetitive tasks — all grounded in their organisation's real data.
Not sure where this was announced - I got that information from the CSM and there was no link for further information.
Rovo Agents
Autonomous Agents in Automations - EAP
Rovo Agents currently do not perform their skills/actions when invoked from Automations - they only return text. With this feature, they will be able to use their skills and act autonomously. This announcement makes only sense if you think about how Agents can run directly from Jira now anyway. So: Rather than using the {{agentResponse}} smart value in follow-up actions, the “Use Rovo Agent” will be packed with actions itself. You can select which of the available skills can be executed autonomously in that specific Automation. We will get even more control with Agent Accounts. Rather than the Agent acting with the Automation flow Owner’s permission (or whoever connected the Agent), the Agent will act as itself, with its own set of permissions. No more unwanted data leaks. See the next announcement for details.
Sign up for the EAP go.atlassian.com/agents-eap
https://youtu.be/5enK2N38rSM?si=pXhLEoQe8Z_0cb3y&t=1761
Related Feature Request: https://jira.atlassian.com/browse/ROVO-261
Rovo Agent Accounts - EAP
With Agents becoming more autonomous in various settings, you may want more granular control. You will be able to decide for each Agent, whether they should run with the invokins user’s permissions or with their own Agent Account. Rovo Agent Accounts will actually look and act more like regular User Accounts. They will use the same Permission logic. Agents will need App and Space level permissions to access specific content. That way, actions performed by the Agent will be logged with the Agent Account as well.
This is going to be an interesting concept. What happens, when a Space admin removes the Agent from their space, not knowing that it will crash someone else’s workflow?..
Sign up for the EAP go.atlassian.com/agents-eap
https://youtu.be/5enK2N38rSM?si=2QPo6JfFhDJ17mfC&t=1835
Agent Versioning - EAP/Rolling Out
Tired of having to save the old instructions in a text file just so you don’t loose it if you work on the Agent? Say no more and patiently wait for one of the next Rovo releases. The team is actively working on Versioning for Agents. Paired with the Evaluations feature you should be able to compare different versions of prompts as well, but there are no details on the exact capabilites yet.
and/or sign up for the EAP go.atlassian.com/agents-eap
Rovo Skills for Rovo Agents - EAP
It doesn’t seem to make a lot of sense if you read it without context. Rovo skills are the fairly new / commands that you can use in Rovo Chat. /update-work-items or /manage-knowledge-base are just two examples. Those skills are coming to Agents, hopefully assimilating Chat and Agents capabilites. Cause frankly, it’s confusing as hell at the current stage.
Rovo Skills are generally available to unlock encoded best-practice guidance
sign up for the EAP go.atlassian.com/agents-eap
Select a LLM for your Agent - EAP
There isn’t much info apart from the sign up link. Pretty confident it’s the implementation of this feature: https://jira.atlassian.com/browse/ROVO-275 I feel like the original pain point of ever changing models was addressed by fixing agents to only ever using one ( see https://community.atlassian.com/forums/Atlassian-AI-Rovo-articles/Important-Update-Rovo-Agents-are-getting-a-new-backend-LLM-model/ba-p/3207356). But I am not mad about being able to choose between models for different jobs.
Sign up for the EAP go.atlassian.com/agents-eap
Import/Export Agent configuration - EAP
Again: not much apart from the sign up. I guess it relates to this feature: https://jira.atlassian.com/browse/ROVO-179
Essentially, you will be able to export/import Agents and reuse them between different sites. This will make a lot of sense for Orgs where Agents need to be deployed and tested on Sandbox first. So, yay!
sign up for the EAP go.atlassian.com/agents-eap
Adjust response behaviour of Subagents - GA
Currently, the Agent has the final say over the response, regardless if a Subagent was triggered. You can now adjust that behaviour so the Subagent response is directed to the user straight away.
Configure subagent responses in Rovo Agents
Rovo Governance
Not a lot of announcements (very disappointing to be frank), but at least some.
Group-based Access - Rolling out - Enterprise Only
Enterprise customers can not only block/allow Rovo access per App, but also allow specific groups to access Rovo per App. I can already feel the disappointment from Standard/Premium users…
Manage Rovo access for Enterprise | Atlassian Support
Org-wide Agent inventory and insights - Announcement
New org‑wide agent lists and insights give admins a live inventory of who built what, where it’s running, and how often it’s being used.
I very much hope that this is rolling out very soon! Vote for these request to maybe accelerate delivery? [ROVO-516] Public APIs for Rovo Agent Management - Create and track feature requests for Atlassian products. / [ROVO-146] Agent Management tools for Org/Studio Admins - Create and track feature requests for Atlassian products.
https://www.atlassian.com/blog/company-news/rovo-team-26
Possibly related feature request that is in progress: https://jira.atlassian.com/browse/ROVO-146
Atlassian Rovo MCP Governance controls - GA
Although technically not part of announcements, these features were released around team so I am mentioning them as well:
-
Control each tool (Read, Write, Delete)
-
Control API token access
-
IP/3rd party Allowlists
Atlassian-hosted Models only - GA - Enterprise only
Old but gold: Now available to all Enterprise customers on request. Choose to only use Atlassian-hosted LLMs and stop data being sent to 3rd party LLMs. Why in theory then? Atlassian hosts their LLMs in US Data centers so not really helpful for regulated customers from other countries.
Atlassian-hosted LLMs | Atlassian Support
Customer Managed Key now include Rovo - EAP - Enterprise only
Customer-managed keys (CMK) are extended to Rovo (Search, Chat, and Agents only), allowing customers to isolate that data.
https://www.atlassian.com/platform/infrastructure/cmk
HIPAA Compliance - Announcement
The Rovo Team is actively working on HIPAA Compliance according to the newest update in https://jira.atlassian.com/browse/ROVO-124
Target date is Q3 2026
Teamwork Graph
You can’t really miss this one, even if you’ve not attended and not read a single blog post on purpose. The Teamwork Graph is the “AI context fabric” and a requirement for true AI Adoption and value.
Atlassian Teamwork Graph: The context engine behind your AI—everywhere - Inside Atlassian
Browse your Teamwork Graph - GA
Go onto https://teamworkgraph.com/ and check out your company’s actual graph. The website also offers entry points to all the things you can do with the graph.
Atlassian Rovo MCP now includes Teamwork Graph - Open Beta
Two new tools “getTeamworkGraphcontext” and “getTeamworkGraphObject” brings the context into AI Agents. This explains better, why the Atlassian MCP Server is mostly refered to as “Rovo MCP Server”. It’s the same thing, in case you were wondering.
Use Teamwork Graph in Rovo MCP Server (Open Beta)
Teamwork Graph CLI - Open Beta
According to my AI expert colleagues, we’re sort of over MCP already. With the “Agent first” Teamwork Graph CLI, 3rd party Agents can browse the Teamwork Graph and integrate the data directly into their workflows.
Build your own Teamwork Graph Connector with Forge - GA
The ability to connect your custom data into the Teamwork Graph has been moved to GA. To be honest: I’ve not heard much about success from the Beta but hoping that will change now. The list of available Connectors has not really been extended as much as I expected so building your own will massively help implementing Rovo as the central company search.
https://developer.atlassian.com/platform/teamwork-graph/build-a-teamwork-graph-connector/
Honorable mentions
Okay. I will share some App Collection focused announcements with you.
Create with Rovo in Jira - Coming Soon
After having decent success with the feature within Confluence, “Create with Rovo” now moves into Jira as well.
No resources available yet.
Agents in Jira - GA
Agents in Jira let teams assign work items directly to Rovo or third‑party agents, mention agents in comments, and embed them into workflows and automations. Every agent action logs against the work item, making AI work auditable, traceable, and visible to the whole team rather than hidden in ad‑hoc prompts. This feature has moved from Beta to GA.
https://www.youtube.com/watch?v=uXL7zzulJiE
https://community.atlassian.com/forums/Jira-articles/Introducing-Agents-in-Jira/ba-p/3194583
https://www.atlassian.com/blog/rovo/ai-agents-in-jira
Rovo Remix in Confluence - Open Beta
Remix with Rovo allows users to select any text, table, or section on a Confluence page and instantly transform it into visual formats such as charts, infographics, diagrams, and other data visualizations, with Rovo recommending formats based on the content; it runs entirely inside the Confluence editor, keeping context and permissions intact
https://support.atlassian.com/confluence-cloud/docs/transform-content-with-remix/
https://www.atlassian.com/blog/confluence/rovo-remix-3p-agents-confluence
https://www.youtube.com/watch?v=c65xu8HiE6c
Rovo powered Incident Command & Prevention Center in Service Collection - Coming Soon
The Incident Command Center is an AI‑native response hub in Jira Service Management that consolidates alerting, investigation, and communication into a single journey, pulling signals from observability tools (such as New Relic and Dynatrace), service maps from Assets, deployments from Bitbucket/GitHub/GitLab, and feature flags to visualize the service graph and pinpoint root cause and blast radius quickly. Complementing the command center, the Incident Prevention Center analyzes upcoming changes (code deployments, configuration updates, etc.), compares them with historical incidents and change outcomes, and warns teams about risk hotspots, suggesting mitigations before issues occur, effectively shifting from reactive incident management to proactive risk control.
Rovo Ops is the AI assistant powering much of the incident and operations story: it helps teams understand what happened during an incident by correlating signals across the Teamwork Graph, identifies likely root causes and impact, assists with remediation steps, and feeds learnings into post‑incident reviews
No links for the Centers yet..
Using the Rovo Ops agent | Rovo | Atlassian Support
Assets in Rovo - GA
Rovo now has access to Assets data and an EAP for actions within Assets is ready for sign-ups.
📣 Your Assets data at your fingertips with Rovo - Atlassian Community
What have I missed?
That's a lot! Thanks to all the Rovo Team at Atlassian not just for all those features but also for keeping JAC tidy ;) that was helpful.
Any additions @Jensen Fleming @Sherif Mansour @Kalvin Xu @Ashish Sharma @Jacqueline Bietz @Janessa Drainville and others?
Did you catch another announcement that I have missed?
Let me know in the comments and I'll add it on the list. If I feel super motivated, I might even mark those that have shipped.
Was this helpful?
Thanks!
Rebekka Heilmann _viadee_
2 comments