[BUG] ] Anthropic model picker shows claude-sonnet-4-5 instead of claude-sonnet-4-5-20250929 → requests fail with custom base URL

[Mahii1972]

Problem (one or two sentences)

Roo Code 3.28.15 lists the Sonnet 4.5 model as claude-sonnet-4-5; the Anthropic API expects the full snapshot name claude-sonnet-4-5-20250929, so calls made through a custom base URL return model_not_found errors.

Context (who is affected and when)

All users on v3.28.15 (commit 7734b29) who configure Anthropic with a custom endpoint that requires snapshot-style names are unable to invoke Sonnet 4.5.

Reproduction steps

• Install Roo Code v3.28.15 in VS Code.

• Open Settings → “API Provider”, choose Anthropic, and set a custom base URL.

• Expand the model dropdown; Sonnet 4.5 appears as claude-sonnet-4-5 instead of the snapshot string.

• Send a simple chat request with that model selection.

• Observe the 400/404 response: model_not_found: claude-sonnet-4-5

Expected result

The model picker should expose claude-sonnet-4-5-20250929, matching Anthropic documentation and Vertex AI naming guides.

Actual result

Only the alias claude-sonnet-4-5 is available; the request fails when routed through endpoints that require exact snapshot IDs.

Variations tried (optional)

Using the built-in Anthropic endpoint succeeds because it maps the alias internally, but any proxy or relay demanding snapshot names fails identically. Works well with Cline.

App Version

3.28.15 (7734b29)

API Provider (optional)

Anthropic

Model Used (optional)

Expected: claude-sonnet-4-5-20250929

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I'm exploring a potential fix for this issue where the Anthropic model picker shows the alias instead of the full snapshot name. I'll open a PR to share progress.

[roomote]

Opened a PR with my attempt at addressing this issue: #8546

The fix maps the alias claude-sonnet-4-5 to the full snapshot name claude-sonnet-4-5-20250929 when making API calls, which should resolve the model_not_found errors when using custom base URLs that require exact snapshot IDs.

Feedback welcome!