Skip to content

fix(sandbox): Celesto maps every status and warns before dropping a stopped disk - #45

Merged
OmarAlex24 merged 3 commits into
fix/sandbox-settle-followupsfrom
feat/celesto-parity
Nov 13, 2026
Merged

OmarAlex24 merged 3 commits into
fix/sandbox-settle-followupsfrom
feat/celesto-parity

Conversation

@OmarAlex24

@OmarAlex24 OmarAlex24 commented Nov 13, 2026 •

Copy link
Copy Markdown
Owner

Problem

The Celesto driver lagged Boat's: statuses the API reports (restorable, pending) were unknown to it, the Sandboxes list never warned before Celesto drops a stopped disk, and the driver docs did not say which Boat capabilities Celesto cannot offer.

Change

Read against Celesto's own API client (Python package 0.1.13, generated from its API spec) and the TS SDK 0.1.6:

  • restorable (a spot move in progress) and pending (create) map to starting, so the sweep leaves those records alone.
  • info.diskRetentionDays is 30, from celesto.ai/pricing ("Stopped root disks are retained free for 30 days").
  • The docs record what Celesto cannot do today and why: no name, labels or metadata on create (no orphan detection), no files API (env files keep the sealed-exec path), no per-computer cost (the spend endpoint returns only top sandboxes), and external_volume_enabled (persistent home) is refused on the coding-agent template with a 422. A comment beside the create body says so, so the field is not re-added.

Desktop and templates are not part of this PR: the fork shows no Boat desktop today, and Celesto templates are built from a build script rather than saved from a machine.

Scope and approval

Requested by the fork owner in a T3 Code session (Celesto parity with Boat). Part of stack pingdotgg#43 on feat/sandbox-environments.

Verification

  • The provisioner's status table (SandboxProvisioner.test.ts) gained the new statuses; it failed before the mapping and passes after
  • vp run check:changed against fix/sandbox settle followups #44's branch passes format, lint, knip, typecheck and tests

Not checked against the live Celesto API (no key was available): the exec user and home, home surviving stop and start, and whether restorable restores without a start call.

Model and harness: Claude Opus 5.5 (implementation subagents at high effort, coordinated by Claude Opus 5.5) in Claude Code, running in T3 Code.

🤖 Generated with Claude Code

OmarAlex24 and others added 3 commits November 13, 2026 05:00
The status map left out `restorable`, which Celesto reports after a spot
interruption before it restores the sandbox on another host, and `pending`,
which its SDK waits through on create. Both now map to `starting`, so the
sweep leaves the record alone and a start keeps waiting instead of falling
through to an untracked state.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Celesto's pricing page says stopped root disks are kept for 30 days, and
the driver already reads `disk_delete_at` to report an expired sandbox.
Declaring `diskRetentionDays` lets the Sandboxes list and the settle prompt
warn before that happens, as they do for Boat.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Celesto's create takes no name, label, or project, so its sandboxes cannot
carry the host tag that orphan detection needs. Its persistent home is
refused on the coding-agent template, so a spot move may lose T3's state.
Say both where the driver contract and lifecycle describe Celesto, and
note the refused field beside the create body.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@OmarAlex24
OmarAlex24 added this pull request to stack #43 November 13, 2026 05:01
@OmarAlex24 OmarAlex24 changed the title feat/celesto parity fix(sandbox): Celesto maps every status and warns before dropping a stopped disk Nov 13, 2026
@OmarAlex24
OmarAlex24 marked this pull request as ready for review November 13, 2026 13:41
@OmarAlex24
OmarAlex24 merged commit b945cf7 into feat/sandbox-environments Nov 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant