Sync agent state from PC at 2026-05-15 16:48:30
This commit is contained in:
14
.cursor/rules/coach-agent.mdc
Normal file
14
.cursor/rules/coach-agent.mdc
Normal file
@@ -0,0 +1,14 @@
|
|||||||
|
---
|
||||||
|
description: Coach agent rules for guiding the OpenClaw multi-agent workflow
|
||||||
|
alwaysApply: true
|
||||||
|
---
|
||||||
|
|
||||||
|
# COACH Role
|
||||||
|
|
||||||
|
- COACH is a guidance role, normally carried by the user's main chat session. Do not open a separate COACH agent unless the user explicitly asks.
|
||||||
|
- COACH does not replace ORCHESTRATOR. ORCHESTRATOR owns task decomposition, dependency state, and acceptance gates.
|
||||||
|
- COACH helps the user understand the current phase, reduce manual coordination, and keep the workflow usable.
|
||||||
|
- COACH should point the user to `USER_STATUS.md` as the primary human-facing state page, not internal task numbers.
|
||||||
|
- When the workflow feels confusing, COACH should ask ORCHESTRATOR to summarize a single next action instead of adding more parallel tasks.
|
||||||
|
- COACH watches for missing playbook updates, session-freeze needs, sync-health confusion, and lessons worth recording.
|
||||||
|
- COACH must not perform PC/VPS configuration changes or bypass safety gates.
|
||||||
13
.cursor/rules/session-freeze.mdc
Normal file
13
.cursor/rules/session-freeze.mdc
Normal file
@@ -0,0 +1,13 @@
|
|||||||
|
---
|
||||||
|
description: Session freeze and knowledge capture rules for long-running agent work
|
||||||
|
alwaysApply: true
|
||||||
|
---
|
||||||
|
|
||||||
|
# Session Freeze Protocol
|
||||||
|
|
||||||
|
- Before a long-running chat ends, changes focus, or approaches context exhaustion, freeze state instead of relying on chat memory.
|
||||||
|
- A freeze must update `USER_STATUS.md`, the active role handoff under `handoff/`, and relevant task files.
|
||||||
|
- A freeze should record reusable lessons in `knowledge/LESSONS_LEARNED.md` when the session produced process insight.
|
||||||
|
- For phase boundaries or notable incidents, create an archive note under `archive/` using `YYYYMMDD-topic.md`.
|
||||||
|
- The final message before handoff should include a short resume prompt for the next session.
|
||||||
|
- Do not start new execution work if the current state is not frozen and the context is near exhaustion.
|
||||||
@@ -1,9 +1,9 @@
|
|||||||
{
|
{
|
||||||
"host": "pc",
|
"host": "pc",
|
||||||
"time": "2026-05-15T16:47:28+08:00",
|
"time": "2026-05-15T16:48:30+08:00",
|
||||||
"branch": "main",
|
"branch": "main",
|
||||||
"head": "53617e0",
|
"head": "9c80dec",
|
||||||
"status": "clean",
|
"status": "dirty",
|
||||||
"intervalSeconds": 30,
|
"intervalSeconds": 30,
|
||||||
"heartbeatEverySeconds": 60
|
"heartbeatEverySeconds": 60
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user