{"version":"2.1.307","anchor":"sandbox-prompt-windows-tls-pytest-hang-and-tmpdir-guidance","canonical_anchor":"sandbox-prompt-windows-tls-pytest-hang-and-tmpdir-guidance","heading":"Windows sandbox guidance covers HTTPS failures, pytest hangs and temp folders","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/sandbox-prompt-windows-tls-pytest-hang-and-tmpdir-guidance","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Windows sandbox guidance covers HTTPS failures, pytest hangs and temp folders\n\nClaude now knows that some Windows programs cannot use HTTPS in the sandbox, how to stop a pytest hang, and where PowerShell keeps temp files\n\n**What**\n\nThe sandbox is a fenced-off area that limits what commands can reach. On Windows, the instructions Claude Code gives the model about the sandbox now cover more cases:\n\n- HTTPS: programs that use Windows' own secure connection system, called Schannel, cannot make HTTPS connections in the sandbox. These include `curl.exe`, PowerShell's web commands, .NET HttpClient and `winget`.\n\n- pytest: a recent `pytest` in a project with no `.pytest_cache` folder yet can print its results and then never finish. The suggested fix is `-p no:cacheprovider`.\n\n- Temporary files: the advice about the temporary folder is now written for each shell, using `$env:TEMP` for PowerShell.\n\nThe note about `~\\` and `%USERPROFILE%` was removed from the advice on allowing file reads.\n\n**Why**\n\nWhen a command fails in the Windows sandbox, Claude is now better placed to explain why and suggest a workaround.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}