AMP & Agent Sessions: how to enable, setup, timeline?

Question

Hi everyone,

Since Team '26 Europe our clients have been asking about AMP. I'm looking for the practical details that the keynote and blog posts didn't cover.

Here's what I have so far. According to the AI SDLC post, Agent Sessions is in closed EAP and local session tracking is "coming soon". Today, Claude or Cursor can update Jira through the Atlassian MCP server, but that is recorded as the user, not as an agent session.

* Enablement: Does AMP have an admin switch anywhere, or does it simply appear as each feature rolls out?
* EAP access: How can someone join the Agent Sessions EAP?
* Timeline: Is there a target quarter for beta or GA of local session tracking and agent accounts?
* Setup for local agents: How will a Claude Code, Claude Desktop or Cursor session be linked to a work item? Through MCP, a separate plugin or CLI, or by starting from the issue key?
* Live updates: Will the agent stream progress to the work item and post a result or transition when it finishes? Or does it still have to do that itself with MCP calls?
* Scope beyond SDLC: Is this limited to coding agents? Could "normal" work, such as drafting a Confluence page or a JSM response, be handed to a third-party agent and tracked the same way?

Any pointers to docs, a roadmap item or an EAP contact would be appreciated.

Thanks!

József

Rebekka Heilmann (viadee) · Answer

To see Agent MCP sessions in your Jira (or Atlassian in general), the specific Apps need to be installed. For Claude it is the "Claude Agent for Jira" App. See Set up Claude Agent for Jira | Jira Cloud | Atlassian Support

This is the requirement for all things AMP to work, but parts of what was showcased are not fully rolled out yet.

Trevan Householder_Isos-Tech-Consulting_ · Answer

@József Porohnavec, there's no AMP admin switch. Atlassian's AMP page (

https://www.atlassian.com/platform/agentic-multiplayer-protocol

) describes it as an umbrella of patterns (agent identity, local sessions, MCP, governance), and each piece ships separately with its own controls. The cloud-side "My agent sessions" view is already GA once Rovo is active (docs:

https://support.atlassian.com/jira-software-cloud/docs/view-and-manage-agent-sessions-in-jira/

).

For local session tracking, the EAP route is the Jira AI-native dev waitlist (

https://www.atlassian.com/software/jira/dev/waitlist

), which lists "Connect local agent sessions to Jira." I haven't seen a public beta or GA quarter, or the exact linking mechanism, so I wouldn't promise clients dates yet. Until then, MCP or the Teamwork Graph CLI writes back as the user, like you said.

On scope, AMP's examples include Confluence pages and IT triage workflows, so it's not coding-only.