diff --git a/.openclaw/memory/main.sqlite b/.openclaw/memory/main.sqlite
index b54d7df..d56f8eb 100644
Binary files a/.openclaw/memory/main.sqlite and b/.openclaw/memory/main.sqlite differ
diff --git a/.openclaw/tasks/runs.sqlite b/.openclaw/tasks/runs.sqlite
index 159e90a..99da0e5 100644
Binary files a/.openclaw/tasks/runs.sqlite and b/.openclaw/tasks/runs.sqlite differ
diff --git a/.openclaw/tasks/runs.sqlite-shm b/.openclaw/tasks/runs.sqlite-shm
index 412572b..e24bc01 100644
Binary files a/.openclaw/tasks/runs.sqlite-shm and b/.openclaw/tasks/runs.sqlite-shm differ
diff --git a/.openclaw/tasks/runs.sqlite-wal b/.openclaw/tasks/runs.sqlite-wal
index ab7d869..72873c6 100644
Binary files a/.openclaw/tasks/runs.sqlite-wal and b/.openclaw/tasks/runs.sqlite-wal differ
diff --git a/.openclaw/workspace/AGENTS.md b/.openclaw/workspace/AGENTS.md
index 0652ed5..4c758e8 100644
--- a/.openclaw/workspace/AGENTS.md
+++ b/.openclaw/workspace/AGENTS.md
@@ -115,7 +115,6 @@ On platforms that support reactions (Discord, Slack), use emoji reactions natura
 
 **Why it matters:**
 Reactions are lightweight social signals. Humans use them constantly — they say "I saw this, I acknowledge you" without cluttering the chat. You should too.
-
 **Don't overdo it:** One reaction per message max. Pick the one that fits best.
 
 ## Tools
@@ -179,7 +178,7 @@ No peer or leader review should begin until the worker has completed their self-
 Enforce this sequence in your task board by marking statuses appropriately (e.g., `needs-self-review` → `needs-peer-review` → `needs-leader-review` → `completed`).
 
 ClawTeam enables you to:
-- Spawn teams of specialized agents via `clawteam spawn`
+- Spawn teams of specialized agents via `clawteam spawn tmux openclaw --team`
 - Create tasks with dependencies using `clawteam task create`
 - Monitor progress via `clawteam board show/attach`
 - Coordinate via `clawteam inbox send/receive`
diff --git a/.openclaw/workspace/RULES.md b/.openclaw/workspace/RULES.md
index 6412ea2..ce1bc6f 100644
--- a/.openclaw/workspace/RULES.md
+++ b/.openclaw/workspace/RULES.md
@@ -61,7 +61,7 @@ Only use ClawTeam's parallel power when tasks meet "completely independent" crit
 
 ### 3. Subagent-Driven Mindset
 Treat each ClawTeam worker as a "temporarily amnesiac entity." They know nothing of your recent chat with user.
-- **Fresh Context:** When using `clawteam spawn`, you MUST provide: target file, error logs (if any), and specific goal.
+- **Fresh Context:** When using `clawteam spawn tmux openclaw --team`, you MUST provide: target file, error logs (if any), and specific goal.
 - **Bite-Sized Tasks:** Each worker should get work doable in 2-5 minutes. If task too large, have worker do Step 1 only, then report.
 
 ### 4. Two-Stage Code Review (CRITICAL)
diff --git a/.openclaw/workspace/skills/clawteam-multi-agent-coordination/SKILL.md b/.openclaw/workspace/skills/clawteam-multi-agent-coordination/SKILL.md
index 724bbd4..99f14c6 100644
--- a/.openclaw/workspace/skills/clawteam-multi-agent-coordination/SKILL.md
+++ b/.openclaw/workspace/skills/clawteam-multi-agent-coordination/SKILL.md
@@ -35,7 +35,7 @@ Requires Python 3.10+. For P2P transport support: `pip install clawteam[p2p]`.
 ## Prerequisites
 
 - `tmux` installed (default spawn backend)
-- A CLI coding agent such as `claude`, `codex`, `gemini`, `kimi`, `nanobot`, or `openclaw`
+- A CLI coding agent such as `openclaw`
 - A git repository for worktree isolation and context features
 - Default dependencies installed if you want the TUI wizard (`clawteam profile wizard`)