{"version":"2.1.318","anchor":"auto-mode-denial-limit-fallback-can-be-timed-for-async-repl","canonical_anchor":"auto-mode-denial-limit-fallback-can-be-timed-for-async-repl","heading":"Permission prompts for REPL script calls, with an async path and timed fallback","tier":"internal","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/auto-mode-denial-limit-fallback-can-be-timed-for-async-repl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Permission prompts for REPL script calls, with an async path and timed fallback\n\nPermission prompts for REPL script calls gain one-time answers, an async lane and a timed denial-limit fallback via replAsyncAsk\n\n**Unclear.** The further condition that decides whether the timed fallback is used is not stated.\n\n**What**\n\nClaude Code is building a REPL scripting feature, a way for Claude to run small scripts that call tools, and is adding permission prompts for it. A permission prompt is when Claude asks whether it may do something.\n\n- When `oneTimeAnswersOnly` is set, each prompt records how it ended. The outcomes are yes, no, esc, closed, expired, hook allow, rules or mode, classifier allow and hook deny. It also records whether the lane was async or classic, how long it took, and the time limit.\n\n- Behind an internal check, a `replAsyncAsk` path waits to draw the prompt until it is first shown. Accepting or denying through the host dialog also runs an extra step.\n\n- In auto mode, once too many actions have been denied, a timed fallback can now be used for asks with `replAsyncAsk` set. Before, that condition could never be true.\n\n**Why**\n\nThis is groundwork for script calls that ask for permission. Prompts from that path can expire after a time limit instead of waiting, which a reader should know when an ask seems to disappear.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}