Skip to main content

Vision and image description

The bundled Ollama plugin registers Ollama as an image-capable media-understanding provider, so OpenClaw can route explicit image-description requests and configured image-model defaults through local or hosted Ollama vision models.
--model must be a full <provider/model> ref; when set, infer image describe tries that model first instead of skipping description for models that already support native vision. If the call fails, OpenClaw can continue through agents.defaults.imageModel.fallbacks; file/URL preparation errors fail before fallback is attempted. Use infer image describe for OpenClaw’s image-understanding flow and configured imageModel; use infer model run --file for a raw multimodal probe with a custom prompt. To make Ollama the default image-understanding provider for inbound media:
Prefer the full ollama/<model> ref. A bare imageModel ref such as qwen2.5vl:7b normalizes to ollama/qwen2.5vl:7b only when that exact model is listed under models.providers.ollama.models with input: ["text", "image"] and no other configured image provider exposes the same bare id; otherwise use the provider prefix explicitly. Slow local vision models can need a longer image-understanding timeout than cloud models, and can crash on constrained hardware if Ollama tries to allocate the model’s full advertised vision context. Set a capability timeout and cap num_ctx:
This timeout applies to inbound image understanding and to the explicit view_image tool. models.providers.ollama.timeoutSeconds still controls the underlying Ollama HTTP request guard for normal model calls. Live verification:
If you define models.providers.ollama.models manually, mark vision models explicitly:
OpenClaw rejects image-description requests for models not marked image-capable. With implicit discovery, this comes from /api/show’s vision capability.