Description

The google-vertex plugin is listed in the user's plugin configuration but is not being recognized at runtime. Every command execution emits a config warning and the provider is completely absent from the loaded providers list, making it impossible to authenticate or use Google Vertex AI models.

Environment

• OpenClaw version: 2026.3.23-2 (7ffe7e4)
• OS: Linux (jarvis)
• Command: openclaw plugins list --json, openclaw models auth login --provider google-vertex --set-default

Steps to Reproduce

1. Have google-vertex listed in the plugins config (e.g. plugins.entries.google-vertex).
2. Run any openclaw command.
3. Observe the config warning on every execution:

   Config warnings:
   - plugins.entries.google-vertex: plugin not found: google-vertex (stale config entry ignored; remove it from plugins config)
   

4. Attempt to authenticate with the provider:

   openclaw models auth login --provider google-vertex --set-default

Actual Behavior

Error: Unknown provider "google-vertex". Loaded providers: anthropic, byteplus, chutes, ..., google-gemini-cli, ...
Verify plugins via `openclaw plugins list --json`.

The plugin is silently ignored and the provider is not loaded. google-gemini-cli is loaded, but google-vertex is not.

$ openclaw plugins list --json | grep "google-"
# Only outputs: "google-gemini-cli"
# "google-vertex" is absent

Expected Behavior

• Either the google-vertex plugin resolves and loads correctly, exposing the provider for authentication and model usage.
• Or, if the plugin is deprecated/renamed, the CLI should:
  • Provide a clear migration message (e.g., "google-vertex has been renamed to X, please update your config").
  • Offer an automated config migration or at minimum a --fix flag to clean up stale entries.

Additional Context

• google-gemini-cli is available as a separate provider, which suggests Google Vertex may have been split out or renamed at some point.
• The warning message says "stale config entry ignored; remove it from plugins config" but provides no guidance on what the replacement plugin name is, if any.
• This affects any user who had google-vertex configured prior to whatever change introduced this regression.

Possible Solutions

• Re-add / re-publish the google-vertex plugin package so it can be resolved.
• Add a config migration step that automatically remaps google-vertex to the correct current plugin name.
• Improve the warning message to include the correct replacement plugin name or a docs link.