Docs

Decision diff

Find two repos in the same account that decided the same topic opposite ways. It reads the decision entries in each tracked repo's brain, pairs the ones with high word overlap, and flags the pairs where one says yes and the other says no. No LLM call.

Where to find it

  • Localhost: /decision-diff.html?repo=<id>
  • API: GET /api/brain/decision-diff?repo=<id>&min=<0..1>
  • Keyboard: ⌘ K then decision diff
  • Navigation: Attribution in the sidebar, then Decision diff under All tools, in the Pull requests, blame and graphs group

What it does for you

One row per opposing pair.Each row shows both decisions side by side (repo, title, date), a similarity score, and a polarity-flip marker. It surfaces the case where two of your repos looked at the same question and landed on the opposite answer.
No model, so no guessing.Pairs are found by word overlap (Jaccard) and a negation check, both computed locally. The result is repeatable and free to run, and nothing about your decisions leaves the machine.
Set how close counts as the same topic.The Min similarity control (default 0.3) sets the overlap floor. Raise it for tighter, fewer pairs; lower it to cast wider. Refresh re-runs against the current setting.

Account rollup

Decision diff compares across every repo assigned to the account, reading each repo's decisions file at request time rather than from a stored rollup. The account rollup shown here is a separate projection. The stamp says when it was last projected, and Refresh account rollup re-projects it and re-runs the diff. An account with no repos assigned says so, rather than reading as stale.

When it is empty

The tab needs at least two tracked repos with overlapping decision entries in their brains. Until then, or when no pair clears the similarity floor, it says so plainly instead of inventing a diff.

Read more

Last updated