Bug

[email protected] ships with SANDBOX_AGENT_INSTALL_SCRIPT still pointing to 0.3.x:

// dist/chunk-TWTMX66J.js (published 0.4.0)
var SANDBOX_AGENT_INSTALL_SCRIPT = "https://releases.rivet.dev/sandbox-agent/0.3.x/install.sh";

Source: src/providers/shared.ts

This affects the e2b and vercel providers — they install 0.3.x server inside the sandbox but the SDK client speaks 0.4.0 ACP protocol, causing:

AcpRpcError: Internal agent error: Internal error
  code: -32603

Expected

export const SANDBOX_AGENT_INSTALL_SCRIPT = "https://releases.rivet.dev/sandbox-agent/0.4.x/install.sh";

The 0.4.x install URL exists and works: curl -sI https://releases.rivet.dev/sandbox-agent/0.4.x/install.sh returns 200.

Workaround

Custom provider that uses the correct install URL:

await sandbox.commands.run('curl -fsSL https://releases.rivet.dev/sandbox-agent/0.4.x/install.sh | sh');

Environment

• SDK: [email protected]
• CLI: @sandbox-agent/[email protected]
• Provider: e2b
• Runtime: Node.js 24