Skip to content

Tailscale · 1 November 2026

New sandboxes can join a tailnet again

POST /v1/sandboxes/{id}/tailscale, GET /v1/sandboxes/{id}/tailscale, DELETE /v1/sandboxes/{id}/tailscale, and the tailscale field on POST /v1/sandboxes and POST /v1/sandboxes/{id}:update now work for every sandbox. Previously, these requests returned 501 feature_unavailable for some newly created sandboxes. The rules have not changed: the auth key is read from your job secret with your key's own permission to reveal it and is never returned or logged. While a sandbox is on a tailnet, forking it or taking a memory snapshot of it returns 409 tailscale_joined. If a create with tailscale cannot join, the sandbox is stopped and the request returns 422 tailscale_failed.

Same day.

Cut your cloud billby 75%.

No card to start. Billed by the second after.

Start free, no card