{"version":"2.1.271","anchor":"sdk-control-request-handlers-for-statususagemodel-queries","canonical_anchor":"sdk-control-request-handlers-for-statususagemodel-queries","heading":"SDK control-request handlers for status\/usage\/model queries refactored into a lookup table","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/sdk-control-request-handlers-for-statususagemodel-queries","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### SDK control-request handlers for status\/usage\/model queries refactored into a lookup table\n\nSDK control-request handling for status and usage queries moved into a lookup table internally\n\n**What**\n\nThe code handling several SDK (software development kit) control-request types \u2014 `mcp_status`, `get_context_usage`, `get_usage`, `get_session_cost`, `list_models`, and `get_binary_version` \u2014 was restructured. These were previously handled by a long chain of if\/else checks and are now looked up in a dispatch table keyed by request type.\n\n**Why**\n\nThis is an internal restructuring with no described change in what these requests return or how they behave; it should make this part of the SDK's request handling easier to maintain.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}