Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release
Unclear The finding does not say what triggers a reannouncement or how it affects the client side beyond the protocol addition itself.
What
A new control message kind, remote_tools_reannounce, was added to the remote-session protocol. When a replacement remote-tool worker gets a tool call naming a machine it doesn't recognize, it can send this request, identified by a worker epoch and a deadline, to ask the attached client (the one serving the session's tools) to re-announce itself. The client side handles this with rate limiting and epoch checks, and the message kind is included in the reject-list for otherwise-unhandled message kinds.
Why
This keeps a remote session's list of available tools and machines in sync even after a worker is replaced, avoiding stale or unrecognized machine references.
Read from
Names in the bundleremote_tools_reannounce
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what triggers a reannouncement or how it affects the client side beyond the protocol addition itself.
