- Who it helps
- Developers reviewing changes made by coding agents.
- Availability
- The public MIT-licensed project offers a command-line tool and an offline HTML view. The README and October 24 maker launch were checked; installation was not tested.
What it checks
A JSON change report describes nodes, flows and references. Validation can check file lines, commit references and diff coverage, helping a reviewer locate the claimed evidence.
Claims still need review
An agent’s statement that tests passed remains an assertion. The tool can display contradictions and still render a review page. A navigable map therefore needs human inspection and separate test evidence.
What you can do
- Inspect the example report and validation rules before using a generated map to review a real change. Open reference ↗
Where the evidence stops
The user-guide fetch failed. No report was generated here, and the maker launch had no independent comments at this check.
Sources read. Public evidence checked October 24, 2026 UTC. No third-party software, model inference or complete product workflow was executed.
Sources & further reading
GitHub · implementation
Task-view implementation ↗
The README defines which file and diff references are checked and which agent claims remain assertions.
gtindo · page checked 2026-10-24
More sources reviewed (1)
Hacker News · discussion
Task-view original launch ↗
The maker’s launch links the same repository. No comments were present at this check; independent review is still missing.
Hacker News · page checked 2026-10-24 · Published 2026-10-24
Coverage note: Primary material was inspected. Independent execution and matching original YouTube, X and Reddit discussion remain incomplete; unavailable engagement counts are omitted.
The record over time (1)
Dated source checks and published explanations. An observation date can differ from the original release date.
- · Added to Current
Task-view turns a coding agent’s account of a change into an HTML review map with links back to code and diffs.