An agent tree describes who is working now. A project’s history must also explain what remains afterward. Released on September 26, 2026, Genesis 0.13.4 develops the commit-history view introduced in 0.13.2 and the durable task references added in 0.13.3. Together they connect temporary activity to inspectable software versions.
From live agents to durable task references
The task-scoped history API resolves durable references and the task’s base commit. This lets the temporal view retain commits from recycled agents. The earlier API queries commit ranges and references across repositories; the task layer supplies the context needed to keep following a particular development effort. v0.13.2 · v0.13.3
When an agent delegates a module and then finishes, its contribution may still need review. Git history gives the change a durable identity; the task view helps locate it within the larger effort. The end of an agent episode need not erase the relationship between a task and its resulting code.
Showing how contributions relate
Version 0.13.4 organizes commits into agent lanes, keeps subtrees together and shows delegation and merge-back edges. Unowned commits have a neutral lane. Selection, hover synchronization and keyboard access support inspection, while partial repository-fetch failures no longer blank the entire graph. v0.13.4
The view marks truncation at its 100-commit limit. When investigating an older change, use the task’s base and tip references to inspect the relevant Git range.
Follow a contribution through integration
Start with a task, locate its base commit and follow an agent lane through delegation and merge-back. Open the corresponding diffs and test results when deciding what to retain. For changes spanning several codebases, multi-repository review provides the next integration step.