Rovo Agent Connector

The rovo:agentConnector module allows you to integrate remote AI agents hosted on external infrastructure into Jira. Once a remote agent is registered, users can interact with them in a similar manner to other users and Rovo agents: assigning them work items, @mentioning them in comments, and chatting with them via the Rovo Chat panel.

Use this module to integrate Jira with AI agents residing outside of the Atlassian platform (such as GitHub Copilot, Cursor Background Agents, or Box AI Agents). Integrations must use A2A 1.0. For implementation guidance, see Integrate remote agents with Jira.

Requirement: Agent2Agent protocol server

Remote agents must implement an Agent2Agent (A2A) protocol server to communicate with Jira. The A2A protocol is an open standard that enables AI agents to communicate with each other, regardless of the underlying framework or vendor.

For more information, see Getting Started.

Jira communicates with remote agents via the JSON-RPC 2.0 protocol. Your remote service must expose an endpoint that accepts JSON-RPC requests from Jira and returns responses according to the A2A protocol specification.

Timeouts

Note that in case of timeouts during the streaming requests, Jira will attempt to reconnect automatically to the remote agent.

We also have different timeout behaviours depending on the trigger of the agent interaction:

System User implications

This means that users won't be able to @-mention the app in comments or fields. This change affects all app versions in the current environment.

Instead, the agent connector user is available for @-mention.

The Forge CLI warns about this behavior change at deployment time and asks you to approve before proceeding. This warning feature requires the Forge CLI version 13.3 or higher. For more details about the deployment approval flow, refer to deploy.

Limitations

1
2
I couldn't finish working because of a technical problem on my end. Try again in a few moments.

Manifest structure

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
modules {}
└─ rovo:agentConnector []
   ├─ key (string) [Mandatory]
   ├─ name (string) [Mandatory]
   ├─ description (string) [Optional]
   ├─ icon (string) [Optional]
   ├─ conversationStarters [] [Optional]
   │  └─ conversationStarter (string)
   ├─ productContexts [] [Mandatory]
   │  └─ product (string)
   └─ protocols [] [Mandatory]
      └─ agent2Agent
         ├─ version (string) [Mandatory]
         └─ jsonRpcTransport
            ├─ streaming (boolean)
            └─ endpoint (string) [Mandatory]

remotes []
└─ key (string) [Mandatory]
└─ baseUrl (string) [Mandatory]

resources []
└─ key (string) [Mandatory]
└─ path (string) [Mandatory]

permissions []
└─ scopes []
  └─ scope (string) [Mandatory]

In this structure:

• The rovo:agentConnector module defines a remote agent with metadata and communication protocols.
• The endpoint property references a separately defined endpoint module, which specifies the route Jira uses to communicate with your remote agent via JSON-RPC.
• The remotes configuration identifies the domain of your remote service and enables authentication tokens to be passed to your service.
• The resources module provides static assets like the agent icon.
• The productContexts property specifies which Atlassian products the agent operates in. Only jira is supported.
• The permissions.scopes array declares the OAuth scopes your app requires. The read:jira-work scope is required for the agent to function correctly.

Properties

A2A Protocols

Transport properties

Collapsed sections in A2A streaming responses

In cases where the A2A agent needs to send back a long response, we recommend utilizing a collapsed section to hide verbose details and streamline the content presented to the user.

We support the Github markdown <details> block syntax as in Organizing information with collapsed sections, with the exception that we do not support <details open>.

Example:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
<details>

<summary>A summary that is immediately shown to the user</summary>

Some detailed content that will appear collapsed and can be expanded, such as tool call payloads or agent thinking messages.

You can use other markdown notations here too, such as code block.

    ```json
    {
      "tool_name": "bash",
      "input": "git pull origin main --no-rebase"
    }
    ```

</details>

Demo

An A2A agent streams a response with three collapsed sections (two tool calls and its thinking), followed by a normal answer. Each section expands when the user clicks the chevron.

Related manifest configurations

The rovo:agentConnector module works together with other manifest configurations to enable remote agent integration:

Manifest example

The following example manifest file defines an rovo:agentConnector that connects to your remotely hosted agent:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
modules:
  rovo:agentConnector:
    - key: your-awesome-agent
      name: Your Awesome Agent
      description: An awesome agent that you built
      icon: resource:agent-resources;icons/your-agent.svg
      productContexts:
        - jira
      protocols:
        agent2Agent:
          version: '1.0'
          jsonRpcTransport:
            endpoint: a2a-json-rpc-endpoint
            streaming: true
  endpoint:
    - key: a2a-json-rpc-endpoint
      remote: agent-remote
      route:
        path: /a2a/json-rpc
remotes:
  - key: agent-remote
    baseUrl: https://youragent.com
    operations:
      - fetch
      - compute
      - other
resources:
  - key: agent-resources
    path: static/hello-world/build
permissions:
  scopes:
    - read:jira-work

Tutorials and example apps