Exact symptom guide · Independent guidance

Fix OpenClaw “spawn claude ENOENT”

`ENOENT` means the process could not find the executable at spawn time. Confirm that `claude` exists for the same user and environment as the Gateway, then compare the Gateway service PATH with your interactive shell. Authentication is a later check; reinstalling credentials cannot fix a missing binary.

Current snapshotUpdated 2026-08-24Official docs main snapshot · OpenClaw 2026.8.1
01

Locate the executable in the right context

  1. 1

    Check your shell

    Record the resolved path and version.

    command -v claude
    claude --version
  2. 2

    Check the Gateway owner

    A service, container, or different user can have another home and PATH.

    openclaw gateway status --json
  3. 3

    Run doctor

    Inspect backend and environment readiness without applying unrelated repairs.

    openclaw doctor --json
  4. 4

    Restart after PATH changes

    Managed services capture environment at install/reload time; verify after restart.

    openclaw gateway restart
    openclaw gateway status --require-rpc
02

Container-specific persistence

The official OpenClaw image does not preinstall Claude Code. If you install it inside a container, persist the relevant home paths and use the same non-root user for install, authentication, and execution. Recreating an image without those volumes can remove the binary while leaving unrelated OpenClaw state intact.

Primary sources

Verify against the owner.

Content snapshot follows official docs main at the recorded commit; the current package metadata reported 2026.8.1 when verified. Your installed release and live CLI schema remain authoritative.