{"version":"2.1.299","anchor":"elicitation-requests-carry-property-order-hook-permissiondi","canonical_anchor":"elicitation-requests-carry-property-order-hook-permissiondi","heading":"Desktop hosts can keep form field order and word permission prompts","tier":"internal","area":"Desktop App","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/elicitation-requests-carry-property-order-hook-permissiondi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Desktop hosts can keep form field order and word permission prompts\n\nRequests for user input now keep the order of their fields, and hooks can supply wording for the desktop app's permission card\n\n**What**\n\nTwo additions for apps that host Claude Code, such as the desktop app:\n\n- Elicitation requests, which ask you to fill in a short form, now send `property_order`, the order the form's fields were defined in.\n\n- Hook output can now include an internal `permissionDisplay` field, so a host can word the permission card shown when a hook decides to ask you. Hooks are commands that run automatically at set points. This applies when the host says it supports host-worded prompts.\n\n**Why**\n\nHosts can show forms in their intended order and present permission prompts faithfully.\n\n- Area: Desktop App\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}