nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Custom Rovo agent access to custom content

Habib ZOUARI

I've created a custom Rovo agent in Forge app installed in confluence workspace. As I know Atlassian built-in Rovo agents can access and retrieve confluence page/space content automatically, so I want to know if it's possible that my custom Rovo agent would have the same or not , or if there are specific configurations, permissions or whatever needed to reach that. I'm asking that because I tried to use my custom agent with some confluence tasks and mostly the agent didn't respond properly.

Also, I want to know if this custom agent is able to access custom content , means that I need the agent to manipulate some tasks inside my custom content app

Accepted answers

Dr Valeri Colon (Connect Centric)

Welcome to the community @Habib ZOUARI Custom Rovo agents don’t get automatic access to all Confluence content. They can only use the knowledge sources you attach and whatever your Forge app passes in, and your app must have the proper scopes to read those spaces or pages. They also can’t access custom app data unless your Forge app retrieves it and includes it in the prompt. If responses seem incomplete, it usually means required spaces weren’t added as knowledge or the app lacks read permissions.

All comments

Dr Valeri Colon (Connect Centric)

Habib ZOUARI

Thank you for your response! @Dr Valeri Colon _Connect Centric_

How do I attach knowledge sources (Confluence spaces/pages/or even customcontent) to my custom Rovo agent? Is this done through:

The manifest file configuration?
The Rovo admin panel at admin.atlassian.com?
Or programmatically through the Forge API?

Could you please point me to documentation or provide an example of how to attach Confluence spaces as knowledge sources to a custom Forge Rovo agent?

Dr Valeri Colon (Connect Centric)

Great questions, @Habib ZOUARI For custom Rovo agents built in Forge, knowledge sources aren’t attached in the manifest or via API today. They’re added the same way you configure knowledge for any other agent. Go to admin.atlassian.com → Rovo → Agents → Knowledge and attach the spaces or pages you want. Custom app data isn’t indexed automatically, so your Forge app must retrieve that content and pass it into the agent.

https://developer.atlassian.com/platform/forge/extend-atlassian-products-with-a-forge-rovo-agent/

Habib ZOUARI

Hello again @Dr Valeri Colon _Connect Centric_ hope you're doing well.

I have some several questions if you have some answers I would be grateful.

When a Forge custom Rovo Agent is asked to generate a large volume of structured content (e.g. a full course with multiple sections and components) in a single conversation turn, the LLM that powers the Rovo Agent silently truncates its output mid-generation. Because action inputs are constructed from the LLM's raw output, the truncated content results in malformed (non-parseable) JSON being passed to the action handler ,causing the action to fail or receive incomplete data. So i need to know if :

Is there an official, documented token/character limit on the LLM output that populates action inputs for Forge Rovo Agents?
Is there a plan to expose a structured truncation signal to action handlers?
Is there an alternative solution to maintain the generated large content with the same number of components?

Your help is appreciated !

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

rovo-atlassian-intelligence