You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
TeammatesArea: what it touches
New FeaturesKind: in v2.1.251,
What probably matters to youSection of the release
What
When a leader approves or denies a tool call on a teammate's behalf, the request now carries the tool name and a digest of the tool input, and the reply is classified as bound, unbound, a tool mismatch, or an input mismatch before it is applied. This stops an approval landing on a different tool call than the one it was given for.
Details
A mismatch in the resume/reply teammate flow is handled by asking again rather than acting on the stale verdict.
That same call site leaves the unbound case an empty function, while a second call site in tool execution sets a flag instead, so the two callers of the same poller behave differently on unbound replies.
What reaches the empty handler is not settled by the code itself.
Evidence
onUnboundVerdict() {}
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
