Which version of a change do HAR’s test records actually cover?

HAR can tie AI-written changes to repository checks that were actually run. Before adopting it, try a routine code review: if an earlier version passed and another edit followed, can the reviewer tell at a glance?

Source: github.com
November 18, 2026
2 min

If your frontend team often gets AI-written code marked “all tests passed” without knowing whether the tests ran before or after the last edit, try HAR on one small change. The point is not another green status line. It is being able to match the passing result to the version under review.

The os-factory/har project documentation describes two distinct capabilities: giving coding agents separate Git worktrees so their changes do not have to share one working directory, and validating a worktree with checks configured in the repository while recording test logs, artifacts, or a validated tree hash. That hash identifies the code tree the checks ran against. It cannot tell you whether the repository's tests missed anything. Separate Git worktrees do not, by themselves, isolate secrets, network access, or process permissions.

Consider a fictional settings-page change as an acceptance exercise. Version A changes only a label and passes the checks. Version B then adjusts the narrow-screen layout. The reviewer first checks whether the evidence is for A or B, then checks whether the existing tests cover that layout. Even if B passes the automated checks, breakpoints the tests missed still need to be verified manually. If the records cannot distinguish the versions, or nobody knows which checks ran, another layer of tooling will not resolve the ambiguity at handoff.

If your existing pull requests already connect commits, required CI check records, and manual acceptance clearly, stick with that process for now. HAR is more worth trying when code is handed off outside a PR or parallel changes make the evidence hard to trace. A worktree keeps changes from getting in one another's way, and a record of checks helps identify the corresponding version. Neither decides for the team whether to merge the change.

Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.

Original source:github.com