Feature Request: Enable Forge app access to Rovo Agent Studio GraphQL API"

Forge
,
1

Problem

Third-party Forge apps cannot access the `agentStudio_getAgents` GraphQL API to list and manage Rovo agents.

Use Case

  • Display all Rovo agents (Built-in, Studio, Forge)
  • Filter and search agents
  • Enable programmatic agent discovery for integrations

What We’ve Tried

:white_check_mark: api.asUser().requestGraph() - “third party oauth clients not allowed”
:white_check_mark: api.asApp().requestGraph() - “UNAUTHENTICATED”
:white_check_mark: Proper permissions in manifest.yml
:white_check_mark: External fetch permissions configured

Request

Please:

  1. Enable third-party Forge apps to access agentStudio_getAgents API
  2. Provide an alternative public API for accessing Rovo agent metadata
  3. Add appropriate OAuth scopes
1 Like
2

This is a major blocker from using Forge Agents at all… Re-implementing “create page“ or “add comment“ as Forge Rovo actions feels wrong.

There should be a feature request for this.

3

@maciejswinarski I’m curious to know why you would want to access Rovo agent metadata. What use case do you have in mind? Feel free to dm me if you prefer.

4

Hey @ppasler I’m not sure that’s the same request, although certainly a valid one.

I don’t think we are tracking that as a request so have created one Jira

For some context, the reason why we haven’t done this so far is we’ve been consolidating all the skills internally onto a single registry (e.g. previously the create issue action in automation was different to the one in editor). It’s getting pretty mature now, so something we could look at exposing more publically.

1 Like
5

You’re right, it’s not the main concern here (should have used Rovo to extract the main pint :P).

But anyway, thanks for the explanation and creating a ticket!