Dr Valeri Colon (Connect Centric) Community Champion

Hi @Wakko3 — and welcome to the community! That UTF-8 error means Rovo is trying to open a file that contains characters not properly encoded in UTF-8. This can happen if a file was saved with a different encoding (like ISO-8859-1 or Windows-1252). To fix it, re-save the file using UTF-8 encoding in your text editor or…

Hi @Jin BaiWan and @Bulut Aras — thanks for raising this and welcome to the community! Rovo Dev CLI currently does not use the standard API token from your Atlassian account. Instead, it requires a special CLI token generated from the Rovo Dev Agents beta dashboard. Make sure you’re using that token and the correct…

@fan yang welcome to the community! This is another good question for https://community.atlassian.com/forums/Rovo-for-Software-Teams-Beta/gh-p/rovo-dev-ai-agents

Sounds like ya'll are problem solvers! We could use you over at https://community.atlassian.com/forums/Rovo-for-Software-Teams-Beta/gh-p/rovo-dev-ai-agents 

看起来您尝试创建的站点符合要求。您愿意将此问题发布到我们的 Rovo Dev 社区论坛吗？这样我们的团队可以更快地帮助您解决问题： https://community.atlassian.com/forums/Rovo-for-Software-Teams-Beta/gh-p/rovo-dev-ai-agents 感谢您的耐心！ It looks like the site you're trying to create meets the requirements. Would you mind posting this to our Rovo Dev Community forum so our team can take a…

Hi @Chris Ou — great use case! You're seeing a common LLM behavior: even with strict instructions, Rovo may "hallucinate" extra phrasing. While there’s no guaranteed fix yet, some users have had better results by formatting the prompt like: “Return only the email address on one line, no punctuation or explanation.” You can…

Great question, @Stefanie Lang! Rovo can support trend analysis of Atlas project updates, but for best results, give the agent a direct link to the project’s update page and limit its knowledge source to Atlassian Home. Results may vary by project—longer, detailed updates return better summaries. Invite Rovo to analyze…

Yes, you’re not alone—rolling out document agents with tailored instructions is tricky. Even strong LLMs can struggle to adapt instructions across similar formats like SOPs and How-Tos. Success often depends on narrowing scope, simplifying instructions, and anchoring responses to a structured template or schema. If it…

Another resource for ya'll https://community.atlassian.com/forums/Rovo-for-Software-Teams-Beta/gh-p/rovo-dev-ai-agents

@Josh Devenny is posting articles on that channel-- I'll start referring CLI questions there. @David Lewis no apology needed, there are so many resources sometimes we need 'context changes' ;)

Update, custom fields now work. Give 'em a try.

Update on custom fields-- they should be working now. Give 'em a try.

Hey David and welcome to the community — that error means the Rovo Dev CLI is trying to run an async task (like a file write or API call) outside the correct async context. It’s usually triggered during context switches or when certain commands (like create_file) run too early or after a failed task. This is likely an…

Thanks, Taner — that extra context helps! And yes, solidarity to all of us lost souls wandering the CLI wilderness... May our files someday be created without error.

Hi @Antoni Pierniczek — thanks for the detailed heads-up! This looks like this may be a known issue in the Rovo Dev CLI where file creation sometimes fails due to async errors or network handling issues, especially on macOS. Reading large files works fine since it streams in chunks, but writing seems to hit a snag. Glad…

Hi @Aman Ajmani Welcome to the Rovo community! This error indicates there’s a syntax problem in a YAML file (likely your manifest or config) that is preventing Rovo Dev CLI from starting. Specifically, the message: "while scanning a quoted scalar, found unexpected end of stream". To fix this, open your YAML or manifest…

Just stopping by to show @Shawn Doyle - ReleaseTEAM some love for sharing his brilliance. 

Hi @Two Owls in the City — thanks for flagging this and welcome to the community. Based on your screenshot, this appears to be a per-user rate limit, not related to token usage (which looks fine). These limits are designed to prevent overloading the Rovo Dev CLI with too many rapid requests. Try slowing the command…

Some really awesome Atlassians at this event! I wonder if we could get the Q&A posted to the product forum like this one: Answers to Questions @ Unleash Your Team with Rovo (Atlassian)

Thanks, @Eric Slosburg! Appreciate you flagging this to Atlassian—these kinds of reports are key to improving Rovo’s behavior. If your selected sources clearly contain the answer, it definitely sounds like something worth investigating. @Hector Menchaca or @Himanshi thoughts?

Hi @Evan — great question! As of now, Rovo Dev CLI doesn’t support background or persistent execution of agents without user prompts. It’s designed to ask for confirmation (like "Allow" or "Deny") to ensure safe and intentional action execution during testing. There’s no built-in “always allow” or persistent session flag…

💪

Hi @Bhekinhlanhla Siza Mbatha — great to have you here! At this time, you can’t reuse built-in Rovo Actions (like “create chart”) directly in your custom Forge Rovo Agent. You’ll need to create your own custom action that performs the same function using Forge APIs. If you'd like to see native Rovo actions become reusable…

Hi @Jens — great question! As of now, Rovo is only available to paid, licensed users within your Atlassian site. Guests or anonymous users do not have access to Rovo features like chat, search, or agents—even if you’re on the Premium plan.

Hi @Eric Slosburg — great question and welcome to the community. Rovo should only use the sources you select, like specific Confluence pages or Slack, but there are a couple of reasons it might still pull from Google Drive: Prompt vs. settings – Adding instructions in the prompt helps, but it’s more important to check the…

Hi @Yousra A_ — great question! Ya'll are on the right track, Rovo currently can’t access content from Marketplace apps like Stagil Tables. It only reads from native Jira fields, Confluence pages, and approved connected sources. For now, a good workaround is to copy key info into Jira custom fields or linked Confluence…

@Jack Brickey in da' house. Now you gotta stay awhile.

Great catch @Rebekka Heilmann _viadee_! You’re right—using status != Closed instead of resolution = Unresolved (or statusCategory != Done) can lead to misleading results. This is a great example of why humans as reviewers are essential in AI workflows. It’s not quite ready for Atlassian Learning, at 1 years old Rovo is…

Hi @Vuchuog — thanks for sharing this, and welcome to the community! 👋 You’re definitely not alone in running into quirks with the Rovo Dev CLI (I think it’s still in beta). Join the developer community and submit a support ticket as @Rebekka Heilmann _viadee_ mentioned. and as @Alexander Meci mentioned that /prune command…

@Apurva Shukla I grabbed all the video links in your series and added them to the Rovo Video Library in our Rovo Enablement Hub. My hopes is that the library will find its way to the new but not activated "Video" section on the Rovo Product Q&A board. cc: @Ali BenCafu @Kelly Stocker I am on the hunt for a video series I…