Inspect
Look at another attempt. No creation, restart or extra cloud charge.
Use the current preparation workflow with one fixed sandbox. This separate workbench simulates future run management locally; it creates no resources.
NEXT / PRODUCT PREVIEWTHE NEXT CHAPTER
Next: a ready workspace, one view of every attempt, and results that outlive the sandbox.
Keep the code revision, environment, inputs, command and result together. A failed test can still have a healthy workspace. A disconnected monitor is not proof of a failed task.
Look at another attempt. No creation, restart or extra cloud charge.
Create a new attempt with pinned inputs. Keep the old run and its results.
Preserve edits, verify the new workspace, then switch access. On failure, keep the original.
See outcomes side by side, with the source and environment differences visible.
TWO LAYERS. ONE PRODUCT.
Core prepares the environment. The optional coordinator manages where and when native project tasks execute. It does not invent another compiler or build language.
Resolve · lock · sync · verify · activate
Plan · authorize · provision · observe · preserve results
Compute, isolation and provider-native lifecycle
A proposed SDK can coordinate preparation and workspace readiness, with permissions, spending limits, idempotency and cleanup. Setup-only targets remain setup-only.
plan → approve → prepare → activate → verifyThe preview does not launch sandboxes. Cross-provider process migration and production deployment are not promised. Open the design contracts for the full boundary.