{"version":"2.1.299","anchor":"sandbox-socat-proxy-script-tracks-pids","canonical_anchor":"sandbox-socat-proxy-script-tracks-pids","heading":"Sandbox proxies are now tracked by process ID","tier":"internal","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/sandbox-socat-proxy-script-tracks-pids","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Sandbox proxies are now tracked by process ID\n\nThe script that starts the sandbox's HTTP and SOCKS proxies now records the process ID of each one\n\n**What**\n\nThe sandbox is a restricted environment Claude Code can run commands in. Inside it, a small script starts two network proxies (go-betweens for network traffic), one for HTTP and one for SOCKS. That script now records the process ID, the number the system gives each running program, of both proxies. It also adds some extra lines to the script.\n\n**Why**\n\nRecording the process IDs gives Claude Code a way to keep track of each proxy it starts.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}