Back to articles
OpenClaw macOS Workspace Config Ignored — Bug Report and Workaround
How-ToDevOps

OpenClaw macOS Workspace Config Ignored — Bug Report and Workaround

via Dev.to DevOpslinou518

When adding a Mac Mini M1 as a new node in OpenClaw, the agents.list[].workspace config was completely ignored. Here's the investigation and a working workaround. Symptoms After installing OpenClaw 2026.3.13 on macOS Ventura (Mac Mini M1) and adding an agent with an explicit workspace path: agents : list : - id : my-agent workspace : /Users/openclaw/.openclaw/agents/my-agent/workspace Every gateway restart ignores the setting and auto-generates ~/.openclaw/workspace/ , pointing the session's cwd there. Default scaffold files (AGENTS.md, SOUL.md, TOOLS.md, etc.) get unpacked every time. The custom agent workspace is never used. Linux Works Fine The same version 2026.3.13 on Linux (Ubuntu 24.04) respects agents.list[].workspace with absolute paths — no issues. The default ~/.openclaw/workspace/ isn't even created. This is a macOS-specific bug . What I Tried (All Failed) Absolute path in agents.list[].workspace → ❌ agents.defaults.workspace fallback → ❌ Adding agentDir field → ❌ (doesn't

Continue reading on Dev.to DevOps

Opens in a new tab

Read Full Article
1 views

Related Articles