{"version":"2.1.323","anchor":"powershell-parse-timeout-is-now-capped","canonical_anchor":"powershell-parse-timeout-is-now-capped","heading":"The PowerShell parse timeout setting is now capped at a maximum","tier":"use","area":"Elsewhere","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/powershell-parse-timeout-is-now-capped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### The PowerShell parse timeout setting is now capped at a maximum\n\nA value set in `CLAUDE_CODE_PWSH_PARSE_TIMEOUT_MS` is now cut down to a built-in maximum instead of being used exactly as given\n\n**Unclear.** The maximum value is not stated.\n\n**What**\n\nBefore running a PowerShell command, Claude Code reads (parses) it to check what it does. The environment variable `CLAUDE_CODE_PWSH_PARSE_TIMEOUT_MS` sets how long, in milliseconds, that reading may take. Any positive value used to be taken as given. A value above a built-in maximum is now reduced to that maximum.\n\n**Why**\n\nIf you set a very large timeout, Claude Code now quietly uses a smaller one.\n\n- Area: Elsewhere\n- Names: `CLAUDE_CODE_PWSH_PARSE_TIMEOUT_MS`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}