[BUG]: Bedrock Mantle models unreachable on v2 — ${AWS_REGION} in base URL is never substituted

[sergical]

Description

On the v2 path, openai.* Bedrock models (GPT-5.6 Sol/Terra/Luna, gpt-oss) can never connect. The catalog advertises the Mantle endpoint as a template, https://bedrock-mantle.${AWS_REGION}.api.aws/openai/v1, and nothing substitutes it, so the request goes to that literal hostname:

Cannot connect to API: Unable to connect. Is the computer able to access the url?
Cannot connect to API: Was there a typo in the url or port?

v1 is fine — packages/opencode/src/provider/provider.ts expands it via the bedrock loader's vars() hook (added in #31001), and provider.ts:1712 does the replacement. The v2 plugin, packages/core/src/plugin/provider/amazon-bedrock.ts, resolves a region for the SDK but leaves options.baseURL untouched; packages/core/src/aisdk.ts:80 assigns model.api.url verbatim. Other v2 plugins expand their own templates (google-vertex.ts:78, cloudflare-workers-ai.ts:64), bedrock just does not.

Same class of bug likely affects the other templated catalog URLs on v2 (${SNOWFLAKE_ACCOUNT}, ${DATABRICKS_HOST}, ${NEON_AI_GATEWAY_BASE_URL}) — none of those plugins expand either. Happy to keep this issue scoped to bedrock.

OpenCode version

opencode2 0.0.0-next-16420 (the v2 binary from @opencode-ai/cli). Also confirmed by reading dev at 1.18.11, where the failing test below was written.

Steps to reproduce

1. Configure amazon-bedrock with any working auth and "region": "us-east-1".
2. Select openai.gpt-5.6-sol on v2.
3. Send a prompt — it fails to connect. The resolved URL is https://bedrock-mantle.${AWS_REGION}.api.aws/openai/v1/responses.

Operating System

macOS 26.5.1

[alfredjophy]

Maybe related

Cannot connect to API: Unable to connect. Is the computer able to access the url?
Cannot connect to API: Was there a typo in the url or port?

Facing the same issue with kimi models too frequently since yesterday

[rekram1-node]

working on it

[opencode-agent]

Completed by #40165 on top of #40119. The Core resolver now always maps @ai-sdk/amazon-bedrock/mantle catalog entries to the native Mantle Chat/Responses provider, without requiring credential availability as a routing condition. That native provider constructs the regional Mantle endpoint itself, so the literal catalog ${AWS_REGION} URL is no longer forwarded. The mapping preserves endpoint, region, bearer/static AWS auth, headers, and supported request options, with focused resolver and native-mapping tests. Closing as resolved on the v2 branch.

[opencode-agent]

Reopening. I closed this too aggressively by treating native Mantle routing as proof that the reported regional URL failure was fully resolved. A human had reopened the issue and indicated active work, which should have blocked another automated closure. Leaving it open for maintainer verification.