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

9
knowledge/LESSONS_LEARNED.md
View File

@@ -12,3 +12,12 @@ Reusable lessons from this OpenClaw multi-agent Cursor workflow.
- COACH and ORCHESTRATOR should remain separate roles: ORCHESTRATOR manages tasks; COACH manages usability, method, and knowledge capture.
- Sync scripts are infrastructure and should not be owned by normal chat agents. They should remain in dedicated terminals for now and later become managed services after safety gates allow persistence.
- Session freeze is mandatory for long-running work. Handoff files and lessons are more reliable than chat memory.
## 2026-05-19
- Multi-window Cursor work needs visible role confirmation. A prompt intended for ORCHESTRATOR can land in a VPS_VERIFIER window and produce plausible but out-of-scope control-plane edits.
- Role mismatch should be treated as a safety blocker for execution or authorization. Pause tasks first, then let ORCHESTRATOR adopt or correct affected files.
- Authorization should name the target role, workspace, task, and exact allowed action. Short prompts like "go ahead" are unsafe when several role windows are open.
- Verifier roles should refuse ORCHESTRATOR/EXECUTOR work even when the requested edit is reasonable.
- Recovery should check for five facts before resuming: cross-role file edits, secret leakage, live PC/VPS commands, frozen website mutation, and sync health.
- Keep `docs/ROLE_MISDIRECTION_RECOVERY.md` and `.cursor/rules/role-confirmation.mdc` as reusable guardrails for future multi-agent sessions.