{"version":"2.1.321","anchor":"askuserquestion-timeout-can-be-admitted-as-nobody-answered","canonical_anchor":"askuserquestion-timeout-can-be-admitted-as-nobody-answered","heading":"Unanswered questions no longer stall some unattended sessions","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/askuserquestion-timeout-can-be-admitted-as-nobody-answered","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Unanswered questions no longer stall some unattended sessions\n\nIn sessions started from an artifact launcher, Claude can now carry on when the host reports nobody answered its question\n\n**What**\n\nClaude can stop to ask you a question with the AskUserQuestion tool. In sessions started from an artifact launcher, the host may report that nobody answered. Claude Code now lets the question finish and tells Claude \"The host reported that nobody answered the question\". It does this only when both of these are true:\n\n- The session comes from an artifact launcher.\n\n- The last message in the conversation is the person's own.\n\nExtra details about this offer are attached only when a remote switch is on. That switch is off unless it is turned on from the server.\n\n**Why**\n\nUnattended launcher sessions no longer wait indefinitely for an answer that will never come.\n\n- Flag `tengu_mellow_kestrel`: Not enough to say (read for one account on one subscription tier against v2.1.321; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}