Agent offers now have a formal hook event definition answered with a single yes-or-no.
An agent-offer hook event is defined alongside the tool-call event, matched on agent and source, but nothing surfaces it.
What's wrong with this entry?
The agent offer hook has a formal event definition sitting alongside the existing tool call event, matched on the agent, its description and where it came from, and answered with a single offered boolean.
- This is the shape a hook author writes a matcher against, the same way tool call events are matched.
event: "agent.offer"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
SessionEnd hooks lose the
bypass_permissions_disabledreasonBoth mention hook
-
v2.1.236
Hooks and Ctrl-C go quiet once shutdown has started
Both mention hook
-
v2.1.236
Shutdown seals transcript writes and gives SessionEnd hooks more time
Both mention hook