The per-agent workspace path ownership map for all 50 live workspace-* directories under ~/.openclaw/. Read this hub before creating any file, script, or service — it tells you which agent owns each path and prevents cross-agent file conflicts. The canonical doc WORKSPACE-REGISTRY is severely stale (last updated 2026-03-08 — 56 days behind live state as of 2026-05-03) and documents only 1 named workspace (workspace-betterbets) while 50 exist on disk. This hub supersedes it for navigation and cross-link purposes.
/home/opsadmin/.openclaw/workspace/WORKSPACE-REGISTRY.md was last updated 2026-03-08 — 56 days behind live state as of 2026-05-03. Critical gaps:
Only workspace-betterbets has a named section in the registry. All 49 other workspace-* dirs are entirely undocumented.
50 live workspace dirs exist on disk. The registry implicitly documents path ownership via the main workspace/ table, but none of the per-agent workspace-* dirs are enumerated.
11 workspace dirs correspond to retired or inactive agents (workspace-betteracq, workspace-betteracq-site, workspace-dealcmd, workspace-debugger, workspace-horseracing-archived, workspace-stefania, workspace-h2-calls, workspace-h3-calls, workspace-investorlift-angel, workspace-investorlift-h2, workspace-investorlift-h3) — status unknown from registry.
5 workspace dirs have no matching agent in the agent registry (workspace-airtable-connector, workspace-betteracq-site, workspace-horseracing-archived, workspace-hubspot-connector, workspace-openphone-connector, workspace-reri-hq, workspace-marketing-intel, workspace-salesmessage-connector) — orphan status, Henry action required.
Action required per G-BLOCKER-SURFACING: update WORKSPACE-REGISTRY.md to enumerate all 50 dirs. Until then, use this hub + live ls -d ~/.openclaw/workspace-*/ as source of truth.
Failure mode: working in wrong workspace path causes cross-agent conflicts, orphaned scripts, services that restart each other’s processes, and duplicated implementations. Classic past failure: running workspace-betteracq/ scripts when acquisitions has superseded that domain.
Success criteria: every file is created inside the owning agent’s registered workspace path; workspace-shared/ only for code confirmed cross-agent
Related cluster — System catalog
This hub is a member of the system catalog cluster anchored at service-registry. Other cluster members: