V2 Workers AI ignores saved account ID when resolving the catalog endpoint

[pkyanam]

Description

V2 still requires CLOUDFLARE_ACCOUNT_ID when a Workers AI credential already contains configuration.accountId. The catalog URL contains ${CLOUDFLARE_ACCOUNT_ID}; the native OpenAI-compatible mapping does not substitute the saved account ID before endpoint validation. Initialization fails before any Cloudflare request.

The same failure occurs with providers.cloudflare-workers-ai.settings.accountId and legacy credential metadata. Setting the service environment variable works around it. Related closed proposals: #41615 and #40907.

Plugins

Built-in Cloudflare Workers AI provider.

OpenCode version

Observed on opencode2 v0.0.0-beta-19425; reproduced with a resolver regression test on current v2.

Steps to reproduce

1. Connect Workers AI with an API token and saved account ID, or configure providers.cloudflare-workers-ai.settings.accountId.
2. Leave CLOUDFLARE_ACCOUNT_ID unset in the server environment.
3. Select cloudflare-workers-ai/@cf/deepseek-ai/deepseek-v4-flash-0731 and send a message.
4. Observe CLOUDFLARE_ACCOUNT_ID is required to resolve the provider endpoint despite the saved account setting.

Screenshot and/or share link

Reproduced in a local automated resolver test; no session shared.

Operating System

macOS 26.6.2, arm64.

Terminal

Noninteractive CLI reproduction.

[rekram1-node]

Automated closure. I am an AI agent closing issues that no longer reproduce on current v2. This is not a maintainer review.

#48404 no longer reproduces on latest v2 (f30d06ea34).

The models.dev catalog still stores https://api.cloudflare.com/client/v4/accounts/${CLOUDFLARE_ACCOUNT_ID}/ai/v1, but since #48943 that template is not copied onto the native Workers AI provider. The resolver builds the endpoint from the saved account ID instead. With CLOUDFLARE_ACCOUNT_ID unset, these all resolve to https://api.cloudflare.com/client/v4/accounts/<saved-id>/ai/v1:

• a Workers AI credential configuration.accountId
• providers.cloudflare-workers-ai.settings.accountId
• legacy credential metadata.accountId

CLOUDFLARE_ACCOUNT_ID is required to resolve the provider endpoint still happens only if settings.baseURL itself still contains the unresolved ${CLOUDFLARE_ACCOUNT_ID} template. Endpoint validation substitutes environment variables only, and it runs before the saved account ID is applied. The current catalog path does not leave that template in settings.

Closing as fixed.