fix(sandbox): the release probe checks the display from inside the box

Merged
SA
2mo ago
+115-221

The desktop port stopped being published in #7602, so sandbox.domain(6080) throws and the production release fails at the probe:

error: No route for port 6080

The probe now opens the websocket from inside the box, against the loopback address websockify listens on, which is what the pane reaches through host-service anyway.

https://claude.ai/code/session_01FK6rLzBEUiHHXZWNmpQ2BP


Summary by cubic

Fixes release probes after the desktop port stopped being published by checking the desktop stream through host-service instead of sandbox.domain(6080). Probes now run the normal repository start hook without Neon credentials, so setup keeps the image’s database and cannot create a throwaway branch.

  • The websocket uses /desktop/websockify with the host secret; the legacy /websockify route is removed.
  • Cloud setup runs from the repository’s start hook and detects completion from the workspace’s .env.
  • Hook commands run independently, so later services still start after an earlier step fails.
  • The image no longer carries duplicate setup scripts, and the CLI asset ships without a .bin suffix.

Summary by CodeRabbit

  • New Features

    • Sandbox workspaces now support authentication without a user API key.
    • Desktop connectivity uses a sandbox-specific WebSocket route with improved handshake validation.
    • Cloud setup runs automatically as part of the start process and safely skips completed setup.
  • Bug Fixes

    • Prevented API client failures when no bearer token is provided.
    • Improved discovery and installation of CLI executables without a file extension.
    • Muse settings are now created and configured consistently.
  • Changes

    • Removed the separate provisioning hook; one-time setup should be handled by idempotent start steps.
    • Restricted Neon credentials from being passed into probe environments.