Updates to AI model access in Rovo Dev CLI

[#1]

As part of our ongoing commitment to delivering the best AI experience for Atlassian customers, we're updating our model availability policy. These updates reflect the rapidly evolving AI landscape and ensure that existing Atlassian customers continue to receive a best-in-class experience.

What's new:

• If you’re on Rovo Dev Standard — no action is needed! Existing Atlassian customers will continue to have access to all available models as they become available.

• If you’re on a Rovo Dev trial — you'll get access to the full set of models if you continue onto a Rovo Dev Standard plan. Rovo Dev CLI and Rovo Dev in the IDE access is no longer included during the trial period.

Please note that unpaid invoices may limit your access to frontier models. In addition, customers with a Rovo Dev Standard plan on a newly created Atlassian organization may experience limited access to new models.

If you have questions about your subscription, please reach out to Atlassian support for assistance.

Interested in trialing the full capabilities of Rovo Dev?

Our team can support you in scaling developer AI across large organizations, please contact us by filling this form.

In case you missed it:

• Rovo Dev is now available in Jira — auto-complete your backlog by unleashing your favorite AI models with deep context, from plan to code.

• Team 26' is just around the corner — join the global conference for AI-forward teams, their leaders, and the apps and agents that fuel them.

🚀 Get involved and shape what's next for Rovo Dev

As we're evolving Rovo Dev, we'd love to hear what's top of mind for you! Use /feedback directly in the terminal and IDE to let us know what you think or comment below to share your thoughts.

New to Rovo Dev? 👉 Get started here

[ElEscarabajo]

That doesn't make sense. So what's the point of the 30-day trial if you won't have access to the RovoDev CLI? It just keeps getting worse—first they limited access, and now this.

[Dylan Toohey]

I'd definitely recommend reviewing the login flow via ACLI in terminal then, I had to install VSCode just to get a proper error message that indicated it was an entitlement issue. When I auth'd via ACLI in terminal it asked me to pick my site (including the site RovoDev was in trial on) and then logged in and booted rovodev fine but I couldn't access anything and the error was generic. 

After installing Rovo Dev in VSCode whilst you're on a trial, you'll get this error:

"Rovo Dev encountered an error CLI and IDE access is not available on your current plan. Please upgrade to continue using Rovo Dev in IDE."

I spent quite a bit of time troubleshooting to find its just a billing issue.

[ElEscarabajo]

If Roodev has too many errors in the CLI, it's giving me errors like...

Model not available for current subscription

The current model is only available with a paid Rovo Dev subscription. Please upgrade your subscription to access this model.

I clearly have an active subscription to the paid version. This error used to happen before, and now it's back. It's a CLI issue—please fix it.