From f8bdd7c0cc8aecb3f3be9b390b7a5ac072f4ac3f Mon Sep 17 00:00:00 2001 From: andrewdamelio Date: Fri, 13 Feb 2026 20:24:14 +0000 Subject: [PATCH] docs(nodes): add exec cwd validation errors to troubleshooting MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add two new error codes to the troubleshooting guide: - `Exec cwd does not exist: ` — cwd doesn't exist on the node - `Exec cwd is not a directory: ` — 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. --- docs/nodes/troubleshooting.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/nodes/troubleshooting.md b/docs/nodes/troubleshooting.md index ce815cdf00e..10b1aa4ad1d 100644 --- a/docs/nodes/troubleshooting.md +++ b/docs/nodes/troubleshooting.md @@ -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: ` → 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: ` → the `cwd` path exists but is a file, not a directory. Use the parent directory instead. ## Fast recovery loop