Claude models 1m token

ElEscarabajo

Feature Request: Model Selection & Expanded Model Options in RovoDev

Overview
Currently, the 200K token model limit is restrictive for extended development workflows in RovoDev. It would significantly improve usability to provide more flexibility in model selection and context size.

Requested Improvements

1. Model Selection خيار (User Choice)

   • Allow users to choose between different context sizes:

     • 200K token model (lighter, faster)

     • 1M token model (for large-scale tasks, long context sessions)

2. Upgrade Existing Models

   • Extend the 1M token context to additional models, not just Opus 4.7

   • Specifically:

     • Keep Opus 4.7 with 1M tokens

     • Add Opus 4.6 with 1M token support as well

3. Add More Model Options

   • Integrate additional model families to increase flexibility:

     • Gemini models (for diversity in reasoning and performance styles)

Why This Matters

• 200K tokens run out quickly in real-world development workflows (large codebases, long chats, multi-file context)

• A 1M token option enables:

  • Better continuity in long sessions

  • Handling full projects without constant resets

  • Improved productivity and fewer interruptions

Expected Impact

• More control for developers depending on task size

• Better resource management (use small vs large context as needed)

• Increased adoption and satisfaction among power users

---

Summary
Give users the ability to choose their model + expand 1M token availability across more models + include Gemini options.

---

Trudy P Claspill

Hello @ElEscarabajo 

Using the Questions forum to submit a feature request is not the most effective way to ensure Atlassian receives the information.

A better method is to open a support case, or to use the Provide Feedback options in the products when that option is available.