A fair question stopped us this week: why would anyone approve an edit from the notch without seeing the change? Until now the approval card named the file and not much else, which made a notch answer a leap of faith on anything bigger than a one-liner.
Version 2.2 closes that gap in two layers. The card itself now carries the compact truth of the change, and when the change is big, one hover opens a full review over the notch, wide enough to actually read the code you are approving.
The card carries the change
When an agent asks to edit a file, the card now shows what the edit does: change counts in the header, removed lines tinted red, added lines tinted green, line numbers in the gutter, and the first changed line first. Long lines pan sideways, longer diffs scroll, and a quiet hint tells you how much more there is.
Multi-line commands get the same treatment. A shell script that used to arrive as three wrapped lines and an ellipsis now reads as an actual block of code, so a permission request is never a mystery box no matter which agent sent it.
Hover for the whole diff
Seven tinted rows are enough to recognize a small edit, and not nearly enough to judge a forty-line refactor. So the diff block itself is now a doorway: rest your pointer on it, or click it, and a wider review sheet drops over the notch with the old code on the left and the new code on the right, scrolling in lockstep like the code review views you already know.
The sheet is sized for real code. Each side fits full lines that the compact card could only hint at, blank lines and indentation survive, and the changed middle of the block stays tinted while shared context reads neutral. Allow and Deny sit pinned at the bottom of the sheet, so the answer lives in the same place as the evidence. Move your pointer away and it folds back into the notch, or answer right there and it collapses with the decision made.
Approvals you can trust
Under the surface, this release makes the decision channel itself steadier. When an agent fires several permission requests in the same instant, each card now resolves to exactly the request it belongs to, so answering one can never quietly consume its sibling.
Cards also clean up after themselves. A request that gets answered in the terminal, times out, or belongs to a finished turn withdraws its card and its review sheet immediately, so the notch never offers you a decision that no longer exists.
Product decision
The principle behind 2.2
An approval is only as good as the context behind it, and asking for trust without showing the change is not a handoff, it is a gamble. The notch card stays small and calm because most decisions are small, and the full picture stays one hover away because some decisions are not.
That layering is the point. The surface you glance at and the surface you scrutinize are the same surface, just closer.