I have an issue in VS code plugin always shows an error Agent process terminated Rovo Dev process te

[prudhviranga_chitturi]

Agent process terminated

Rovo Dev process terminated with exit code 1.
Please start a new chat session to continue.


The terminal process "c:\Users\XXXXX\AppData\Roaming\Code\User\workspaceStorage\e77878cf2b8b0301d516684ff0d98818\atlassian.atlascode\atlascode-rovodev-bin\0.12.10\atlassian_cli_rovodev.exe 'serve', '40000', '--xid', 'rovodev-ide-vscode', '--site-url', 'https://XXX.atlassian.net', '--respect-configured-permissions'" terminated with exit code: 1.

[Dr Valeri Colon _Connect Centric_]

@prudhviranga_chitturi That error usually shows up when the rovodev process can’t start cleanly in VS Code—most often from a corrupted local .rovodev cache or a permission conflict. Try closing VS Code, deleting the .rovodev folder under your user profile, then relaunching the plugin so it rebuilds. If it keeps exiting with code 1, re-auth in the plugin and verify the site URL is correct.

[Elliot Silver]

For what it's worth, aslo seeing this on WSL in windows 11:

The terminal process "/home/<user>/.vscode-server/data/User/workspaceStorage/dc3d8ac76c4e74203d9c504da45f668a/atlassian.atlascode/atlascode-rovodev-bin/0.12.16/atlassian_cli_rovodev 'serve', '40000', '--xid', 'rovodev-ide-vscode', '--site-url', 'https://<corp>.atlassian.net', '--respect-configured-permissions'" terminated with exit code: 1.

[Tony Jackson]

Same here - "Rovo Dev process terminated with exit code 1" with a fresh VSCode extension installation and API key.

[Scott Vail]

I encountered the same thing, but I was able to run the agent manually by copying CLI command, removing the commas (","), and pasting it into a terminal. e.g.

c:\Users\XXXXX\AppData\Roaming\Code\User\workspaceStorage\e77878cf2b8b0301d516684ff0d98818\atlassian.atlascode\atlascode-rovodev-bin\0.12.10\atlassian_cli_rovodev.exe 'serve' '40000' '--xid', 'rovodev-ide-vscode' '--site-url' 'https://XXX.atlassian.net' '--respect-configured-permissions'

 So, the issue appears to be a broken integration with VS Code

[Thomas Prince]

I had the same problem on apple silicon mac, This removal of the commas worked for me too.

VS Code extension version: 4.1.48