task-progress

What problem does it solve?

Task progress can get lost or become inconsistent after interruptions, making it hard to resume work, audit decisions, or understand what changed over time.

Core Features & Use Cases

• Progress logging for meaningful actions: Append human-readable progress entries after each decision, sub-step completion, or issue to a date-stamped file under the task directory.
• LRU task history for fast recovery: Maintain a top-10 most recently updated task-history.json, spilling older tasks to per-task history files to keep recovery lightweight.
• Deterministic resume flow after session reset: Load the latest task state by reading history first, then pulling spec.md, plan.md, and the most recent progress entries to continue from the right point.

Use case example: An autonomous coordinator assigns a long-running task, the session resets midway, and you need to resume with full context by reconstructing the plan and decisions from the saved progress logs.

Quick Start

Ask the agent to record a progress update for task-id task-20260221-100000 by appending today’s date-stamped entry to the task’s progress log and updating ~/.hermes/task-history.json accordingly.