Skip to content

[Bug]: Google vertex models cannot be overriden via openclaw.json #96600

Closed

Description

@randompup

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

The manual override to google-vertex model providers through openclaw.json doesn't work

Steps to reproduce

  1. Add a custom model for google-vertex in openclaw.json
  2. Restart the gateway
  3. See the list of registered models for google-vertex

Expected behavior

It should accept the user overrides from openclaw.json and show the additional models in the model list

Actual behavior

openclaw models list --provider google-vertex --all

OpenClaw 2026.6.10 (aa69b12) — If you can describe it, I can probably automate it—or at least make it funnier.

Model Input Ctx Local Auth Tags
google-vertex/gemini-2.5-flash text+image 1024k no yes fallback#1,configured,alias:Gemini Flash
google-vertex/gemini-2.5-flash-lite text+image 1024k no yes
google-vertex/gemini-2.5-pro text+image 1024k no yes default,configured,alias:Gemini Pro
google-vertex/gemini-3-flash-preview text+image 1024k no yes
google-vertex/gemini-3.1-flash-lite text+image 1024k no yes
google-vertex/gemini-3.1-pro-preview text+image 1024k no yes

OpenClaw version

2026.6.10

Operating system

Ubuntu 26.04

Install method

npm global

Model

google-vertex

Provider / routing chain

openclaw -> google-vertex

Additional provider/model setup details

Config for openclaw.json

"models": {
"mode": "merge",
"providers": {
"google-vertex": {
"api": "google-vertex",
"models": [
{
"id": "gemini-3.5-flash",
"name": "Gemini 3.5 Flash (Vertex AI)"
}
]
}
}
},

Logs, screenshots, and evidence

Impact and severity

Affected: anyone using google-vertex models
Severity: Breaks any custom or newer models not in the catalog
Frequency: Always for custom models
Consequence: Limit to static models only

Additional information

No response

Activity

  1. clawsweeper commented on Jun 24, 2026

    @clawsweeper
    Contributor

    Thanks for the context here. I did a careful shell check against current main, and this is already implemented.

    Close: current main now covers the reported Google Vertex override path well enough through configured provider row listing, Vertex ADC catalog auth preservation, and a static catalog row for the exact reported model; the broader live Vertex discovery request remains separate.

    I found the merged PR that appears to have closed this: #97123: feat(codex): add always plugin approval mode.

    So I’m closing this as already implemented rather than keeping a duplicate issue open.

    Review details

    Best possible solution:

    Keep the current main configured-provider and Vertex ADC catalog behavior, and leave live dynamic Vertex discovery to the separate product discussion at #96597.

    Do we have a high-confidence way to reproduce the issue?

    Yes. The v2026.6.10 report gives concrete openclaw models list --provider google-vertex --all output, and current source shows the corresponding configured-provider and ADC catalog-auth paths that now handle it.

    Is this the best way to solve the issue?

    Yes. Reusing the existing models.providers.*.models and provider catalog/auth normalization paths is the narrow maintainable fix; adding another override surface would duplicate the documented config contract.

    Security review:

    Security review: Non-PR issue triage; no patch security review applies.

    AGENTS.md: found and applied where relevant.

    What I checked:

    • Configured provider rows are listed on current main: Provider-filtered and --all model lists append configured models.providers.*.models rows, and rows are eligible when the provider or model declares an API, matching the reporter's provider-level api config shape. (src/commands/models/list.rows.ts:354, c5d34c8376f8)
    • Provider-filtered model source path calls configured rows: The all/provider-filtered source cascade calls appendConfiguredProviderRows after catalog rows, so arbitrary non-catalog provider models are added when not already seen. (src/commands/models/list.row-sources.ts:79, c5d34c8376f8)
    • Explicit Google Vertex models inherit implicit provider metadata: mergeProviders starts from implicit provider catalog entries and merges explicit provider models back into the provider, preserving the built-in Vertex base URL when user config only adds model rows. (src/agents/models-config.merge.ts:129, c5d34c8376f8)
    • Missing Vertex provider apiKey is filled before writable filtering: Current normalization resolves a missing provider apiKey from env, ADC auth evidence, or auth profiles before filterWritableProviders requires baseUrl and apiKey for providers with model rows. (src/agents/models-config.providers.secret-helpers.ts:312, c5d34c8376f8)
    • Google Vertex exact reported model is now cataloged: The shared Google/Vertex static catalog on current main includes gemini-3.5-flash, so the exact model in the report no longer depends on manual override to appear. (extensions/google/provider-catalog.ts:39, c5d34c8376f8)
    • Regression coverage for Vertex ADC catalog auth exists: Current tests cover writing Google Vertex catalog rows when auth profiles or ADC auth evidence provide the provider auth marker. (src/agents/models-config.applies-config-env-vars.test.ts:470, c5d34c8376f8)

    Likely related people:

    Codex review notes: model internal, reasoning high; reviewed against c5d34c8376f8; fix evidence: merged PR #97123, commit c5d34c8376f8, main fix timestamp 2026-06-27T01:19:00-07:00.

  2. added
    P2Normal backlog priority with limited blast radius.
    impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.
    issue-rating: 🦐 gold shrimpDecent issue quality, but reproduction details are still incomplete.
    clawsweeper:needs-infoClawSweeper needs more reporter information before it can verify this issue.
    clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.
    clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.
    on Jun 25, 2026
  3. locked as resolved and limited conversation to collaborators on Jul 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.bugSomething isn't workingbug:behaviorIncorrect behavior without a crashclawsweeper:needs-infoClawSweeper needs more reporter information before it can verify this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.issue-rating: 🦐 gold shrimpDecent issue quality, but reproduction details are still incomplete.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions