Repository navigation
feat: add Claude Opus 5 support - #8464
Conversation
|
Thanks for this — verified the model ID, context window, and pricing for Claude Opus 5 all match the current official spec, and confirmed there was no existing catalog entry for it on I ran the full test suite for the touched area in an isolated checkout (331 tests, 0 failures), The Claude Code client-identity version bump (2.1.207 → 2.1.219) bundled in alongside the Opus 5 work makes sense as a coupled change (OAuth identity gating needs the real captured client version), so we're keeping it as-is rather than asking you to split it out. This is merge-ready as submitted — no changes requested. Thank you for the thorough work, including the new regression tests. |
|
Merged into |

What changed
2.1.219across code, environment defaults, snapshots, tests, and documentation.Why
The provider catalogs and Claude request paths still assumed earlier Claude generations, while Claude Code identity values were duplicated and had drifted. This prevented consistent Opus 5 routing and produced mismatched behavior between API, web, and Copilot transports.
Impact
OmniRoute can advertise and route Claude Opus 5 through the verified providers with consistent thinking, pricing, fallback, and client identity behavior. Fable 5 remains first in the flagship model ordering.
Validation
npm run typecheck:corenpm run check:docs-all