Atlassian announces AMP for shared human-agent work

Atlassian introduced AMP, the Agentic Multiplayer Protocol, in a post dated October 6 from Team ’26 Europe in Amsterdam. The company described it as a foundation for agents to work alongside people across Atlassian and other tools, and said its rollout was beginning that day.

Access controls are a central part of the design. Atlassian contrasts an HR agent that inherits the access of the person prompting it with a helpdesk agent operating through a dedicated service account. Agents would draw context from the company’s Teamwork Graph, which connects information across software tools. Atlassian also describes activity audits recording who triggered an agent and what data it touched, with human checkpoints built in.

The interactions are meant to happen where teams already work: briefing an agent through a Loom video, mentioning it in a Confluence document or discussing an approach in Jira comments. Atlassian says agents can also handle triage and routing in Jira workflows. Another described interaction turns a person’s voice, cursor movements and selections into a structured brief with acceptance criteria; the agent then reports back for review.

To make those contributions visible, Atlassian says each agent has an owner, a profile and real-time attribution. Its examples include an agent’s cursor appearing beside human collaborators in a document or whiteboard, plus a record of agent-made changes that teams can review.

The rollout announcement does not mean every described capability was available at once. The post says Jira’s Agent Sessions capability automatically connects local and cloud sessions to work items, but later describes bringing sessions from IDEs and terminals into Jira as coming soon. It gives no date for that capability, leaving the boundary between the announced design and initial availability unclear.