anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[PR #6916] fix(provider): add support for jp. prefix in Amazon Bedrock cross-region inference profiles #12161

New Issue
Closed
opened 2026-02-16 18:17:05 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:17:05 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/anomalyco/opencode/pull/6916

State: closed
Merged: Yes

Problem

When using Amazon Bedrock with the jp. cross-region inference profile prefix (e.g., jp.anthropic.claude-sonnet-4-5-20250929-v1:0), OpenCode incorrectly adds an additional region prefix, causing the model invocation to fail.

Currently, OpenCode only skips region prefixing for models starting with global., but AWS Bedrock also provides a jp. (Japan) cross-region inference profile, which is required for using certain models in the ap-northeast-1 (Tokyo) region.

Example

When configuring:

{
  "model": "amazon-bedrock/jp.anthropic.claude-sonnet-4-5-20250929-v1:0"
}

With AWS_REGION=ap-northeast-1, OpenCode currently transforms this to apac.jp.anthropic.claude-sonnet-4-5-20250929-v1:0, which is invalid.

Solution

Add jp. to the list of prefixes that skip automatic region prefixing, alongside the existing global. prefix.

Changes

  • Modified packages/opencode/src/provider/provider.ts to recognize jp. prefix as a cross-region inference profile prefix that should not have additional region prefixes added.

Background

The jp. prefix is a Japan-specific cross-region inference profile provided by AWS Bedrock. Unlike the apac. prefix (which covers broader Asia Pacific regions), the jp. prefix routes requests specifically to the Japan (Tokyo) region infrastructure.

Some models like Claude Sonnet 4.5 are available with the jp. inference profile but not with the apac. profile, making this fix necessary for users in the Japan region.

Testing

Tested with:

  • Model: jp.anthropic.claude-sonnet-4-5-20250929-v1:0
  • Region: ap-northeast-1
  • Result: Model invocation succeeds without incorrect prefix transformation
**Original Pull Request:** https://github.com/anomalyco/opencode/pull/6916 **State:** closed **Merged:** Yes --- ## Problem When using Amazon Bedrock with the `jp.` cross-region inference profile prefix (e.g., `jp.anthropic.claude-sonnet-4-5-20250929-v1:0`), OpenCode incorrectly adds an additional region prefix, causing the model invocation to fail. Currently, OpenCode only skips region prefixing for models starting with `global.`, but AWS Bedrock also provides a `jp.` (Japan) cross-region inference profile, which is required for using certain models in the `ap-northeast-1` (Tokyo) region. ### Example When configuring: ```json { "model": "amazon-bedrock/jp.anthropic.claude-sonnet-4-5-20250929-v1:0" } ``` With `AWS_REGION=ap-northeast-1`, OpenCode currently transforms this to `apac.jp.anthropic.claude-sonnet-4-5-20250929-v1:0`, which is invalid. ## Solution Add `jp.` to the list of prefixes that skip automatic region prefixing, alongside the existing `global.` prefix. ## Changes - Modified `packages/opencode/src/provider/provider.ts` to recognize `jp.` prefix as a cross-region inference profile prefix that should not have additional region prefixes added. ## Background The `jp.` prefix is a Japan-specific cross-region inference profile provided by AWS Bedrock. Unlike the `apac.` prefix (which covers broader Asia Pacific regions), the `jp.` prefix routes requests specifically to the Japan (Tokyo) region infrastructure. Some models like Claude Sonnet 4.5 are available with the `jp.` inference profile but not with the `apac.` profile, making this fix necessary for users in the Japan region. ## Testing Tested with: - Model: `jp.anthropic.claude-sonnet-4-5-20250929-v1:0` - Region: `ap-northeast-1` - Result: Model invocation succeeds without incorrect prefix transformation
yindo added the pull-request label 2026-02-16 18:17:05 -05:00
yindo closed this issue 2026-02-16 18:17:05 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#12161
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?