Versions: reproduced on 2026.5.28 (e932160) and 2026.6.5 (5181e4f), Linux x64, node 22.22.2, gateway as systemd user service.
Symptom: every pdf (and image) tool call fails with:
pdf failed: All image models failed (2): google/gemini-3.5-flash: Unknown model: google/gemini-3.5-flash | anthropic/claude-opus-4-8: Unknown model: anthropic/claude-opus-4-8
while the same model ids work fine as the default agent model and as explicit --model runs, and openclaw models list shows them all as text+image with auth yes:
anthropic/claude-opus-4-8 text+image 1024k no yes default,configured
google/gemini-3.5-flash text+image 1024k no yes configured
openai/gpt-5.5 text+image 195k no yes configured
Config permutations tried (same failure in all five):
- Stock setup: alias entries in
agents.defaults.models + a custom models.providers.google entry for gemini-3.5-flash.
- Explicit
agents.defaults.imageModel = { "primary": "google/gemini-3.5-flash", "fallbacks": ["anthropic/claude-opus-4-8"] } — the tool uses this list (failure order changes accordingly) but still reports Unknown model for both.
- Custom
models.providers removed entirely (models present in the bundled catalog).
agents.defaults.models alias map removed entirely.- Both removed.
Possibly-related observation: with an alias entry present and models.providers absent, an explicit agent run produces a more informative variant of the same resolver error:
FailoverError: Unknown model: google/gemini-3.5-flash. Found agents.defaults.models["google/gemini-3.5-flash"], but no matching models.providers["google"].models[] entry. Add { "id": "gemini-3.5-flash" } to models.providers["google"].models...
i.e. an agents.defaults.models entry appears to shadow the bundled catalog for that resolver. Restoring the models.providers entry fixes explicit agent runs — but never the image/pdf tool, which fails regardless of whether the model is catalog-native, provider-defined, or both.
So the media-understanding tool path appears to resolve models against a registry instance that sees neither the bundled catalog nor models.providers — same shape as #66758 (ollama) and #65450, but affecting first-party anthropic/google/openai models.
Happy to run any debug build or provide verbose logs.
Versions: reproduced on
2026.5.28 (e932160)and2026.6.5 (5181e4f), Linux x64, node 22.22.2, gateway as systemd user service.Symptom: every
pdf(and image) tool call fails with:while the same model ids work fine as the default agent model and as explicit
--modelruns, andopenclaw models listshows them all astext+imagewith authyes:Config permutations tried (same failure in all five):
agents.defaults.models+ a custommodels.providers.googleentry forgemini-3.5-flash.agents.defaults.imageModel = { "primary": "google/gemini-3.5-flash", "fallbacks": ["anthropic/claude-opus-4-8"] }— the tool uses this list (failure order changes accordingly) but still reportsUnknown modelfor both.models.providersremoved entirely (models present in the bundled catalog).agents.defaults.modelsalias map removed entirely.Possibly-related observation: with an alias entry present and
models.providersabsent, an explicit agent run produces a more informative variant of the same resolver error:i.e. an
agents.defaults.modelsentry appears to shadow the bundled catalog for that resolver. Restoring themodels.providersentry fixes explicit agent runs — but never the image/pdf tool, which fails regardless of whether the model is catalog-native, provider-defined, or both.So the media-understanding tool path appears to resolve models against a registry instance that sees neither the bundled catalog nor
models.providers— same shape as #66758 (ollama) and #65450, but affecting first-party anthropic/google/openai models.Happy to run any debug build or provide verbose logs.