Sandbox fails to start after PC reboot

[GenMachine]

Bug Report: Sandbox fails to start after PC reboot

Summary

After restarting the PC, an existing sandbox fails to start and returns an internal server error.

Environment

• Product: SBX
• Sandbox Runtime: opencode
• OS: Windows
• Issue first observed: After system reboot

Error Message

Failed to start sandbox "opencode-web": start runtime "opencode-web": start runtime: request failed: 500 Internal Server Error: failed to start runtime

Steps to Reproduce

1. Create and start a sandbox named opencode-web.
2. Verify that the sandbox starts successfully.
3. Restart the host machine.
4. Attempt to start the same sandbox again.

Expected Behavior

The sandbox should start normally after the machine reboot.

Actual Behavior

The sandbox fails to start and returns:

500 Internal Server Error: failed to start runtime

Additional Information

• The sandbox starts successfully when it is first created.
• I can stop and start the sandbox multiple times without any issues as long as the host machine has not been rebooted.
• After shutting down or restarting the PC, the same sandbox can no longer be started.
• The issue appears to be triggered specifically by a host reboot rather than by stopping and starting the sandbox itself.

[tfleis]

I can confirm that I’m seeing the same behavior. From my perspective, the root cause seems to be that secrets are no longer automatically injected into the requests by the proxy. In Codex, I’m receiving HTTP 401 responses from our API gateway. It only starts working again after recreating the sandbox.

[kiview]

@GenMachine that sounds like a duplicate of #185.
@tfleis Your error sounds entirely different.