Skip to content
WHY
v0.2.0 · early · Linux only

Read the diff. Then ask why.

WHY is a local-first desktop app for reviewing code your coding agents wrote. It shows the live diff of every repo and worktree you add, and what Claude Code and Codex did, turn by turn. Read-only, early, Linux only.

ChangelogSecurityMIT OR Apache-2.0

The WHY window on demo data: repositories and worktrees on the left with each changed file marked by the agent turns that explain it, a split diff of mod.rs in the middle, and on the right a Codex session timeline whose items are labelled Observed, Declared or Unknown.
WHY on demo data: a worktree's changed files with the agent turns that explain them, the diff, and a Codex session timeline. Fixture data, not a real repository.

Because git diff tells you what, not why.

Coding agents write code fast. A human still has to understand and approve it, so review is now the bottleneck.

git diff shows what changed. It does not show the task the agent was given, why it made a change, whether a block was necessary, or whether the agent drifted from scope. Today people paste diffs back into the agent's chat and ask “why did you do that?”.

WHY aims to answer three questions in one place: what changed, how it changed, and why. An agent's own explanation can be an after-the-fact rationalisation, so WHY labels every explanation by how well it is backed. It never replaces reading the code.

Today, in v0.2.0

What WHY does

Every explanation says how it is backed

WHY labels each piece of evidence, and never presents a guess as fact. In v0.2 the labels you will see are Observed, Declared and Unknown.

Observed
The harness recorded it: a tool call, an edit, an exit code.
Declared
The agent said it. Shown as its own claim, never as proof.
Inferred
Reconstructed from the available records. Part of the model; v0.2 does not produce it yet.
Unknown
There is not enough evidence. WHY says so instead of guessing.

Unknown beats a confident guess. A tool call that started and never reported a result is shown as unknown, never as success. A change that no captured agent edit explains is shown as exactly that, because WHY cannot tell a human from a shell command or a lost event.

Safe to run next to your agents

WHY runs git against repositories that agents are using right now, so it is built never to disturb them.

It is early software and has had no external security review. The security policy lists its known limits and how to report a problem.

What it is not, yet

These are plans, not shipped features. Everything from v0.3 on is a plan, not a promise, and nothing here has a date.

  1. v0.3 · planned, not shipped

    Line provenance

    Attribute individual lines to the edits that produced them.

  2. v0.4 · planned, not shipped

    Attention

    Signals such as unknown origin, churn and untested code, and a review queue ordered by them.

  3. v0.5 · planned, not shipped

    Close the loop

    Anchored comments, and feedback sent back to the agent that wrote the code.

Limits today

Get WHY

WHY v0.2.0 ships as a Linux AppImage and a .deb. Download one from the latest release.

Requirements

  • Git 2.45.1 or newer on your PATH. Check with git --version.
  • webkit2gtk 4.1 and GTK 3. The .deb installs them for you; the AppImage bundles its own copy.

Check the download

Builds are unsigned. Download SHA256SUMS from the same release and run this next to the files:

sha256sum --check --ignore-missing SHA256SUMS

AppImage, any distribution

chmod +x WHY_0.2.0_amd64.AppImage
./WHY_0.2.0_amd64.AppImage

If it fails with a FUSE error, install libfuse2 (libfuse2t64 on Ubuntu 24.04).

Debian, Ubuntu and derivatives

sudo apt install ./WHY_0.2.0_amd64.deb

Then start WHY from your application menu, or run why.

Uninstall the agent hooks from the Agent hooks dialog before you remove the app, so your agent config no longer points at the hook.