Docker Sandboxes gives you an isolated microVM with its own filesystem and tools, managed through the sbx CLI. Box Mount runs inside the sandbox and maps a Box folder to a standard POSIX path, so your agent works with ordinary file operations while Box remains the system of record.
This demo mounts a Box folder in a Docker Sandbox, runs an agent that reviews a contract against an approved legal playbook, and syncs the review memo back to Box.
Before you begin
On the Box side, you need:
- Access to the Box Mount developer preview, including the Linux Box Mount binary. To request access, complete the Box Mount developer preview form.
- A Box app configured for OAuth 2.0 or JWT. See Configure credentials.
- The ID of the Box folder you want to mount. This is the number at the end of the folder URL on Box.
Demo video
Set up Box Mount in Docker Sandboxes
The demo has its own requirements, in addition to the Box Mount prerequisites:
- A Box developer token. See Use a developer token.
- A new, empty Box folder.
- An Ubuntu 24.04 or later host with KVM available and a sudo-capable account.
- Node.js 20 or later and npm.
- An OpenAI API key for the demo agent.
Follow the Box Mount contract review with Docker Sandboxes README. It covers installing Docker Sandboxes, building a sandbox template that includes the Box Mount binary, registering credentials with the sandbox credential proxy, and running, inspecting, and tearing down the demo.
Developer tokens expire after 60 minutes, and you can’t refresh them. When the token expires, update it and recreate the sandbox.
Next steps
Last modified on November 5, 2026
