I’ve come across an issue with Rovo while working on a Confluence app that includes a custom Rovo Agent.
Here’s what I’ve observed:
If my app is installed after Rovo is activated on a site, my custom agent becomes available immediately.
However, if Rovo is activated after my app has already been installed, the custom agent does not appear for users. It’s completely missing from the browse agents dialog as well.
The only way to resolve this is by redeploying my app, after which the agent becomes available. However, this workaround isn’t ideal, especially in production environments where seamless functionality is critical.
The activation of Rovo for a site involves setting up the initial set of default Agents, but it appears this setup doesn’t take into account installed apps that provide Rovo modules.
Steps to reproduce
Install a Forge app that includes a Rovo Agent module in a site for which Rovo is not already activated.
Activate Rovo for the site.
Observe the Agents available.
Expected result
At step 3, the set of available Agents includes the Agent provided by the Forge app.
Actual result
At step 3, the set of available Agents does not include the Agent provided by the Forge app.
Notes
Re-deploying the app after Rovo has been activated in a site will make the app’s Agent available, but this is not considered a viable workaround.
