菜单
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.
Use before direct filesync calls, reading non-task shared files, pushing mid-task progress, or troubleshooting missing shared files. Do not use for normal task acceptance or submission; taskflow ack_task and submit_task handle lifecycle sync internally.
Use before filesync calls for project directories, global-shared inputs, non-task shared files, listing shared paths, or troubleshooting missing files. Do not use for task-level sync; taskflow delegate_task and check_task handle task directory sync internally.
Sync files with centralized storage. Use when your coordinator or another Worker notifies you of file updates (config changes, task files, shared data, collaboration artifacts).
Discover and install agent skills from the open ecosystem. Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task.
Discover and call MCP Server tools via the mcporter CLI. Use when your coordinator notifies you about new MCP tools, or when you need to call external APIs. Includes workflow for generating skill documentation for new MCP servers.
Use when you are invited to a Project Room or assigned a task within a multi-worker project. Covers project plan reading, task coordination with other Workers, and git author config.
| name | task-progress |
| description | 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. |
/home/openhuman/.openhuman/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:
/home/openhuman/.openhuman/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 the task directory after each update:
mc mirror /home/openhuman/.openhuman/shared/tasks/{task-id}/ ${HICLAW_STORAGE_PREFIX}/shared/tasks/{task-id}/ --overwrite --exclude "spec.md" --exclude "base/"
File: /home/openhuman/.openhuman/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": "/home/openhuman/.openhuman/shared/tasks/task-20260221-100000",
"last_worked_on": "2026-02-21T15:00:00Z"
}
]
}
Rules:
recent_tasks/home/openhuman/.openhuman/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/home/openhuman/.openhuman/shared/tasks/{task-id}/ (auto-synced){task_dir}/spec.md, {task_dir}/plan.md, and recent {task_dir}/progress/ files (latest first)progress/YYYY-MM-DD.md