#Multple projects
1 messages · Page 1 of 1 (latest)
You usually do not need separate OpenClaw instances (or separate Docker containers) per project.
Option A (simplest): one Gateway, one agent, multiple Discord threads/channels
On Discord, each channel/thread already gets its own session, so you can keep project conversations separated just by using separate threads/channels.
Downside: it’s still the same agent + same workspace, so file ops will default into the same workspace unless you’re disciplined about folders.
Option B (recommended for real separation): one Gateway, multiple agents (one per project)
Use Multi-Agent Routing: each agent has its own workspace + sessions + auth profiles (so “Project A” can’t bleed into “Project B” unless you want it to).
Typical flow:
openclaw agents add project-a
openclaw agents add project-b
openclaw agents list --bindings
Then add bindings so e.g. your #project-a Discord channel routes to project-a agent, etc.