DigitalOcean managed agents run in cloud sandboxes that you can pause when idle and resume when needed. 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.
Before you begin
On the Box side, you need:
- Access to the Box Mount developer preview, including the 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
This demo mounts a Box deal room folder in a DigitalOcean sandbox session, runs an agent that summarizes the files into an acquisition memo, and syncs the memo back to Box. A Box webhook then prompts the agent to update the memo whenever someone uploads a new file to the folder.
How the demo works
- In DigitalOcean, the demo creates an environment and a sandbox session with the Harness Runtime.
- Over SSH, the demo switches to a separate Unix user for Box Mount and mounts the folder with
box-mount mount "/mnt/box" "<box-id>". Running Box Mount as its own user follows Secure your credentials.
- The agent reads the files in
/mnt/box, follows a workflow file stored in the folder, and writes the memo to the mount. Box Mount syncs the memo back to Box.
- A Box webhook fires when someone uploads a file to the folder. Box and DigitalOcean use different webhook signatures, so a small relay function verifies the Box event and signs it for a DigitalOcean trigger, which prompts the agent to regenerate the memo.
Next steps
Last modified on November 5, 2026
