Skip to main content
The Sixb logo mark and wordmark inside the boxd card. Sixb is a TypeScript framework for apps and AI built on one model of your business data. Its agents run commands and work with files in a sandbox, and Sixb lets you pick the sandbox provider. @sixb/sandboxes-boxd makes that sandbox a boxd machine. Each agent run gets a fresh machine that is deleted after the run. A conversation that keeps its files gets one machine per thread, which hibernates between runs with its memory and disk. The provider is part of Sixb (pull request), and Sixb’s docs list it with its sandbox providers.
The provider is merged into Sixb’s main branch and is not on npm yet. It ships with Sixb’s next release. Until then, use it from a checkout of sixb-ai/sixb.

Set up

1

Install the provider

In a Sixb project, with Bun 1.4.2 or later:
2

Create an API key

.env.local
Machines are created and billed in the key’s organization. The factory reads BOXD_API_KEY when you don’t pass apiKey.
3

Add the factory to Sixb

sandbox.ts
Pass it as sandboxes to createSixb in sixb.config.ts, next to your existing storage and models.
4

Make the Sixb API reachable

Commands in the machine call your Sixb API server, so the API needs a public HTTPS URL. For local development, start a tunnel to the API port and pass its origin:
The agent worker adds that origin to the machine’s network, installs the Sixb CLI in it, and destroys the machine after the run.

Use a machine directly

The factory also works outside an agent run:

Keep a workspace between runs

A named sandbox is one machine. stop() hibernates it with its memory and disk, and resume() wakes it with its files, installed packages and running processes:
Sixb’s conversation sandbox bindings use this to keep a thread’s workspace between runs. destroy() deletes the machine for good. The machine is labelled sixb-sandbox=<name>.

Network

New machines reach nothing, DNS included, until you allow it:
The machine runs remotely, so loopback and private addresses are refused. Allow a public origin instead.

Configuration

create() and resume() can override workingDirectory, env, network and timeout.

What each machine gets

  • Isolation: every machine is isolated, with no route to your other machines and no boxd credentials inside.
  • An unprivileged command user: commands run as UID 65534 without sudo, so setup can’t install system packages. Put them in a snapshot and pass snapshot.
  • Credentials the commands can’t read: the run token for the Sixb API sits in a root-only file in the machine, and a forwarder adds it to requests to the API.
  • The default image: Ubuntu 24.04 with Bun, Node, Python, Git and curl.
  • Cleanup: call destroy() for ephemeral work. A machine left behind hibernates after its idle timeout and stays until you delete it, so set labels to find your workers’ machines.

Read more