Building a Multi-Agent System with a Single OpenClaw Workspace
In OpenClaw, the standard way to build a multi-agent workflow is to create a completely new workspace for every new agent. If you want a social media agent, you create a social media workspace. If ...

Source: DEV Community
In OpenClaw, the standard way to build a multi-agent workflow is to create a completely new workspace for every new agent. If you want a social media agent, you create a social media workspace. If you want an engineering agent, you create an engineering workspace. This multi-workspace architecture keeps the agents perfectly isolated. But if you are a solo operator running multiple projects, it introduces a massive pain point: You are constantly switching environments, and your agents can't easily share a ground truth. For months, I tried to bypass this by running all my projects through a single OpenClaw workspace and bloating my global system prompt (AGENTS.md) with rules for every startup I was running. The result? A massive "Context Bloat" wall. My agent's startup context hit 27,000 tokens. The agent spent 20 seconds just "reading its own brain" before it could answer a simple prompt. Engineering logic was bleeding into my social media drafts. I wanted the project isolation of a mul