refactor: rename to openclaw

This commit is contained in:
Peter Steinberger
2026-01-30 03:15:10 +01:00
parent 4583f88626
commit 9a7160786a
2357 changed files with 16688 additions and 16788 deletions
+5 -5
View File
@@ -6,7 +6,7 @@ read_when:
# Channels & routing
Moltbot routes replies **back to the channel where a message came from**. The
OpenClaw routes replies **back to the channel where a message came from**. The
model does not choose a channel; routing is deterministic and controlled by the
host configuration.
@@ -53,7 +53,7 @@ The matched agent determines which workspace and session store are used.
## Broadcast groups (run multiple agents)
Broadcast groups let you run **multiple agents** for the same peer **when Moltbot would normally reply** (for example: in WhatsApp groups, after mention/activation gating).
Broadcast groups let you run **multiple agents** for the same peer **when OpenClaw would normally reply** (for example: in WhatsApp groups, after mention/activation gating).
Config:
@@ -80,7 +80,7 @@ Example:
{
agents: {
list: [
{ id: "support", name: "Support", workspace: "~/clawd-support" }
{ id: "support", name: "Support", workspace: "~/.openclaw/workspace-support" }
]
},
bindings: [
@@ -92,9 +92,9 @@ Example:
## Session storage
Session stores live under the state directory (default `~/.clawdbot`):
Session stores live under the state directory (default `~/.openclaw`):
- `~/.clawdbot/agents/<agentId>/sessions/sessions.json`
- `~/.openclaw/agents/<agentId>/sessions/sessions.json`
- JSONL transcripts live alongside the store
You can override the store path via `session.store` and `{agentId}` templating.