Summary
Agnes Code currently ships with Agnes-2.5-Flash as the only available model.
Please add Agnes-2.5-Pro as a selectable model inside Agnes Code as soon as
it becomes available on the platform.
Why this matters
Agnes-2.5-Pro has been announced as the flagship model, purpose-built for
"production-grade systems, complex agent pipelines, and tasks that require
deeper reasoning over longer periods" (per the official Agnes-2.5-Flash
launch announcement). Agnes Code is exactly where that kind of long-running,
multi-file agentic work happens — reading project structure, editing across
files, running commands, and iterating on real codebases.
Right now, developers who need Pro-level reasoning for these deeper tasks
have to fall back to raw API calls outside of Agnes Code, which breaks the
project-based workspace experience the tool is designed around. Having Pro
available inside Agnes Code would let one tool cover both fast/everyday
coding (Flash) and complex, long-horizon engineering work (Pro) — without
switching context.
Requested behavior
- A model switcher/dropdown in Agnes Code to choose between
Agnes-2.5-Flash and Agnes-2.5-Pro per task or per session
- Pro should use the same account/credits system already in place, so
there's no separate plan to manage
- If Pro launches with different rate limits or pricing than Flash,
surfacing that clearly in the UI would help users choose the right
model for the job
Additional context
The official announcement already states "Agnes-2.5-Pro will join the
workspace when it becomes available" — this issue is just to register
demand and make sure Agnes Code support ships alongside (not long after)
the Pro model's platform release.
Would love to hear if this is already on the roadmap. Happy to test
early/beta access if that helps prioritize this.
Summary
Agnes Code currently ships with Agnes-2.5-Flash as the only available model.
Please add Agnes-2.5-Pro as a selectable model inside Agnes Code as soon as
it becomes available on the platform.
Why this matters
Agnes-2.5-Pro has been announced as the flagship model, purpose-built for
"production-grade systems, complex agent pipelines, and tasks that require
deeper reasoning over longer periods" (per the official Agnes-2.5-Flash
launch announcement). Agnes Code is exactly where that kind of long-running,
multi-file agentic work happens — reading project structure, editing across
files, running commands, and iterating on real codebases.
Right now, developers who need Pro-level reasoning for these deeper tasks
have to fall back to raw API calls outside of Agnes Code, which breaks the
project-based workspace experience the tool is designed around. Having Pro
available inside Agnes Code would let one tool cover both fast/everyday
coding (Flash) and complex, long-horizon engineering work (Pro) — without
switching context.
Requested behavior
Agnes-2.5-Flash and Agnes-2.5-Pro per task or per session
there's no separate plan to manage
surfacing that clearly in the UI would help users choose the right
model for the job
Additional context
The official announcement already states "Agnes-2.5-Pro will join the
workspace when it becomes available" — this issue is just to register
demand and make sure Agnes Code support ships alongside (not long after)
the Pro model's platform release.
Would love to hear if this is already on the roadmap. Happy to test
early/beta access if that helps prioritize this.