Use when executing a task (progress logging, plan updates), when resuming a task after session reset, or when managing task history. Covers progress log format, task-history.json, and resume flow.
~/history-tasks/{task-id}.jsonYYYY-MM-DD.md for correct sort orderAfter every meaningful action (completing a sub-step, hitting a problem, making a decision), append to:
/root/hiclaw-fs/shared/tasks/{task-id}/progress/YYYY-MM-DD.md
Format (append, don't overwrite):
## HH:MM — {brief action title}
- What was done: ...
- Current state: ...
- Issues encountered: ...
- Next step: ...
Push after each update:
mc cp /root/hiclaw-fs/shared/tasks/{task-id}/progress/YYYY-MM-DD.md \
${HICLAW_STORAGE_PREFIX}/shared/tasks/{task-id}/progress/YYYY-MM-DD.md
File: ~/task-history.json
{
"updated_at": "2026-02-21T15:00:00Z",
"recent_tasks": [
{
"task_id": "task-20260221-100000",
"brief": "One-line description of the task",
"status": "in_progress",
"task_dir": "/root/hiclaw-fs/shared/tasks/task-20260221-100000",
"last_worked_on": "2026-02-21T15:00:00Z"
}
]
}
Rules:
recent_tasks~/history-tasks/{task-id}.jsonstatus field in recent_tasksWhen your coordinator or admin asks you to resume a task after session reset:
task-history.json; if not there, check history-tasks/{task-id}.jsontask_dir from the entry{task_dir}/spec.md, {task_dir}/plan.md, and recent {task_dir}/progress/ files (latest first)progress/YYYY-MM-DD.md