feat: add tensorlake sandbox workers to scode-ssh-delegate - #330
Merged
Conversation
Tensorlake sandboxes join SSH hosts and Fly.io sprites as a third worker kind because they offer knobs sprites lack: a chosen CPU/memory shape per sandbox, a tunable idle-suspend timeout, and filesystem snapshots that can be cloned into ready-made workers. Registration mirrors the sprite forms: `sbx foo` borrows an existing sandbox, `sbx:N` grants a budget of sandboxes the session creates, uses, and cleans up. The platform facts in tensorlake.md were verified hands-on in August 2026 against a live account (tl CLI 0.5.118). Two decisions worth recording. Owned sandboxes are created named rather than ephemeral, so that hitting the idle timeout suspends them and the tools installed during bootstrap survive, instead of the sandbox being destroyed mid-task. And cleanup has to delete not just the sandboxes but also their snapshots, which the platform creates on idle suspend and which outlive termination while billing storage monthly; that deletion is keyed on sandbox IDs recorded at creation, because the name-to-ID mapping disappears once a sandbox is terminated. The touched line in sprites.md is a reference fix: the shared base-packages heading in using-workers.md was renamed from "(both kinds)" to "(all kinds)".
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tensorlake sandboxes join SSH hosts and Fly.io sprites as a third
worker kind because they offer knobs sprites lack: a chosen CPU/memory
shape per sandbox, a tunable idle-suspend timeout, and filesystem
snapshots that can be cloned into ready-made workers. Registration
mirrors the sprite forms:
sbx fooborrows an existing sandbox,sbx:Ngrants a budget of sandboxes the session creates, uses, andcleans up.
The platform facts in tensorlake.md were verified hands-on in August
2026 against a live account (tl CLI 0.5.118). Two decisions worth
recording. Owned sandboxes are created named rather than ephemeral, so
that hitting the idle timeout suspends them and the tools installed
during bootstrap survive, instead of the sandbox being destroyed
mid-task. And cleanup has to delete not just the sandboxes but also
their snapshots, which the platform creates on idle suspend and which
outlive termination while billing storage monthly; that deletion is
keyed on sandbox IDs recorded at creation, because the name-to-ID
mapping disappears once a sandbox is terminated.
The touched line in sprites.md is a reference fix: the shared
base-packages heading in using-workers.md was renamed from "(both
kinds)" to "(all kinds)".