Not-Found on ErrorVault — Developer Error Code Dictionary

Fix clw-llm-not-found: OpenClaw LLM Provider Not Found

Tue, 11 Aug 2026 12:44:04 +0800

1. Symptoms

When OpenClaw encounters the clw-llm-not-found error, the toolchain halts execution at the point where it attempts to invoke a Large Language Model provider. Users typically observe the error manifested through several distinct indicators that signal the provider resolution failure.

In the command-line interface, the error manifests as a non-zero exit code accompanied by a descriptive message. The terminal output commonly displays a message resembling the following pattern:

[OpenClaw] ERROR clw-llm-not-found: LLM provider 'provider-name' could not be resolved.
Please verify that the provider is installed and properly configured in your openclaw.yaml.

In structured JSON output mode, the error payload includes a code field with the value clw-llm-not-found, a provider field identifying which LLM provider failed, and an optional suggestion field offering remediation guidance. The application exits with a status code typically in the range of 20 to 30, depending on the specific OpenClaw version and invocation context.

Fix docker-manifest-not-found: Manifest for image not found when pulling from registry

Fri, 03 Jul 2026 09:25:00 +0800

The docker-manifest-not-found error is a common issue encountered when attempting to pull a Docker image from a registry. It signifies that the Docker daemon was unable to locate the image manifest, which is a crucial JSON document describing the image’s layers, configuration, and architecture, for the specified image name and tag. This problem typically prevents the successful download and subsequent use of the Docker image, halting deployment or development workflows. Understanding its root causes and systematic troubleshooting steps is essential for maintaining smooth container operations.

Fix clw-api-not-found: OpenClaw API Endpoint Resolution Failure

Thu, 11 Jun 2026 22:20:04 +0800

1. Symptoms

The clw-api-not-found error manifests when OpenClaw fails to resolve or locate a required API endpoint during runtime. Developers typically encounter this error immediately after initiating a connection, running a sync operation, or attempting to access cloud resources through the OpenClaw CLI or API client.

Common symptom patterns include:

CLI command terminates with exit code 127 and the clw-api-not-found message
API calls return 404 status codes or connection failures
Configuration files appear correct but operations fail silently or with cryptic messages
The error occurs on first-time setup or after infrastructure changes

Typical error output: