{"version":"2.1.268","anchor":"bash-tool-execution-now-threads-sandbox-network-lists-comput","canonical_anchor":"bash-tool-execution-now-threads-sandbox-network-lists-comput","heading":"Bash tool execution now threads sandbox network lists computed at permission time into the actual spawn","tier":"internal","area":"Sandbox Network","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/bash-tool-execution-now-threads-sandbox-network-lists-comput","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Bash tool execution now threads sandbox network lists computed at permission time into the actual spawn\n\nBash commands now reuse the network access list computed when permission was checked, instead of recalculating it at run time\n\n**What**\n\nWhen Claude Code runs a shell command inside its sandbox (a restricted environment that limits what a command can access), it now carries forward the network access list that was already worked out during the permission check for that command, and hands it directly to the process that actually runs the command. This is done through a small cache (holding up to 256 entries) keyed to the specific command, so the cached list is only reused if the command text still matches.\n\n**Why**\n\nThis keeps the network rules used at execution time consistent with the ones the user (or policy) already approved, rather than recomputing them separately and risking a mismatch.\n\n- Area: Sandbox Network\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}