## Summary Add Claude Opus 5.5 to the Amazon Bedrock BYOK provider. Upstream #64627 added Opus 5.5 to the Anthropic provider; this brings the same model to Bedrock. The model mirrors the Opus 5 definition: 1M context window, 128K max output, tool use, image input, prompt caching, and adaptive thinking (including xhigh effort). Cross-region inference profiles cover global, us, ca, eu, au, and jp. Opus 5.5 publishes a jp geo profile that Opus 5 does not. ## Model-level behavior Opus 5.5 carries model-level constraints, matching the Anthropic provider: - Opus 5.5 always runs adaptive thinking and rejects an explicit thinking.type.disabled opt-out, so the provider never sends one. This also fixes a substring bug where claude-opus-5-5 matched the Opus 5 request id and incorrectly received the opt-out. - Adaptive thinking does not accept sampling controls, so temperature is omitted (top_k and top_p were already unset), as the Anthropic provider does. - Forced tool use (tool_choice any) is reported as unsupported by reusing the shared anthropic::supports_forced_tool_use list, since Bedrock friendly ids match Anthropic model ids. Automatic tool use is unaffected, and no other Bedrock model changes behavior. ## Tests - bedrock: model id, request id, display name, token limits, thinking modes, and cross-region inference (including jp) for Opus 5.5. - language_models: Opus 5.5 omits the thinking opt-out and temperature, and rejects only forced tool choice. Release Notes: - Added Claude Opus 5.5 support to the Amazon Bedrock provider --------- Co-authored-by: Smit Barmase <heysmitbarmase@gmail.com> |
||
|---|---|---|
| .agents/skills | ||
| .cargo | ||
| .cloudflare | ||
| .config | ||
| .factory | ||
| .github | ||
| .wezel | ||
| .zed | ||
| assets | ||
| ci | ||
| crates | ||
| docs | ||
| extensions | ||
| legal | ||
| nix | ||
| script | ||
| tooling | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .prettierrc | ||
| .rules | ||
| AGENTS.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CLAUDE.md | ||
| clippy.toml | ||
| CODE_OF_CONDUCT.md | ||
| compose.yml | ||
| CONTRIBUTING.md | ||
| corgi.toml | ||
| default.nix | ||
| Dockerfile-collab | ||
| Dockerfile-collab.dockerignore | ||
| Dockerfile-cross.dockerignore | ||
| Dockerfile-distros | ||
| Dockerfile-distros.dockerignore | ||
| flake.lock | ||
| flake.nix | ||
| GEMINI.md | ||
| LICENSE-APACHE | ||
| LICENSE-GPL | ||
| Procfile | ||
| Procfile.web | ||
| README.md | ||
| rust-toolchain.toml | ||
| rustfmt.toml | ||
| shell.nix | ||
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking discussion)
Developing Zed
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.
Sponsorship
Zed is developed by Zed Industries, Inc., a for-profit company.
If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.