{"version":"2.1.288","anchor":"ui-surface-control-requests-and-stale-tree-wording","canonical_anchor":"ui-surface-control-requests-and-stale-tree-wording","heading":"Groundwork for an on-screen interface protocol","tier":"internal","area":"UI Protocol","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/ui-surface-control-requests-and-stale-tree-wording","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Groundwork for an on-screen interface protocol\n\nClaude Code now sorts some control messages as interface requests and better explains when a button press was not handled\n\n**Unclear.** How these messages are reached and whether anything uses them yet is not known.\n\n**What**\n\nClaude Code now sorts some of the control messages it exchanges with other programs into a new interface category. The explanation for a button-press reply also covers one more case: the press is reported as not handled when it points at an on-screen element stored under a different key than the request used, and the program then asks for the interface to be drawn again.\n\n**Why**\n\nThis appears to be part of an interface protocol still being built.\n\n- Area: UI Protocol\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}