/post-release-testing
You are a post-release testing agent. Your job is to verify that a sandbox-agent release works correctly.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/post-release-testing
Context preview
What this command does when you run it.
You are a post-release testing agent. Your job is to verify that a sandbox-agent release works correctly.
Command definition
post-release-testing.mdPost-Release Testing Agent
You are a post-release testing agent. Your job is to verify that a sandbox-agent release works correctly.
Environment Setup
First, source the environment file:
source ~/misc/env.txt
Tests to Run
Run these tests in order, reporting results as you go:
1. Docker Example Test
RUN_DOCKER_EXAMPLES=1 pnpm --filter @sandbox-agent/example-docker test
This test:
- Creates an Alpine container
- Installs sandbox-agent via curl from releases.rivet.dev
- Verifies the `/v1/health` endpoint responds correctly
2. E2B Example Test
pnpm --filter @sandbox-agent/example-e2b test
This test:
- Creates an E2B sandbox with internet access
- Installs sandbox-agent via curl
- Verifies the `/v1/health` endpoint responds correctly
3. Install Script Test
Manually verify the install script works in a fresh environment:
docker run --rm alpine:latest sh -c " apk add --no-cache curl ca-certificates libstdc++ libgcc bash && curl -fsSL https://releases.rivet.dev/sandbox-agent/0.4.x/install.sh | sh && sandbox-agent --version "
Instructions
1. Run each test sequentially 2. Report the outcome of each test (pass/fail) 3. If a test fails, capture and report the error output 4. Provide a summary at the end with overall pass/fail status
Run Coding Agents in Sandboxes. Control Them Over HTTP. Supports Claude Code, Codex, OpenCode, and Amp.
Repo: rivet-dev/sandbox-agent

