Atlassian describes AMP as interface patterns for making human-agent work more visible and attributable across pages, tickets, chats and code. The guidance focuses on showing which agent acted, which person initiated the work and—where relevant—which connection method it used. Atlassian’s public design page does not establish AMP as a separately sold product or specify a launch date, price or availability terms.
What Atlassian means by AMP
Atlassian Design presents AMP as UI patterns for collaboration between people and AI agents across existing work surfaces. The documented patterns cover real-time and asynchronous collaboration, agent mentions and comments, chat and multimodal input, agent workflows, and contextual governance. Code is one of the surfaces, alongside pages, tickets and chats. Atlassian Design’s AMP overview describes the approach.
As an Amazon Associate I earn from qualifying purchases.
The practical goal is to make agent activity legible as work happens, rather than leaving teammates to infer later how a change appeared. This is design guidance, not evidence of a distinct AMP product launch: the cited page does not give a launch date, standalone product offer, pricing or availability terms.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What useful AI-code attribution should show
Atlassian’s example separates the agent from the person who invoked it, while putting technical connection details in supporting attribution information. In the example, a hover card identifies Anthropic, the associated person and Atlassian MCP as the connection method. That illustrates three questions a code reviewer or teammate may need answered:
#1 Best Overall
- Which agent acted? Identify the agent responsible for the action.
- Who initiated it? Show the person on whose behalf the agent worked.
- How did it connect? Expose the route, such as MCP, in the supporting details when relevant.
This distinction matters: naming only a tool may not tell a team who authorized an action, while naming only a person can obscure that an agent performed the work. Atlassian’s guidance calls for agent activity to remain visible and attributable, including actions carried out through MCP and CLI connections. Atlassian Design’s AMP overview
How the patterns span teamwork surfaces
AMP is not limited to code review. Its documented scope includes pages, tickets, chats and code, with interactions that can be real-time or asynchronous. The page names concepts including real-time editing, mentions, comments, chat and multimodal input, alongside agent workflows and context and governance. The point is to make agent participation understandable in the context where the work is happening, rather than treating it as an isolated coding-tool event.
When evaluating an implementation against this guidance, useful questions include whether attribution is complete, whether activity is visible on each relevant surface, whether updates work both live and asynchronously, and whether people can interact through the modes their workflow requires.
Governance is part of visibility
Attribution explains an action; governance defines what an agent can access and which controls apply. Atlassian says agents access the Teamwork Graph through permissioned access governed by administrator controls, Atlassian Guard and enterprise data policies. The AMP page also references integrations across tools such as Figma, GitHub and Claude. These are described as part of the design context, not as a list of products bundled with AMP. Atlassian Design’s AMP overview
For teams, the design implication is to consider permissions and oversight alongside interface details: an activity trail is more useful when it can be understood within the access rules and policies that governed the agent’s work.
AMP is distinct from Atlassian’s AI measurement announcements
Atlassian has separately described tools and measurements related to AI development. Those announcements provide context for the visibility problem, but they should not be mistaken for AMP features or proof that AMP is an analytics product.
Rank #4
- In its October 6, 2026 announcement, Atlassian said more than 3,000 of its developers use Codex through ChatGPT Enterprise across terminals, IDEs and code-review workflows. That is Atlassian’s own report of internal usage, not an independent survey. The announcement also says DX provides visibility into developer impact. Atlassian’s OpenAI partnership announcement
- Atlassian’s September 10, 2026 article describes DX for Agentic Development as measuring AI impact across throughput, quality, adoption and cost, and discusses a Jira Agent Usage Dashboard for seeing which agents teams use. These are separate measurement and Jira capabilities, not evidence that AMP itself is a standalone analytics product. Atlassian’s DX for Agentic Development article
- In the same DX discussion, Atlassian reports an analysis in which teams whose AI tools used the most Teamwork Graph context shipped roughly 64% more per developer. This is an association reported by DX and Atlassian; it does not establish that context alone caused the difference. Atlassian’s DX for Agentic Development article
- Atlassian’s 2026 AI SDLC study, described as including more than 1,100 engineers and engineering leaders, found that 94% of engineering leaders said their organizations use AI in some capacity. This is the study’s reported figure, not a measure of AMP adoption. Atlassian’s 2026 AI SDLC study article
Together, these figures explain why teams may care about understanding agent activity and impact. They do not demonstrate AMP’s adoption, effectiveness or commercial status.
What teams can assess in an implementation
Atlassian’s material is best read as a set of design concerns rather than a product comparison. Teams applying the guidance can assess whether their interfaces provide:
Best Value
- Attribution that identifies the agent, the invoking person and, where appropriate, the connection method.
- Visibility on the work surfaces where actions occur, including code as well as tickets, pages and chats.
- Useful updates for both real-time and asynchronous collaboration.
- Permissioning and oversight consistent with administrator controls and enterprise data policies.
- Interaction through relevant mechanisms such as mentions, comments, chat and multimodal input.
The sources support these as evaluation dimensions, but do not establish a scorecard, certification or purchasable set of AMP tiers.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
