{"version":"2.1.289","anchor":"device-hook-ask-distinguishes-failure-cause-next-unapplie","canonical_anchor":"device-hook-ask-distinguishes-failure-cause-next-unapplie","heading":"Questions sent to an interface host now report why they failed","tier":"internal","area":"Plugin UI","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289\/e\/device-hook-ask-distinguishes-failure-cause-next-unapplie","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289","markdown":"### Questions sent to an interface host now report why they failed\n\nWhen Claude Code asks an interface host a question, a failure now comes back with a reason instead of an empty result\n\n**Unclear.** What uses these failure reasons is not shown.\n\n**What**\n\nWhen Claude Code sends a question to an interface host (the program displaying Claude Code), it now gets back the answer together with a reason. The reason is either that the question was never asked or the cause of the error. Before, any failure simply returned nothing. A separate check on arguments passed between steps also gained a path for arguments that were never applied.\n\n**Why**\n\nThis is internal groundwork for interface hosts and does not change anything a reader does directly.\n\n- Area: Plugin UI\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}