{"version":"2.1.271","anchor":"control-request-handling-gains-a-generic-dispatch-branch-ahe","canonical_anchor":"control-request-handling-gains-a-generic-dispatch-branch-ahe","heading":"Control-request handling gains a generic dispatch branch ahead of the hardcoded subtype switch","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/control-request-handling-gains-a-generic-dispatch-branch-ahe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Control-request handling gains a generic dispatch branch ahead of the hardcoded subtype switch\n\nControl-request handling gains a generic dispatch step that runs before the existing hardcoded request-type checks\n\n**Unclear.** Which control-request types are actually routed through the new generic dispatch path is not specified.\n\n**What**\n\nThe loop that processes control requests (internal commands like interrupting a session, ending it, or changing its model or permission mode) now first checks whether a request matches a new generic dispatch path, optionally replying immediately through a callback, before falling back to the existing hardcoded checks for specific request types such as `interrupt`, `end_session`, `initialize`, `set_permission_mode`, `set_model`, and `set_cwd`.\n\n**Why**\n\nThis adds a general-purpose route for handling control requests ahead of the older per-type checks, likely making it easier to add new control-request types without extending the hardcoded chain, though the finding doesn't specify which requests currently take this new path.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}