{"version":"2.1.304","anchor":"silent-turn-bounce-generalized-to-configurable-policy","canonical_anchor":"silent-turn-bounce-generalized-to-configurable-policy","heading":"Turns that end without a reply can be sent back more than once under a policy","tier":"internal","area":"Turn Handling","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/silent-turn-bounce-generalized-to-configurable-policy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Turns that end without a reply can be sent back more than once under a policy\n\nClaude Code's check for turns ending with no reply now supports a policy that can ask again several times\n\n**Unclear.** Where this policy comes from, and whether a user can set it, is not stated.\n\n**What**\n\nWhen a turn ends without Claude giving a reply, Claude Code can send it back and ask for one. Before, this happened once with fixed text. Alongside the existing Remote Control mode, there is now a policy mode with these settings:\n\n- `terminal_tools`\n\n- `ask_text`: the text used to ask again\n\n- `max_asks_after_person`: how many times to ask after a message from a person\n\n- `max_asks_after_server_event`: how many times to ask after an event from the server\n\nIt can ask several times. It does not ask when the turn ended in an API error, or stopped for reasons such as reaching the length limit (`max_tokens`) or a refusal.\n\n**Why**\n\nRe-asking driven by a policy can change how sessions end.\n\n- Area: Turn Handling\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}