I've been using rovo dev beta for a week or so and love it! But it stopped working about 2 hours ago. 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, I've tried logging out and logging back in using: acli rovodev auth login (after logout), but I keep getting the same behavior.
Version info: (just upgraded and created a new API key)
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
Hello @Rick H
Welcome to Atlassian Community!
Can you please post this on our Rovo Dev Beta Forum?
Thanks!
@Rick H @S That loop happens when the site-level Dev CLI flag is out of sync. Even if it shows “enabled,” the backend sometimes drops the entitlement. Have your org admin toggle Rovo Dev CLI off/on from Admin → Rovo Dev Agents, then recreate the API key. If the message persists, open a support ticket—the issue is on Atlassian’s side, not your local setup.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.