Agent lane task fails with ENOENT: mkdir '/home/node' on macOS

Summary

Agent lane/session tasks on macOS consistently fail with:

Error: ENOENT: no such file or directory, mkdir '/home/node'

/home/node is a Linux-container convention (common in Docker images like node:22). On macOS hosts, /home doesn't exist and node's HOME is /Users/<user>. Something in the agent runner is trying to create /home/node unconditionally.

The error triggers a model fallback cascade (haiku → sonnet) and ultimately an Embedded agent failed before reply — so user-facing jobs (cron payloads, especially those with sessionTarget:"isolated") fail outright.

Environment

• macOS 15.x (darwin 24.6.0), $HOME=/Users/robcolvin
• Node 22 via Homebrew (/usr/local/opt/node@22/bin/node)
• openclaw installed globally via npm

Symptom

Both gateway instances log the error repeatedly (hourly pattern):

$ grep -c 'home/node' ~/.openclaw/logs/*.log ~/.openclaw/logs/*.err.log
gateway.err.log:1347
gateway.log:87
sugi.err.log:513
sugi.log:204

Example context:

2026-04-21T09:19:31.766  [diagnostic] lane task error: lane=main durationMs=285
  error="Error: ENOENT: no such file or directory, mkdir '/home/node'"
2026-04-21T09:19:31.771  [diagnostic] lane task error: lane=session:agent:main:main
  durationMs=291 error="Error: ENOENT: no such file or directory, mkdir '/home/node'"
2026-04-21T09:19:31.772  [model-fallback] model fallback decision: decision=candidate_failed
  requested=anthropic/claude-haiku-4-5-20251001 ... reason=unknown
  detail=ENOENT: no such file or directory, mkdir '/home/node'
2026-04-21T09:19:32.079  Embedded agent failed before reply:
  ENOENT: no such file or directory, mkdir '/home/node'

The same error appears in cron run logs (e.g., ~/.openclaw/cron/runs/afternoon-todo-send.jsonl) as the lastError for sessionTarget:"isolated" jobs.

Likely cause

A hardcoded /home/node path somewhere in the agent-runner / sandbox setup. The fact that it's being invoked hourly even without cron triggers suggests this is also fired by some internal housekeeping lane (lane=main and lane=session:agent:main:main both fail with the same error).

Expected

Resolve HOME / workspace paths via os.homedir() or environment, not hardcoded Linux conventions.

Suggested fix

• Replace any hardcoded /home/node with os.homedir() or a configurable path.
• If the path is meant for a specific container/sandbox scenario, guard it behind a platform check (only attempt on Linux / in container runtime) or make it recover gracefully (use $TMPDIR as a fallback, catch ENOENT and create under the real home dir).

Happy to grep for the offending reference if you can point me at the source repo.