Add Claude Opus 4.6 support across providers

[PeterDaveHello]

Description

Add support for Claude Opus 4.6 across providers and align 1M context behavior/UI copy.

Key implementation details:

• Added Opus 4.6 model definitions and pricing metadata for Anthropic, Bedrock, Vertex, OpenRouter, and Vercel AI Gateway.
• Added Opus 4.6 to prompt-caching / reasoning-capable model sets where applicable.
• Updated Anthropic and Bedrock provider handling so Opus 4.6 participates in existing 1M context and prompt-caching flows.
• Updated settings UI gating logic to show the 1M context toggle for Opus 4.6.
• Updated i18n strings for 1M context descriptions across locales to mention supported Claude 4 models consistently.
• Added a changeset entry for roo-cline patch release.

Reviewer focus areas:

• Provider model IDs and pricing fields for Opus 4.6 are consistent with current provider conventions.
• 1M context toggle behavior is consistent across Anthropic, Bedrock, and Vertex paths.
• Updated i18n wording remains clear and consistent across locales.

Test Procedure

Commands run:

• pnpm --filter @roo-code/types test
• pnpm --filter @roo-code/vscode-webview test (run with elevated permissions due to sandbox EPERM on tsx IPC during pretest bundle)
• pnpm changeset status

Observed results:

• @roo-code/types: 9 files passed, 166 tests passed.
• @roo-code/vscode-webview: 118 files passed, 1239 tests passed, 8 skipped.
• Changeset status reports roo-cline as patch.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable).
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

N/A (no visual layout or interaction changes; only model availability and provider description text updates).

Documentation Updates

• No documentation updates are required.
• Yes, documentation updates are required. (Please describe what needs to be updated or link to a PR in the docs repository).

Additional Notes

• Opus 4.6 long-context tier pricing (for >200K input tokens with 1M context) is included in model metadata.
• Existing Node engine warning (20.20.0 vs target 20.19.2) was observed during commands but did not block test/lint success.

Get in Touch

Discord: @PeterDaveHello

---

Important

Add support for Claude Opus 4.6 across providers and update 1M context handling and UI.

• Model Support:
  • Added Claude Opus 4.6 model definitions and pricing metadata in anthropic.ts, bedrock.ts, and vertex.ts.
  • Included Claude Opus 4.6 in prompt-caching and reasoning-capable model sets in openrouter.ts and vercel-ai-gateway.ts.
• 1M Context Handling:
  • Updated 1M context toggle logic for Claude Opus 4.6 in anthropic.ts, bedrock.ts, and vertex.ts.
  • Adjusted AnthropicHandler and AwsBedrockHandler to support 1M context for Claude Opus 4.6.
• UI and i18n:
  • Updated settings UI to show 1M context toggle for Claude Opus 4.6 in Anthropic.tsx, Bedrock.tsx, and Vertex.tsx.
  • Updated i18n strings in multiple locale files to include Claude Opus 4.6 in 1M context descriptions.
• Misc:
  • Added a changeset entry for roo-cline patch release.

^{This description was created by for 5c3c468. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Rooviewer   See task on Roo Cloud

Review complete. No issues found.

The PR correctly adds Claude Opus 4.6 support across Anthropic, Bedrock, Vertex, OpenRouter, and Vercel AI Gateway with consistent model definitions, proper 1M context integration, and appropriate i18n updates.

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[hannesrudolph]

Thanks for the quick PR on this, @PeterDaveHello! We're closing this in favour of #11224, which is being handled internally.