docs(sdk): add migration guide to Together Sandbox#322
Open
christianalfoni wants to merge 6 commits into
Open
Conversation
Add a new SDK page walking through migrating from @codesandbox/sdk to together-sandbox: vocabulary mapping, auth/client changes, the create→start loop, per-namespace before/after examples (snapshots, lifecycle, execs, filesystem, ports, versioning), gaps without a direct equivalent, and a migration checklist. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Reframe intro: new infrastructure, factual tone only (no subjective claims) - Drop client option comparisons (baseUrl/retry/tracer) - Move "features without a direct equivalent" and the checklist near the top - Remove the "where Together is nicer" section Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Part 1 "Should you migrate?" — decision overview leading with the two proxy requirements (previews + browser access) and the unsupported- functionality table - Part 2 "Supported features" — capability→API map plus before/after usage - Part 3 — how to implement the preview proxy and browser proxy Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
CodeSandbox is now part of Together AI. Rework the guide to recommend a feature-parity destination first, then Together Sandbox: - Option 1 (recommended): Daytona — closest match to the CodeSandbox SDK (fork, snapshots, preview URLs + token auth, terminals, git, code interpreters, list/get, resize, CLI), with a feature-mapping table and before/after examples. - Option 2: Together Sandbox — highlights only the unsupported features and the two server-side pieces you must build (preview proxy, browser proxy). Rename page to "Migration Guide" (migration-guide.mdx). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
What
Adds a new SDK docs page: Migrate to Together Sandbox — a guide for moving from
@codesandbox/sdktotogether-sandbox.New page:
packages/projects-docs/pages/sdk/migrate-to-together-sandbox.mdx, linked under the Resources section in_meta.json.Contents
connect()→create()+start()split, namespace renames.CSB_API_KEY→TOGETHER_API_KEY.execs), filesystem (files/directories), terminals/PTY, ports, persistence/version history.Notes for review
list/get, no TTL/idle auto-hibernate, no hosts/preview URLs, no sessions) and where Together improves on CodeSandbox.🤖 Generated with Claude Code