Ayuriel/openclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(nodes): add exec cwd validation errors to troubleshooting

Browse Source 
Add two new error codes to the troubleshooting guide:

- `Exec cwd does not exist: <path>` — cwd doesn't exist on the node
- `Exec cwd is not a directory: <path>` — cwd is a file, not a dir

These errors were introduced in #15454 (node-host cwd validation).
Previously, an invalid cwd would silently fall back to $HOME, which
could cause confusing behavior. The new errors give clear guidance
on what went wrong and how to fix it.
This commit is contained in:
andrewdamelio 2026-02-13 20:24:14 +00:00
parent 1655df7ac0
commit f8bdd7c0cc
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/nodes/troubleshooting.md
View File

@ -86,6 +86,8 @@ If pairing is fine but `system.run` fails, fix exec approvals/allowlist.
- `LOCATION_BACKGROUND_UNAVAILABLE` → app is backgrounded but only While Using permission exists.
- `SYSTEM_RUN_DENIED: approval required` → exec request needs explicit approval.
- `SYSTEM_RUN_DENIED: allowlist miss` → command blocked by allowlist mode.
- `Exec cwd does not exist: <path>` → the `cwd` passed to `nodes.run` doesn't exist on the node. Verify the path exists on the remote node (not the gateway host). Remove the `cwd` parameter to use the node's default working directory.
- `Exec cwd is not a directory: <path>` → the `cwd` path exists but is a file, not a directory. Use the parent directory instead.
## Fast recovery loop