{"version":"2.1.280","anchor":"generic-shared-control-request-answering-path-added-to-the","canonical_anchor":"remote-controls-usage-fetch-callback-generalized-into-a-sha","heading":"Control bridge gains a generic 'shared control request' handler","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/generic-shared-control-request-answering-path-added-to-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Control bridge gains a generic 'shared control request' handler\n\nRemote Control's request handling now goes through a general answerSharedControlRequest step before falling back to per-type handling\n\n**What**\n\nRemote 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.\n\n- The remote-bridge connection options now expose `answerSharedControlRequest` in place of the older `onGetUsage` callback.\n\n- 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.\n\n**Why**\n\nThis 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.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}