Skip to main content

Better Harness

Harness Inspector

Trace product intent through agent activity, sessions, files, and commits—while keeping evidence strength and limitations visible.

Run in your repositorynpx @qoder-ai/better-harness inspector
  • Interactive sample
  • Read-only
  • English sample data
Open full screen

Interactive Harness Inspector sample

Loading the interactive sample…

This deterministic sample uses fictional English data. It does not read your workspace, Git history, or coding-agent sessions.

What it shows

Follow delivery without losing the evidence boundary

Inspector brings product structure, agent activity, and Git outcomes into one read-only workspace. It keeps strong links separate from useful—but limited—context.

01

Intent to delivery

Navigate the capability tree from capability and Story intent to the sessions, files, and commits associated with it.

02

A session in context

Review retained prompts, normalized tool activity, file paths, commit events, and the read-only session replay.

03

Explainable evidence

Synchronized selections and the Evidence Drawer show why a relationship exists, its confidence, and what it does not prove.

How to use it

Start broad, then follow the evidence

  1. Choose a scope

    Use Capability for product intent or Date for a time-based view of sessions and commits.

  2. Read the three lanes

    Compare user prompts, checkpoint activity, and commits or files without leaving the selected Story or date.

  3. Inspect the relationship

    Select a prompt, action, commit, or path. Related items stay highlighted while the Evidence Drawer explains the link and its limits.

  4. Open Session View or Replay

    Drill into retained turns and normalized tool calls, or replay the observed sequence. Replay never reruns tools or resumes the coding-agent session.

Reading the labels

Correlation is visible; authorship is not assumed

Explicit / direct
A retained reference directly connects the Story, session, or commit.
Observed same-path
The session and commit share exact repository paths. This supports correlation, not proof of authorship.
Candidate
Structure or timing suggests a useful association that still needs human review.
Contextual
Nearby history helps explain the delivery, but no direct relationship is claimed.
Read the architecture, evidence model, and boundaries