{"version":"2.1.318","anchor":"bash-read-only-auto-approval-helper-for-repl-script-commands","canonical_anchor":"bash-read-only-auto-approval-helper-for-repl-script-commands","heading":"Stricter rules for auto-approving commands run from REPL scripts","tier":"notice","area":"REPL Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/bash-read-only-auto-approval-helper-for-repl-script-commands","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Stricter rules for auto-approving commands run from REPL scripts\n\nA command written out in a REPL script is auto-approved as read-only only if it runs in the foreground and avoids several shell features\n\n**Unclear.** Whether REPL mode is available to users in this release is not stated.\n\n**What**\n\nClaude Code can approve some shell commands on its own when they only read things, so it does not have to ask you. For commands written out in a REPL script, a command now qualifies only if all of these hold:\n\n- No permission rule gives a reason to block it\n\n- It does not run in the background\n\n- It parses cleanly, with no errors\n\n- It has no stray `&`\n\n- It does not use `coproc`\n\n- It has no redirects other than `2>&1`\n\n**Why**\n\nThis decides which REPL-run commands go through without a permission prompt. Anything that breaks one of these rules gets a prompt instead.\n\n- Area: REPL Mode\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}