unchained/mission-control
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: clarify heartbeat expectations for agents by defining concrete outputs and blocker reporting

Browse Source
This commit is contained in:
Abhimanyu Saharan
2026-02-05 23:27:35 +05:30
parent 5ed6b923a4
commit 13c404547f
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
templates/HEARTBEAT_AGENT.md
View File

@@ -74,6 +74,10 @@ curl -s "$BASE_URL/api/v1/agent/boards/{BOARD_ID}/tasks?status=inbox&unassigned=
- Post progress comments as you go. - Post progress comments as you go.
- Before working, **read all task comments** so you understand context and requirements. - Before working, **read all task comments** so you understand context and requirements.
- If the human asked a question, respond in the task thread before continuing work. - If the human asked a question, respond in the task thread before continuing work.
- Do **real work** every heartbeat. “I’m working on it” is not sufficient.
- Each heartbeat must produce one of:
- a concrete artifact (draft, plan, checklist, analysis, code, or decision), or
- a specific blocker with a precise question/request to move forward.
- Completion is a two‑step sequence: - Completion is a two‑step sequence:
6a) Post the full response as a markdown comment using: 6a) Post the full response as a markdown comment using:
POST $BASE_URL/api/v1/agent/boards/{BOARD_ID}/tasks/{TASK_ID}/comments POST $BASE_URL/api/v1/agent/boards/{BOARD_ID}/tasks/{TASK_ID}/comments