Hi, I’m building a Rovo agent for Codegeist 2026 and need help testing it.
What I did:
- Created an app with Forge CLI 14.2.0 using the rovo-agent template
- forge deploy to development, forge install on my free developer site (hashir-dev.atlassian.net), Confluence product
- App shows as installed in admin.atlassian.com > Connected apps
- forge tunnel runs fine, no lint errors
Problem:
Rovo is not visible anywhere on the site. No Rovo button bottom-right, no “Ask Rovo” in the top bar, and /ai in the Confluence editor only shows a paste menu (Markdown / Plain text). The search bar only says “Ask AI”. On home.atlassian.com there is no Rovo chat or agents list either.
What I checked:
- Billing shows Rovo on the Free plan with credits included
- Rovo access page: blocklist is empty
- Rovo settings: Beta features on
- Admin Agents page shows “No agents”
- /rovo and /rovo/agents return 404
Questions:
- How do I activate Rovo chat on a free developer site so I can test my Forge agent?
- Is a different site type or the Atlassian Cloud Developer License site needed?
- Is there another supported way to test a rovo:agent (besides forge tunnel and forge logs)?
Thanks!
Hi @HashirAbdullah, skip the dev site and test on a Forge demo site. It ships “enterprise editions of Jira, Confluence, Jira Service Management, and Rovo”.
npm install -g @forge/cli@latest
forge site provision
forge deploy
forge install --demo-site
Each developer gets one. It stays active for 90 days by default.
That covers your second question too. A new Cloud Developer Bundle site is still the same free site. The one in 103575 showed “Rovo is disabled on this site”.
The free plan is likely part of it. The pricing page lists Rovo for Standard, Premium and Enterprise only. That thread’s Premium trial was disabled too, though, so a trial is a gamble.
On the demo site the agent should appear in Rovo Chat, with tunnel and logs as now. I haven’t run provision myself, so shout if it refuses.
I had the same problem on a free developer site: no Chat button, and an empty Agents list in admin even with nothing on the Rovo blocklist. A Forge demo site fixed it for me today (Nov 10).
forge site provision
forge install --demo-site --product jira -e development
Notes:
- On CLI 14.2.0 the provision command printed “Status: FAILED”, but the site had actually been created. Run
forge site provision again and it shows the existing site’s URL.
- The demo site has Rovo Chat. My agent showed up under “Change agent” by searching its name, and its actions ran, including the confirmation card for a CREATE action.
- One demo site per developer, active for 90 days.
Hope this helps others in Codegeist.