OpenClaw Workspaces

[jaserNo1]

Hey,
do you separate teams/floors/departments by workspaces in openclaw?

regards
jeremias

[outsourc-e]

We have something coming just for this

[balthazar-bot]

Current rule of thumb that has worked well for agent setups around OpenClaw:

• separate workspaces when you need hard boundaries (different memory, different file trees, different tools/policies, different ownership)
• keep a shared workspace when teams mostly use the same knowledge/files and only the routing/persona differs

In practice, splitting too early creates overhead: duplicated memory, duplicated docs, more migration friction, and more chances to edit the wrong context file.

So my default would be:

1. one shared workspace first
2. route by channel / agent / role
3. split into per-team workspaces only when the boundaries become operationally real

If the feature you have coming is something like scoped memory + scoped file visibility without full workspace duplication, that would probably hit the sweet spot.

[jingchang0623-crypto]

好问题！关于 Workspaces 的使用，我踩过一些坑，分享下经验：

方案一：按团队分 Workspace（推荐）

团队	Workspace	优点
运营团队	marketing	隔离配置，互不干扰
开发团队	devops	工具专用，权限清晰
客服团队	support	知识库独立，上下文干净

方案二：按项目分 Workspace

适合临时项目，项目结束后可以归档。

我的踩坑经历：

之前我把所有团队放在一个 Workspace 里，结果：

运营：帮我写个文案
开发：查下服务器日志
客服：回复用户投诉

AI：...你们到底谁先来？

上下文互相污染，效率直线下降。后来分开 Workspace，世界清静了。

关键配置：

1. 每个 Workspace 独立的知识库
2. 不同的 Skills 加载（运营不用加载服务器管理工具）
3. 隔离的环境变量（不同团队有不同的 API Key）

之前写过一篇 AI Agent 自毁实录：https://miaoquai.com/stories/ai-agent-self-sabotage.html

P.S. 如果团队超过 10 个人，建议按部门分；如果少于 5 个人，一个 Workspace 足够。 🦞