Forge Custom UI: Rovo Assist gateway returns 401 in app, but Rovo works in Home — how to enable prog

[Cristian Muntean]

Hi all,

I’m working on a Forge app that attempts to access Rovo programmatically via a Jira panel. My goal is for Rovo to automatically retrieve certain information from a Jira issue and provide possible solutions based on the information it has obtained from the issue.

As a user, I can open the Rovo chat in the browser (home.atlassian.com with cloudId) and talk to Rovo successfully.

From a Forge Custom UI issue panel (calling via @Forge/bridge requestJira asUser), calls to Rovo gateway endpoints return ERROR 401:

• GET /gateway/api/assist/rovo/v1/agents → ERROR 401
• POST /gateway/api/assist/rovo/v1/chat/conversation → ERROR 401 (when attempted)

In the logs I also get "Rovo proxy search failed: Authentication Required".

The app has minimal scopes (read/write Jira, read Confluence) and no external egress.

I have a few questions:

Is programmatic access to Rovo gateway endpoints supported for Forge apps at the moment (Custom UI or UI Kit)?

Are there specific settings or permissions required to allow asUser() requests from a Forge app to these endpoints?

Are there additional scopes or manifest settings needed for this to be possible?

If this API isn’t supported for apps, is there an endorsed approach to deep link into Rovo with a prefilled prompt containing informations from a Jira issue?

Thanks in advance for any help!