| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
The following comment was made by an LLM, it may be inaccurate: |
Sorry, something went wrong.
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
Sorry, something went wrong.
|
@rekram1-node hey just FYI -> I think bedrock is switching from recommending mantle to recommending runtime again with the distinction of multiple API's
I think at some point we should be able to throw away the mantle specific stuff -> It's very annoying to deal with models not supported in different regions with mantle, and this would eventually simplify a lot of that effort with the CRIS profiles (US, Global) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Issue for this PR
Closes #
Type of change
What does this PR do?
Amazon Bedrock Runtime now supports OpenAI Responses, OpenAI Chat Completions, and Anthropic Messages alongside Converse. This PR adds explicit entrypoints for each API while keeping Converse as the default:
The routes reuse OpenCode's existing protocol implementations and Bedrock authentication.
API support varies by model. The intended routing is:
Next steps
A follow-up models.dev change should assign each Bedrock model its preferred API, allowing OpenCode to select the route automatically. For example, the existing Amazon Bedrock provider and a model-specific Responses selection in models.dev could look like:
providers/amazon-bedrock/models/global.openai.gpt-5.6-sol.toml
Suggested values are responses, chat, messages, and converse. A separate api_type field avoids overloading the existing provider.api field, which currently contains a base URL.
Add api_type to models.dev's model-level [provider] schema and generated API output. Then update OpenCode's models.dev normalization to map it to the matching @opencode/ai/providers/amazon-bedrock/* package, falling back to Converse when omitted.
How did you verify your code works?
Added tests for route selection, Runtime URLs, SigV4 signing, API-key headers, and package loading. Also ran the existing Bedrock Converse tests and bun run check.
Screenshots / recordings
Not applicable; this is not a UI change.
Checklist