Dashboard
The dashboard brings your project’s progress and records together on one page.
Open .helmit/dashboard.html in a browser. The file stays in the project, works
without a server, and sends no data over the network.
What to follow
Section titled “What to follow”| On the dashboard | What it means |
|---|---|
| Project status | Shows whether work is in progress, recent session activity was recorded without an active task, a decision is waiting for you, work may have been interrupted, or no activity is confirmed. |
| Phases, tasks, and requirements | Show what is planned, completed, and proven in the project records. |
| Tests | Show recorded gate runs, their results, and duration. No recorded history does not mean no tests were run. |
| Tokens | Show recorded usage, including new input, output, cache read, and cache creation. There are views by model, phase, change, and unassigned work. |
| Time and timeline | Show recorded task and session intervals. Parallel tasks can overlap, so a day’s sum may exceed 24 hours. |
| Repository map | Appears when data for this optional capability exists. |
The header also shows open CHG changes and active Inbox items, when present. To see how a change differs from a phase delivery, read Inbox and changes.
How to read project status
Section titled “How to read project status”Work in progress requires matching signals from an open task, the project lock, and recent executor activity. An open conversation alone does not mean a task is running. Waiting for your decision means a pause was recorded; work may have been interrupted calls for the agent to reconcile state before continuing. Recent activity recorded is weaker evidence: the host observed the session, but HelmIt does not invent a task or phase for it. The time since the last activity and the expiration of temporary signals update on the page itself.
Status describes the available records; it is neither a command nor permission to advance the project. If it looks inconsistent, ask the agent to check the task state and the records behind the dashboard.
When the numbers change
Section titled “When the numbers change”HelmIt regenerates the HTML when its operations record relevant changes, such as a completed task, a change, a verification, or a ship. At session start, it also repairs a missing or stale dashboard. While the tab is visible, it checks the local file every three seconds, preserving the theme, scroll position, and open tables. You do not need to refresh manually during the normal workflow.
Reloading does not collect new data by itself: a change made outside HelmIt’s workflow may require the agent to regenerate the dashboard. If the file is missing, ask: “Open or update this project’s HelmIt dashboard.” The dashboard is a generated view; you do not need to edit it.
What the data does not claim
Section titled “What the data does not claim”The dashboard summarizes existing records without estimating gaps. The token total includes all four types in the legend, including cache. A capture is an increment of usage saved to the record; it is not necessarily one model call. When the record cannot identify a model, phase, or change, the usage remains in the total but has no such attribution. The token block shows how much of each breakdown is covered and flags known periods of undercounting.
Likewise, tests and time show recorded events only. The dashboard does not replace the project files as detailed evidence, run tests, or complete tasks or phases. If an update fails, valid work continues and the last available version is marked stale.
The data comes chiefly from .helmit/ROADMAP.md, each phase’s CHART.md,
.helmit/REQUIREMENTS.md, and the run.jsonl and metrics.jsonl records.
See Project artifacts for each file’s role.