{"version":"2.1.275","anchor":"sandbox-proxy-trap-now-preserves-the-shells-exit-code","canonical_anchor":"sandbox-proxy-trap-now-preserves-the-shells-exit-code","heading":"Sandbox proxy trap now preserves the shell's exit code","tier":"internal","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/sandbox-proxy-trap-now-preserves-the-shells-exit-code","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Sandbox proxy trap now preserves the shell's exit code\n\nSandbox proxy script now preserves the shell's real exit code instead of masking it on exit\n\n**What**\n\nThe launcher for the socat-based sandbox proxy has a shutdown trap that runs when the process exits. Previously it just killed background processes and exited plainly; now it first captures the actual exit code (`$?`), kills the background processes, and then re-exits with that captured code.\n\n**Why**\n\nThis means a sandboxed shell's real exit status is now correctly reported when it finishes, instead of being overwritten by the cleanup logic, so scripts or tools checking the exit code get an accurate result.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}