Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.280 ·

Control bridge gains a generic 'shared control request' handler

Remote Control's request handling now goes through a general answerSharedControlRequest step before falling back to per-type handling

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaRemote Controlwhat it touches
KindInternal Changesin v2.1.280,
Group of 2 Under the hood

Remote Control's request handling now goes through a general answerSharedControlRequest step before falling back to per-type handling

What

Remote Control's connection options previously had a specific onGetUsage callback just for usage queries. This has been replaced with a more general answerSharedControlRequest callback that can handle more kinds of requests.

  • The remote-bridge connection options now expose answerSharedControlRequest in place of the older onGetUsage callback.
  • Before the control bridge dispatches a control_request to its specific handler (for things like initialize or set_model), it first calls answerSharedControlRequest on the request. If that returns a promise, the request is handled asynchronously; if it returns a result right away, a control_response is sent immediately without running the normal per-type handling.

Why

This generalizes what used to be a single-purpose usage-query callback into a reusable path for answering various control requests, making it easier to add new request types without special-casing each one in the dispatch logic.

See this entry in the whole of v2.1.280 →

Feedback