Rovo Dev CLI quit working and I am totally SOL

[Rick H]

I've been using rovo dev beta for 2 weeks or so and love it! But it stopped working yesterday and still not working. The CLI quit, which has happened before, but I've always been able to just re-run it with: acli rovodev run. But now when I do that, it looks like it starts running and then I just get the following over and over:

Rovo Dev CLI is not enabled on your site ───────────────────────────────────────────────────────────────────────────╮
│ │
│ To use Rovo Dev CLI, enable it in Rovo Dev Agents settings. │
│ │
│ Visit: https://rickhoro.atlassian.net/dev-agents/rovo-dev-cli │
│ │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ To resume your session, restart Rovo Dev CLI with the --restore flag. │
╰───────────────────────────────────────────────────────────────────────────────

I tried disabling Rovo Dev CLI and reenabling on your website, I've tried logging out and logging back in using: acli rovodev auth login (after logout), I tried it on another machine, I deleted the atlassian directory in my home dir so it would be recreated, and I created a new API token, but I keep getting the same behavior.

Version info:

acli rovodev --version
Rovo Dev CLI: 0.9.2
Operating System: Linux 6.12.10-76061203-generic (x86_64)
Git: git version 2.43.0

[Peter Wu]

Hi @Rick H is this still happening after updating to latest version?

[A2K]

Yes, it happens at times. It happened to me without updating so I updated and it was same error.

But I found a fix last time & retried it again by creating new API key again & that worked - https://community.atlassian.com/forums/Rovo-for-Software-Teams-Beta/Error-authentication-failed/m-p/3061763#M175 (see my comment here)

[Jovana Dunisijevic]

Hey @Rick H & @A2K 

Can I quickly check which versions of CLI you are currently running?

We've had another release and 0.9.2 is outdated already.

And if you can share if this issue is still happening?

Kindest regards,

Jovana