wangzhendong/openclaw-control-plane
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Sync agent state from PC at 2026-05-19 12:32:00

Browse Source
This commit is contained in:
wangzhendong
2026-05-19 12:32:00 +08:00
parent d8b2521bc2
commit 65af21485a
5 changed files with 92 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
docs/MULTI_AGENT_CURSOR_PLAYBOOK.md
View File

@@ -19,6 +19,30 @@ Recommended windows:
- VPS control-plane window: VPS executor/verifier roles.
- Dedicated terminals: PC and VPS sync scripts. Do not let normal chat agents own these long-running terminals.
## Multi-Window Role Confirmation
When several Cursor windows are open, every window should make its role visible before work starts:
- Put the active role at the top of the working context or first message, such as `Role: ORCHESTRATOR`, `Role: VPS_VERIFIER`, or `Role: PC_EXECUTOR`.
- Before sending an execution or authorization prompt, check the visible workspace path and the relevant `handoff/*.md` file.
- Prompts that authorize token use, `node run`, `approve`, service changes, Docker/Nginx changes, firewall changes, or other mutation must echo the intended role and workspace in the first sentence.
- If the target role and current window role do not match, do not reinterpret the prompt. Stop and ask the user to resend it to the correct window.
- Verifier windows must not accept ORCHESTRATOR or EXECUTOR work, even if the requested content looks reasonable.
- ORCHESTRATOR must adopt or correct any cross-role control-plane edits before executors act on them.
Example safe authorization phrasing:
```text
Target role: PC_EXECUTOR in D:\openclaw-control-plane.
Authorize only T9 foreground node run under docs/G2_RUNBOOK.md.
```
Unsafe phrasing:
```text
Go ahead with G2.
```
## Role Boundaries
- ORCHESTRATOR owns requirements, task split, dependency state, and acceptance gates.
@@ -43,6 +67,7 @@ Git is the durable source of truth. It is not a real-time message bus. Upgrade l
- Do not store secrets in files, evidence, commits, or chat.
- Do not enter mutation stages while sync health is blocked.
- Require rollback notes before persistent service, routing, firewall, Docker, or environment changes.
- Treat role mismatch as a safety blocker for execution or authorization prompts.
## User Experience Rule