Add sandbox commands by marius-baseten · Pull Request #126 · basetenlabs/baseten-cli

marius-baseten · 2026-09-30T22:16:38Z

(adjusted from original PR description as changes came about -@cretz)

🚀 What

baseten sandbox list: lists sandboxes, filtered by --query and --status, up to --limit
baseten sandbox describe: shows one sandbox, with --show-secrets to reveal secret env values
baseten sandbox create: creates a sandbox, sending only the flags given
baseten sandbox update: changes a sandbox's image, env vars, or labels
baseten sandbox delete: deletes a sandbox after confirming
baseten sandbox exec: runs a command and streams its output, passing through its exit code
baseten sandbox connect: opens an interactive shell in a sandbox
baseten sandbox process
- start: starts a command in the background
- list: lists processes
- describe: shows one process
- logs: prints a process's output, with --tail to follow it
- wait: waits for a process to exit, passing through its exit code
- stop: asks a process to stop
- kill: asks a process to be killed
baseten sandbox image
- list: lists images, up to --limit
- describe: shows one image
- push: pushes an image from a directory or a registry, with --wait to wait for the build
- delete: deletes an image after confirming
- logs: prints an image's build logs
- list-tags: lists an image's tags
- list-library: lists the platform's starter images
baseten api sandbox: direct API calls to sandbox exec plane (matching management and inference forms that already exist for other APIs)

💻 How

Built on the high-level sandbox package from baseten-go#60
Control plane commands call the generated API through the sandbox client and print the API's own records
Execution API commands use the high-level client, which retries idempotent calls
Sandbox tokens are minted through the session's management client, so API keys and OAuth logins both work
Sandbox API errors map to the CLI's exit codes and JSON error envelope
connect speaks the sandbox's terminal WebSocket in internal/sandboxconnect
New dependencies: github.com/moby/patternmatcher (Docker's .dockerignore matcher) and github.com/creack/pty (tests only, not in the binary)

🔬 Testing

Unit tests per command file against the mock API, which also serves the sandbox's own API
E2E tests against staging: every command, connect through a real pseudo-terminal, and one image push from a directory with a .dockerignore
E2E runs on Linux only, as the rest of the suite does

Important review notes and deviations

Thin layer over the API
- Control plane JSON is the generated API type as is, matching the rest of the CLI
- Execution API JSON is the high-level client's record mapped back to the generated type, since those calls go through the high-level client for its retries. Timestamps come out as RFC 3339
- No client-side checks for what the server rejects
- --team defaults to your only team and is required if you belong to more than one, which is the API's behavior. Other commands default to the organization's default team
Naming
- --name is always the command's own resource: the sandbox, or the image under image. Processes are --pid or --process-name
- Flags take the API's field names (--memory), except --if-not-exists (shortened from create_if_not_exists) and the singular repeatable --env and --label
- Only sandbox exec, not also process exec, since it is the most common action
- image list-library, a verb like every other leaf command
- --status values are lowercase like other CLI enums
Lists
- list and image list collect pages up to --limit (default 1000) and print {"items": [...]}, like every other list
- Blaxel's CLI instead shows one page of 200 with a next-page cursor hint
- Streamed output would be a breaking change later, so we may want to discuss it for all list commands together
create
- No --wait: create returns once the sandbox is deployed, and the SDKs have no wait either
- --env values are secret (the server's default) and --plain-env values are not. Both need KEY=VALUE. A docker-style --env KEY read from the local environment would keep secrets out of shell history, but no other command does that yet
exec and processes
- exec is basically process start then process wait, with streamed output and --stdin
- One argument after -- is the whole command line for the sandbox's shell. Several are quoted so each stays one argument
- With --stdin, output arrives line by line, since stdin can only be written once the process exists
- process logs --tail replays from the start, then follows
- Without --tail, log lines have no stream, since the API's output so far does not say which stream a line came from
- stop and kill request termination and do not wait for it
- No write-stdin or close-stdin commands, since exec --stdin covers piping
- No check that a sandbox is deployed before using it. The API reports its own error
Images
- push --dir leaves out paths per a root .dockerignore, read with Docker's own matcher, so the upload matches what Docker would build
- Without a .dockerignore, the defaults are Blaxel's CLI's list, documented in the help as the equivalent .dockerignore
- Blaxel's CLI reads .blaxelignore instead, and matches unanchored names at any depth. We follow Docker
- The directory is zipped to a temporary file and uploaded with its length, as Blaxel's CLI does, so memory stays flat
- push --wait is opt-in, since builds take minutes
- --image became --registry-image so it does not read like the image's name
- image logs prints at most the newest 11,000 lines, the API's limit
- image list-library has no --team
connect
- Fails before connecting unless both stdin and stdout are terminals
- Each connect is a new shell
- The terminal endpoint is not in the API spec, so it is not in the SDK
- Windows has no resize signal, so the window keeps its starting size
Not included: filesystem commands, drives, and the other execution API features the SDK has

CLAassistant · 2026-09-30T22:17:22Z

All committers have signed the CLA.

Copilot

Copilot review overview

🟡 Changes recommended

Omitted update flags can clear environment variables, exec corrupts quoted arguments, and E2E failure cleanup is ineffective.

Review effort: Balanced
Findings: 2 · 1 · 3

Open (6)

Preserve argv boundaries when constructing shell commands · New
Omitted --env clears existing sandbox environment variables · New
Register cleanup at the parent test lifecycle · New
Text delete output omits the returned sandbox record · New
Place --jq before the command separator · New
Assert partial updates omit environment changes · New

What changed in this PR

Adds pre-release sandbox lifecycle and command execution support to the CLI.

Changes:

Adds list, describe, create, update, start, stop, delete, and exec commands.
Integrates the high-level sandbox SDK client.
Adds unit and end-to-end lifecycle coverage.

File	Description
`cmd/command.go`	Registers the sandbox command group.
`cmd/command.sandbox.go`	Defines sandbox commands, flags, help, and outputs.
`internal/cmd/command.sandbox.go`	Implements sandbox operations and exec streaming.
`internal/cmd/command.sandbox_test.go`	Tests command behavior and API requests.
`internal/cmd/command_context.go`	Constructs authenticated sandbox clients.
`internal/e2e-tests/sandbox_test.go`	Adds sandbox lifecycle E2E coverage.
`go.mod`	Updates the sandbox-capable SDK dependency.
`go.sum`	Records updated dependency checksums.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Copilot

Copilot review overview

🟡 Changes recommended

JSON execution does not wait for completion, terminal failures are hidden, and the new E2E suite is not enabled in CI.

Review effort: Balanced
Findings: 4 · 2

Open (6)

Reject negative memory values instead of silently defaulting · New
Wait for process completion before emitting JSON output · New
Export the sandbox E2E API key in the CI workflow · New
Propagate WebSocket read errors instead of treating them as disconnects · New
Public sandbox image commands exceed the stated PR scope · New
Text delete output omits the returned sandbox record

Resolved since last review (5)

Omitted --env clears existing sandbox environment variables
Preserve argv boundaries when constructing shell commands
Register cleanup at the parent test lifecycle
Assert partial updates omit environment changes
Place --jq before the command separator

Copilot

Copilot review overview

🟡 Changes recommended

JSON execution, token handling, terminal errors, and the missing start/stop commands contain blocking issues.

Review effort: Balanced
Findings: 1 · 7 · 4

Open (12)

Redact sandbox tokens from WebSocket errors · New
Stream or spool directory archives to limit memory use · New
Implement or remove advertised start and stop commands · New
Require a name with --if-not-exists · New
Propagate WebSocket read errors instead of treating them as disconnects
Export the sandbox E2E API key in the CI workflow
Wait for process completion before emitting JSON output
Reject negative memory values instead of silently defaulting
Document image build logs included in failures · New
Avoid claiming builds continue after every interruption · New
Public sandbox image commands exceed the stated PR scope
Text delete output omits the returned sandbox record

Previously missed (1)

In code that hasn't changed since last review

Set a read deadline before checking test timeout

internal/sandboxconnect/terminal_test.go:110

The timeout check occurs only after the blocking pipe read returns, so a missing echo can hang this test until the suite-wide timeout; time.After does not bound the read. Set a read deadline before entering the loop.

Copilot

Copilot review overview

🟡 Changes recommended

Terminal failures are reported as success, input validation is incomplete, and the exposed commands conflict with the stated PR scope.

Review effort: Balanced
Findings: 2 · 7 · 4

Open (13)

Pipe read deadline does not bound the blocking read · New
Redact sandbox tokens from WebSocket errors
Require a name with --if-not-exists
Implement or remove advertised start and stop commands
Stream or spool directory archives to limit memory use
Propagate WebSocket read errors instead of treating them as disconnects
Export the sandbox E2E API key in the CI workflow
Wait for process completion before emitting JSON output
Reject negative memory values instead of silently defaulting
Avoid claiming builds continue after every interruption
Document image build logs included in failures
Public sandbox image commands exceed the stated PR scope
Text delete output omits the returned sandbox record

Previously missed (1)

In code that hasn't changed since last review

Terminal errors bypass the injected stderr writer

internal/sandboxconnect/terminal.go:153

This bypasses the command's injected stderr and writes to the process-global stream, so callers using ExecuteOptions.Stderr cannot capture terminal error frames. It also violates the repository rule to route stderr through context-owned logging (CONTRIBUTING.md:9). Pass an io.Writer for stderr into Dial/Terminal and write the frame there.

Copilot

Copilot review overview

🔵 Needs a closer look

Text output, source validation, terminal stream handling, and test timeout behavior contain unresolved defects.

Review effort: Balanced
Findings: 1 · 2 · 1

Open (4)

Pipe read deadline does not bound the blocking read
Stream or spool directory archives to limit memory use
Export the sandbox E2E API key in the CI workflow
Text delete output omits the returned sandbox record

Resolved since last review (9)

Redact sandbox tokens from WebSocket errors
Require a name with --if-not-exists
Implement or remove advertised start and stop commands
Propagate WebSocket read errors instead of treating them as disconnects
Wait for process completion before emitting JSON output
Reject negative memory values instead of silently defaulting
Avoid claiming builds continue after every interruption
Document image build logs included in failures
Public sandbox image commands exceed the stated PR scope

Previously missed (6)

In code that hasn't changed since last review

Validate mutually exclusive source flags before client creation

cmd/command.sandbox.go:328

These flags promise exactly one source, but unlike other exclusive/required flag groups they omit the framework's oneof metadata (internal/cmd/command.go:667-677). Validation therefore happens only inside the SDK after credential resolution and after the command has printed “Waiting for image ...”, so invalid invocations can report an auth error or misleading progress instead of a usage error. Validate the pair before constructing the client, preferably via a shared oneof tag.

Text output omits environment variables with --show-secrets

internal/cmd/command.sandbox.go:84

--show-secrets is sent to the API, but the default text path immediately passes the result to outputSandboxInfo, which never renders info.Envs. As a result, baseten sandbox describe NAME --show-secrets succeeds without revealing any values unless the user also knows to request JSON. Render the environment variables in text mode (deterministically), or explicitly require/document structured output for this flag.

Display unavailable image creation time as -

internal/cmd/command.sandbox.go:440

ImageInfo.CreatedAt can be zero when the optional API field is absent (including the existing UPLOADING test fixture), so this renders 0001-01-01T00:00:00Z in the table. Match the sandbox list and detail renderer by showing - when the timestamp is unavailable.

Route terminal errors through the injected stderr writer

internal/sandboxconnect/terminal.go:165

This bypasses the command's injected stderr and writes to the process-global os.Stderr, so terminal protocol errors cannot be captured by ExecuteOptions.Stderr and violate the repository rule to route stderr through ctx.Log* (CONTRIBUTING.md:9). Pass an error writer into Terminal and use ctx.Stderr from the caller instead.

Preserve UTF-8 characters across terminal read chunks

internal/sandboxconnect/terminal.go:177

Converting each arbitrary Read chunk directly to a string can corrupt UTF-8 input. A paste larger than 512 bytes can split a multibyte character at the buffer boundary, and json.Marshal replaces each invalid fragment with U+FFFD before sending it. Buffer incomplete UTF-8 sequences (or read complete runes) so terminal input survives chunk boundaries.

Fix typo in test command

internal/cmd/command.sandbox_test.go:442

Correct the typo in this test command so the fixture reads naturally.

baseten sandbox list/describe/create/update/start/stop/delete/exec per the M1 spec, over the baseten-go high-level sandbox client. Create waits for DEPLOYED by default; exec shell-quotes argv into the command string, streams output, and passes the command's exit code through. Update keeps omitted --env unchanged rather than clearing. E2E cases join the e2e suite, gated additionally on BASETEN_E2E_TEST_SANDBOXES_URL. Co-Authored-By: Claude Code <noreply@anthropic.com>

baseten sandbox image list/describe/push/delete over the SDK's image client, and sandbox connect NAME, a raw-mode terminal to a deployed sandbox over its /terminal/ws WebSocket. Push waits for BUILT by default; connect reuses the repo's coder/websocket dependency and requires an interactive terminal. Co-Authored-By: Claude Code <noreply@anthropic.com>

The server's default session is shared, so a second connect rejoins a shell an earlier one may have left dead; each dial now carries a fresh session id and its window size, matching the reference client. The round trip and the close path are unit tested against a local terminal server. Co-Authored-By: Claude Code <noreply@anthropic.com>

Co-Authored-By: Claude Code <noreply@anthropic.com>

Shell-quoting every argument broke the one-quoted-string style: the whole command arrived wrapped in single quotes and the sandbox's shell looked for a program by that whole name. One argument now passes as the command string with its quoting intact; several arguments are still re-quoted so word boundaries survive. Co-Authored-By: Claude Code <noreply@anthropic.com>

A whole command string passes to the sandbox shell verbatim, so the case exercises remote variable expansion and redirects. Co-Authored-By: Claude Code <noreply@anthropic.com>

Chad's spec refresh (baseten-go 7b8c438) serves GET /v1/sandboxes/library_images through the Baseten management API, which supersedes the Blaxel hub path and the client-side hidden and coming-soon filtering (the server drops those entries). The Sandbox record also lost its state field; the curated record and the list table follow. Co-Authored-By: Claude Code <noreply@anthropic.com>

The served library_images endpoint is team-scoped like every other sandbox command; the list table lost the STATE column with the state field. Co-Authored-By: Claude Code <noreply@anthropic.com>

- Render environment variables in describe's text output, sorted, so --show-secrets shows values without --output json. - Validate the image push source flags with the framework's oneof group at parse time, before any client or progress output. - Show '-' for a missing image creation time in the image list table. - Route terminal protocol errors through the command's stderr instead of the process global. - Hold back partial UTF-8 sequences at read boundaries in the terminal input loop, so pasted multi-byte characters survive the 512-byte chunking; covered by a test that splits a rune across two reads. - Bound the terminal test's blocking echo read with a pipe read deadline, so a missing echo fails instead of hanging. Co-Authored-By: Claude Code <noreply@anthropic.com>

The catalog is available to every team; the endpoint's team parameter is uniform spec plumbing, and --team implied wrong semantics. Co-Authored-By: Claude Code <noreply@anthropic.com>

The alias and process exec render the same help; one const, following sandboxPreRelease and volumePreRelease. Co-Authored-By: Claude Code <noreply@anthropic.com>

Deletes internal/sandboxclient: the CLI consumes the sandbox package from baseten-go#60 directly, now that it covers the whole surface (create_if_not_exists, show_secrets, process list/logs, image push with spooling, library listing). Three contract points kept through the swap: - JSON stays snake_case: the SDK types carry no tags, so the CLI wraps its records in output DTOs, keeping --jq examples honest. - Terminal output streams chunks as written; no synthetic newlines. - The BASETEN_SANDBOXES_API_URL_OVERRIDE env var is gone: the sandbox control plane serves on the management domain, verified against staging. The e2e suite follows: no separate sandboxes URL gate, and the process phase reads the pid from JSON instead of the human output. Co-Authored-By: Claude Code <noreply@anthropic.com>

Rebased on latest main (drops the README bump, already upstream); the alias and process exec share their output descriptions through consts so they cannot drift. Co-Authored-By: Claude Code <noreply@anthropic.com>

The lint gate runs go mod tidy and go fmt with a diff check. Co-Authored-By: Claude Code <noreply@anthropic.com>

Co-Authored-By: Claude Code <noreply@anthropic.com>

cretz

Did high-level review of just some commands/flags, did not review actual logic

cretz · 2026-10-02T21:32:00Z

+				"Lists every sandbox in the team, following every server page. Filter by free-text " +
+				"--query or repeatable --status.",
+			Flags: SandboxListFlags{},
+			Output: &CommandOutput[SandboxList]{


For every list thus far we have just collected the whole thing and shown it, but for metrics/usage/logs stuff, we stream it out to user (which has built-in backpressure if they are using a pager like less). Sandbox list is said to get pretty large, I wonder if we want to stream or if maybe we want to expose pagination details to users so they can repeatedly call.

I agree. For CLIs would stream or page be more ergonomic (and also do you expect agents to use this)?
I think a lot of use cases pragmatically want stuff recency based, so a query filter for last active or created at might be more important than free form text.

All of our list calls today do not stream for JSON (they do for text, and they do for JSON calls like logs), they page internally and we have --limits in some cases. So using a pager like less does work and provide backpressure I believe. Blaxel SDK does the same thing but exposes cursors to users to get successive pages.

What I think is best here is not to stream list (we don't anywhere else, but we will for logs) and provide a reasonable default --limit and if we need to support explicit user paging or streaming, we can discuss in the context of the CLI as a whole.

Makes sense to me.

What do you think about recency filters?

If/when the API supports it, we can add to all of the interfaces no prob. What my current code is doing (will be in PR early tomorrow, e2e failing atm) is having --limit default to 1000, but you can override it. This encourages users to give a more specific query or status filter or explicitly override and allows us to do more in the future such as user-controlled pagination.

cretz · 2026-10-02T21:37:52Z

+				"By default the command returns as soon as the server accepts the create; " +
+				"--wait blocks until the sandbox is DEPLOYED and then prints its execution URL.",
+			Flags: SandboxCreateFlags{},
+			Output: &CommandOutput[sandbox.Info]{


sandbox.Info does not conform to our expected JSON form elsewhere. I think this just was meant to be SandboxInfoOutput or something.

So we need to decide, are we doing more raw calls like we do elsewhere or high-level client calls? I'm leaning to former (still using high-level client so you get token provider) so that we can use the proper JSON object the API uses like we do elsewhere in CLI (this applies to other commands too).

Makes sense to me.

cretz · 2026-10-02T21:40:50Z

+// imageSubcommands is the image family under baseten sandbox image. Images
+// are the sources sandboxes are created from; push builds one from a
+// directory or imports one from a registry.
+var imageSubcommands = Command{


I think this is better inlined where referenced above or its own file (both match what we've done elsewhere, this is different though)

cretz · 2026-10-02T21:41:49Z

+// SandboxNameFlags selects one sandbox by name.
+type SandboxNameFlags struct {


To match others, maybe SandboxRefFlags as I suspect ID may come about one day too

cretz · 2026-10-02T21:43:38Z

+type SandboxListFlags struct {
+	SandboxTeamFlags
+	Query  string   `flag:"query" desc:"Free-text search over sandbox names and labels."`
+	Status []string `flag:"status" desc:"Only sandboxes with one of these statuses, for example DEPLOYED. May be repeated."`


Can be a flag with an enumerate

cretz · 2026-10-02T21:58:22Z

+	Region      string   `flag:"region" desc:"Region to run in. Defaults to the closest region."`
+	MemoryMB    int      `flag:"memory-mb" desc:"Memory in megabytes, which also sets the CPU allocation. Defaults to 4096."`
+	Image       string   `flag:"image" desc:"Image reference including its tag. Defaults to the built-in sandbox image."`
+	Env         []string `flag:"env" desc:"Environment variable as KEY=VALUE. May be repeated."`


People need a way to pass envs that are secrets (which is the default)

cretz · 2026-10-02T21:59:22Z

+// image-library. The library is available to every team, so no team
+// selection applies.
+var imageLibrarySubcommands = Command{
+	Name:    "image-library",


Given we don't expect any more subcommands here, I think under image, either library or list-library is probably good

I think my rationale was that this a resource distinct from the custom images (and e.lg. has no --teams flag either). The endpoint is /v1/sandboxes/library_images (which would be an argument to line up the command name). But I'm ok with making this a subcommand of image, if that plays well with leaving the team-flag out.

The endpoint I think is /v1/sandboxes/library_images because it couldn't be put under /images/{image_name} because that accepts names on the path afterwards. In SDKs we put this under the images sub-service. Yeah, team flag is per call (even though every sandbox call besides this one will have it.

cretz · 2026-10-02T22:01:00Z

+// processLogsOutput is the JSON shape of a process's captured output.
+type ProcessLogsOutput struct {


I can't find where this is used

cretz · 2026-10-02T22:03:06Z

+var sandboxInteractionCommands = []Command{
+	processSubcommands,
+	{
+		Name:      "exec",


Need to decide if we want the duplicated commands of baseten exec and baseten process exec. In SDKs and API, exec is under process, not top level

cretz · 2026-10-02T22:09:49Z

+				"Prints one process's captured output: standard output and standard error, " +
+				"interleaved.",
+			Flags: SandboxProcessLogsFlags{},
+			Output: &CommandOutput[sandbox.ProcessLogs]{


There is an internal discussion to be had about the ability to stream logs (you are allowed to during exec but not afterwards)

Copilot

Copilot review overview

🟡 Changes recommended

Stdin failures can hang execution, and unrelated Dockerignore exclusions can incorrectly preserve ignored directories.

Review effort: Balanced
Findings: 1 · 1

Open (2)

Prevent stdin copy failures from hanging process waits · New
Avoid uploading ignored directories for unrelated exclusions · New

Resolved since last review (4)

Pipe read deadline does not bound the blocking read
Stream or spool directory archives to limit memory use
Export the sandbox E2E API key in the CI workflow
Text delete output omits the returned sandbox record

cretz · 2026-10-06T20:49:03Z

Added baseten api sandbox command

Copilot AI balanced review requested due to automatic review settings September 30, 2026 22:16

Copilot started reviewing on behalf of marius-baseten September 30, 2026 22:17 View session

marius-baseten force-pushed the marius/sandbox-commands branch from 3a3515f to bce6ed8 Compare September 30, 2026 22:17

Copilot AI reviewed Sep 30, 2026

View reviewed changes

marius-baseten force-pushed the marius/sandbox-commands branch 3 times, most recently from 43bdede to 0c8c503 Compare September 30, 2026 22:59

marius-baseten requested a balanced review from Copilot October 1, 2026 00:00

Copilot started reviewing on behalf of marius-baseten October 1, 2026 00:01 View session

Copilot AI reviewed Oct 1, 2026

View reviewed changes

Comment thread internal/cmd/command.sandbox.go Outdated

Comment thread internal/cmd/command.sandbox.go Outdated

Comment thread internal/e2e-tests/sandbox_test.go Outdated

Comment thread internal/sandboxconnect/terminal.go Outdated

Comment thread cmd/command.sandbox.go Outdated

marius-baseten requested a balanced review from Copilot October 1, 2026 00:51

Copilot started reviewing on behalf of marius-baseten October 1, 2026 00:52 View session

Copilot AI reviewed Oct 1, 2026

View reviewed changes

marius-baseten force-pushed the marius/sandbox-commands branch from 8c46d2d to 8eea73c Compare October 1, 2026 01:10

marius-baseten requested a balanced review from Copilot October 1, 2026 01:13

Copilot started reviewing on behalf of marius-baseten October 1, 2026 01:13 View session

Copilot AI reviewed Oct 1, 2026

View reviewed changes

Comment thread internal/sandboxconnect/terminal_test.go Outdated

marius-baseten requested a balanced review from Copilot October 1, 2026 17:04

Copilot started reviewing on behalf of marius-baseten October 1, 2026 17:05 View session

Copilot AI reviewed Oct 1, 2026

View reviewed changes

marius-baseten force-pushed the marius/sandbox-commands branch 3 times, most recently from 1e35c94 to f381a67 Compare October 1, 2026 19:52

marius-baseten and others added 6 commits October 2, 2026 13:12

Drop a dead assertion and its narration comment

ba75176

Co-Authored-By: Claude Code <noreply@anthropic.com>

Cover the single-quoted exec style in e2e

11ca00b

A whole command string passes to the sandbox shell verbatim, so the case exercises remote variable expansion and redirects. Co-Authored-By: Claude Code <noreply@anthropic.com>

marius-baseten and others added 7 commits October 2, 2026 13:12

Give image-library the shared team flag and drop the stale STATE column

9d66b95

The served library_images endpoint is team-scoped like every other sandbox command; the list table lost the STATE column with the state field. Co-Authored-By: Claude Code <noreply@anthropic.com>

Drop the team selector from image-library

81e8bb2

The catalog is available to every team; the endpoint's team parameter is uniform spec plumbing, and --team implied wrong semantics. Co-Authored-By: Claude Code <noreply@anthropic.com>

Share the exec description through a const

675834a

The alias and process exec render the same help; one const, following sandboxPreRelease and volumePreRelease. Co-Authored-By: Claude Code <noreply@anthropic.com>

Minimize churn on the sandbox command surface

87e0a23

Rebased on latest main (drops the README bump, already upstream); the alias and process exec share their output descriptions through consts so they cannot drift. Co-Authored-By: Claude Code <noreply@anthropic.com>

marius-baseten force-pushed the marius/sandbox-commands branch from 15d6419 to 87e0a23 Compare October 2, 2026 20:17

marius-baseten and others added 2 commits October 2, 2026 13:47

Tidy modules and format the sandbox client options

5ac34ad

The lint gate runs go mod tidy and go fmt with a diff check. Co-Authored-By: Claude Code <noreply@anthropic.com>

Follow baseten-go#60's latest head

eb5da60

Co-Authored-By: Claude Code <noreply@anthropic.com>

cretz reviewed Oct 2, 2026

View reviewed changes

marius-baseten assigned cretz Oct 5, 2026

cretz added 2 commits October 5, 2026 15:32

Rework sandbox commands on the latest sandbox SDK

f876ee8

Merge remote-tracking branch 'origin/main' into marius/sandbox-commands

ab38b00

cretz requested review from cploujoux and a balanced review from Copilot October 5, 2026 22:29

Copilot started reviewing on behalf of cretz October 5, 2026 22:30 View session

Copilot AI reviewed Oct 5, 2026

View reviewed changes

Comment thread internal/cmd/command.sandbox.go Outdated

Comment thread internal/cmd/command.sandbox_image.go Outdated

Fix sandbox e2e and address review feedback

8edbaa7

cploujoux reviewed Oct 6, 2026

View reviewed changes

Comment thread internal/cmd/command.sandbox_process.go

Add api sandbox command

f22a9a6

Update sandbox commands for latest SDK

0f7d368

cploujoux approved these changes Oct 7, 2026

View reviewed changes

squidarth approved these changes Oct 7, 2026

View reviewed changes

cretz added 3 commits October 7, 2026 14:54

Avoid streaming exec in sandbox image e2e

d6a77c1

Update baseten-go to v0.4.0

e540906

Merge branch 'main' into marius/sandbox-commands

ee8744a

cretz merged commit ad5345d into main Oct 7, 2026
4 checks passed

cretz deleted the marius/sandbox-commands branch October 7, 2026 22:11

		// SandboxNameFlags selects one sandbox by name.
		type SandboxNameFlags struct {

		// processLogsOutput is the JSON shape of a process's captured output.
		type ProcessLogsOutput struct {

Conversation

marius-baseten commented Sep 30, 2026 • edited by cretz Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🚀 What

💻 How

🔬 Testing

Important review notes and deviations

Uh oh!

CLAassistant commented Sep 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot review overview

🟡 Changes recommended

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot review overview

🟡 Changes recommended

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot review overview

🟡 Changes recommended

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot review overview

🟡 Changes recommended

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot review overview

🔵 Needs a closer look

Uh oh!

cretz left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cretz Oct 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cretz Oct 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

marius-baseten commented Sep 30, 2026 •

edited by cretz

Loading

CLAassistant commented Sep 30, 2026 •

edited

Loading

cretz Oct 5, 2026 •

edited

Loading

cretz Oct 2, 2026 •

edited

Loading