Record completed steps, decisions, issues, and next actions in dated progress logs. Maintain recent task history and sync updates to shared storage so an agent can recover context and resume work after a session reset.
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.
Review the instructions the agent will receive before you install.
~/.hermes/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:
~/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 ~/shared/tasks/{task-id}/ ${AGENTTEAMS_STORAGE_PREFIX}/shared/tasks/{task-id}/ --overwrite --exclude "spec.md" --exclude "base/"
File: ~/.hermes/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": "~/shared/tasks/task-20260221-100000",
"last_worked_on": "2026-02-21T15:00:00Z"
}
]
}
Rules:
recent_tasks~/.hermes/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~/shared/tasks/{task-id}/ (auto-synced). If you need the very latest, run hermes-sync{task_dir}/spec.md, {task_dir}/plan.md, and recent {task_dir}/progress/ files (latest first)progress/YYYY-MM-DD.mdNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Find worker agents in Nacos that match a task, recommend candidates, and import the administrator's chosen worker. It also supports importing a specified nacos package URI, with worker name confirmation and direct reporting of installation failures.
Prepare an existing OpenClaw setup for import as an AgentTeams managed Worker. Analyze tool dependencies, adapt role instructions and scheduled jobs, and build a ZIP package containing the configuration and custom image requirements.
Manage communication channels by identifying senders, maintaining trusted contacts, and setting the administrator's primary notification destination. It also covers first contact on a new channel and contacting the administrator across channels, with rules for handling unknown senders.
Prepare coding tasks for delegation to an authorized agent’s AI command-line tool. Set up and synchronize the workspace, write precise change requests, then review returned changes and run relevant checks before reporting completion.
Run AI coding command-line tools on behalf of worker agents using their prepared prompts and workspaces. Detect available tools, configure delegation, return results, and apply supported execution controls such as time budgets and permission settings.
Guide agent replies in Matrix chat rooms, including when to mention a coordinator, report completion, raise blockers, or answer questions. The rules limit repetitive acknowledgments and stop exchanges that add no new task, question, or decision.