AI Coding Agent Memory & Semantic Change Control

nool debug

Replay the exact steps an agent took, walk the causal chain back to the originating knot, or binary-search which change introduced a regression.

  • Replay a session step by step.
  • Binary-search a regression with nool debug bisect.
  • Check blast radius before touching shared code.
nool debug blame <path>

Why it matters

Git blame tells you who last touched a line. nool debug blame walks the causal chain back to the knot whose recorded intent explains the failure — across proposal, validation, and policy steps, not just the text diff.

Replay a session step by step

Step through what an agent (or a person) actually did, one operation at a time, instead of reconstructing it from scattered terminal output.

nool debug replay HEAD

Binary-search a regression

When you know something broke but not when, bisect walks the DAG to find the exact knot that introduced it — the same idea as git bisect, applied to semantic history.

nool debug bisect

Check impact before you touch shared code

Root-causing a failure and scoping a fix are different problems. Blast radius answers the second one — see the dedicated guide for how to read its output.

  • Root cause: nool debug blame / nool debug bisect
  • Scope of a planned change: nool debug blast-radius