{"version":"2.1.59","anchor":"opus-4-6-model-routing-gradual-rollout","canonical_anchor":"opus-4-6-model-routing-gradual-rollout","heading":"Opus 4.6 Model Routing [Gradual Rollout]","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.59\/e\/opus-4-6-model-routing-gradual-rollout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.59","markdown":"### Opus 4.6 Model Routing [Gradual Rollout]\n\n**What**\n\nInfrastructure for routing requests to the Opus 4.6 model when a `coral_reef_opus` feature flag is enabled server-side.\n\n**Status**\n\nFeature-flagged via `coral_reef_opus`\n\n**Details**\n\n- When `coral_reef_opus` is `\"true\"` and the model string contains `\"opus-4-6\"`, a special token limit of 1,000,000 is applied\n- Extended output is enabled for matching Opus 4.6 models via the `HbA()` function\n- Gated behind multiple checks: not in test mode, not using custom provider\n\n**Evidence**\n\nModel routing (search for `\"coral_reef_opus\"`, `\"opus-4-6\"`)"}