Rovo Dev agent crashes on new chat

[hortfrancis]

Bug report

Background context

I work in University College London as a software engineer. We use Jira to manage all our work items. I am working in React (we are building a framework). I am interested in AI-driven workflows. We use:

• GitHub for source control
• VSCode for local development
• WSL (Ubuntu) on work-issued Windows 11 laptops

The Rovo chat inside Jira's web app is pretty good, I've been finding it useful, and I'd like to connect to more context.

Description of bug

Rovo Dev crashes when a new chat is started, and when the extension is first initialised, when VSCode starts.

My system

• WSL2 environment (running inside Windows 11)
• Linux distro: Ubuntu 24.04.2 LTS (Noble Numbat)
• Linux kernel: 6.6.87.2-microsoft-standard-WSL2
• Architecture: x86_64
• VS Code environment: Remote – WSL
• Hosting OS: Windows 11 (work laptop)

Additional notes

ChatGPT 5.1 believes this is caused by the use of commas between arguments in the Shell command, which is not accepted in a Linux environment.

[bwieger-atlassian-com]

Thank you for the details! I'm going to try to reproduce this issue.

[bwieger-atlassian-com]

@hortfrancis I haven't been able to reproduce.

Can you share which version of the extension you are on?

[bwieger-atlassian-com]

@hortfrancis can you also share screenshot/video of the "Rovo Dev: Show in Terminal" output? You can find this in the command pallete

[Hadi99K]

i have the same problem

[thomaspcruise]

@bwieger-atlassian-com If I copy the command without the commas it executes successfully. Version 4.1.48 of the Extension.

Here's a video of the terminal when I start a new chat with rovo in the sidebar.
It goes quick, the error appears to be that it believes the registered site is invalid.

https://github.com/user-attachments/assets/e9f1ff88-15db-4519-b7a1-27cd2192da99

[hortfrancis]

@hortfrancis I haven't been able to reproduce.

Can you share which version of the extension you are on?

Hi @bwieger-atlassian-com, I've just checked and I'm on 4.0.8

[hortfrancis]

I just switched it to the 'pre-release' version to check, and it presents the same (if that's helpful):

@bwieger-atlassian-com

[hortfrancis]

This is what I'm getting in the terminal output, @bwieger-atlassian-com:

It still seems to be logged in ok for other Jira operations (looking at tickets, etc).

Is it anything to do with the subscription package for my org, maybe? Or a feature that needs to be turned on inside Jira's settings?

[bwieger-atlassian-com]

@hortfrancis In this case, you need to have Rovo Dev entitlement. You may need your admin to get this.

Do you have Rovo Dev entitlement?

And I'll raise this as a ticket to the team to make this error more discoverable

[bwieger-atlassian-com]

@thomaspcruise It sounds like you are facing the same problem as hortfrancis.

Here's what I share with him

In this case, you need to have Rovo Dev entitlement. You may need your admin to get this.
Do you have Rovo Dev entitlement?
And I'll raise this as a ticket to the team to make this error more discoverable

[thomaspcruise]

@bwieger-atlassian-com Yeah I figured as much. We have Rovo enabled, but we haven't received a rollout email for Rovo Dev yet, so I guess we have to wait for that first.