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

feat(agents): Update task comment requirements and add in_progress_at tracking

Browse Source
This commit is contained in:
Abhimanyu Saharan
2026-02-04 19:08:14 +05:30
parent 554ecc4c85
commit 3a2bc5135e
7 changed files with 142 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
templates/AGENTS.md
View File

@@ -30,5 +30,12 @@ Write things down. Do not rely on short-term context.
- HEARTBEAT.md defines what to do on each heartbeat.
## Task updates
- Log all task progress and results via the task comments endpoint.
- Do not post task updates in chat/web channels.
- All task updates MUST be posted to the task comments endpoint.
- Do not post task updates in chat/web channels under any circumstance.
- You may include comments directly in task PATCH requests using the `comment` field.
- Required comment fields (markdown):
- `status`: inbox | in_progress | review | done
- `summary`: one line
- `details`: 1–3 bullets
- `next`: next step or handoff request
- Every status change must include a comment within 30 seconds (see HEARTBEAT.md).

3
templates/BOOT.md
View File

@@ -4,6 +4,7 @@ On startup:
1) Verify API reachability (GET {{ base_url }}/api/v1/gateway/status).
- A 401 Unauthorized response is acceptable here for agents (auth-protected endpoint).
2) Connect to Mission Control once by sending a heartbeat check-in.
2a) Use task comments for updates; do not send task updates to chat/web.
2a) Use task comments for all updates; do not send task updates to chat/web.
2b) Follow the required comment format in AGENTS.md / HEARTBEAT.md.
3) If you send a boot message, end with NO_REPLY.
4) If BOOTSTRAP.md exists in this workspace, the agent should run it once and delete it.

29
templates/HEARTBEAT.md
View File

@@ -21,6 +21,15 @@ curl -s -X POST "$BASE_URL/api/v1/agents/heartbeat" \
-d '{"name": "'$AGENT_NAME'", "board_id": "'$BOARD_ID'", "status": "online"}'
```
## Commenting rules (mandatory)
- Every task state change MUST be followed by a task comment within 30 seconds.
- Never post task updates to chat/web channels. Task comments are the only update channel.
- Minimum comment format:
- `status`: inbox | in_progress | review | done
- `summary`: one-line progress update
- `details`: 1–3 bullets of what changed / what you did
- `next`: next step or handoff request
2) List boards:
```bash
curl -s "$BASE_URL/api/v1/boards" \
@@ -40,25 +49,29 @@ curl -s "$BASE_URL/api/v1/boards/{BOARD_ID}/tasks" \
curl -s -X PATCH "$BASE_URL/api/v1/boards/{BOARD_ID}/tasks/{TASK_ID}" \
-H "X-Agent-Token: $AUTH_TOKEN" \
-H "Content-Type: application/json" \
-d '{"status": "in_progress"}'
-d '{"status": "in_progress", "comment": "[status=in_progress] Claimed by '$AGENT_NAME'.\\nsummary: Starting work.\\ndetails: - Triage task and plan approach.\\nnext: Begin execution."}'
```
5) Work the task:
- Update status as you progress.
- Post a brief work log to the task comments endpoint (do not use chat).
- When complete, move to "review":
- When complete, use the following mandatory steps:
5a) Post the completion comment (required, markdown). Include:
- status, summary, details (bullets), next, and the full response text.
Use the task comments endpoint for this step.
5b) Move the task to "review":
```bash
curl -s -X PATCH "$BASE_URL/api/v1/boards/{BOARD_ID}/tasks/{TASK_ID}" \
-H "X-Agent-Token: $AUTH_TOKEN" \
-H "Content-Type: application/json" \
-d '{"status": "review"}'
```
```bash
curl -s -X POST "$BASE_URL/api/v1/boards/{BOARD_ID}/tasks/{TASK_ID}/comments" \
-H "X-Agent-Token: $AUTH_TOKEN" \
-H "Content-Type: application/json" \
-d '{"message": "Summary of work, result, and next steps."}'
```
## Definition of Done
- A task is not complete until the draft/response is posted as a task comment.
- Comments must be markdown and include: summary, details (bullets), next.
## Status flow
```