harness-multitool

0010 — Hook runs are visible

Decision

Every run of a hook is an event on the bus, and frontends show it: on which loop event the hooks ran (session start, compaction, before or after a tool call, prompt submit, stop, ...), which scripts ran, and what each did — ok, added context (with the lines it added), blocked the event (with the reason), failed (exit code, stderr tail), timed out, still running — with its duration. The terminal UI draws one HOOK card per event (docs/tui.md).

Why

Hooks change what the agent sees and may veto what it does. Invisible, they make the agent's behaviour hard to explain: a context line that came from a hook, a tool call that silently did not happen. The owner asked to see, for example, which scripts fire at session start and at compaction.

Rejected

This page's source