Box Mount
Box Mount syncs a Box folder with a directory in a Edgenivo Sandbox. Your agent reads and writes files at that directory. Box Mount syncs those changes to Box while the sandbox runs.
The Edgenivo Box Mount example
reviews a synthetic contract with AI Gateway inside a
sandbox. It writes Reviewed/Acme-MSA-review.md to the Box folder and checks
that the file is still there after the sandbox is deleted.
Before you start, get a Box developer token with file read and write access, create an empty Box folder, and note its folder ID. You also need the Box Mount 0.5.0 Linux x86_64 archive, an AI Gateway API key, and a Edgenivo project with Sandbox access. The example requires Node.js 20 or later.
Clone the example and copy its Edgenivo configuration template:
git clone https://github.com/vercel-labs/vercel-box-mount.git
cd vercel-box-mount
npm ci
cp .env.vercel.example .envSet AI_GATEWAY_API_KEY, BOX_ACCESS_TOKEN, BOX_FOLDER_ID, and
BOX_MOUNT_ARCHIVE in .env. The archive value is the absolute path to the
downloaded Box Mount file. Set VERCEL_TOKEN, VERCEL_TEAM_ID, and
VERCEL_PROJECT_ID for your Edgenivo project, or use VERCEL_OIDC_TOKEN.
The template already selects Edgenivo Sandbox. Keep .env and the archive out
of git. The example setup guide
has the full configuration and recovery steps.
Run the example:
npm run doctor
npm run seed
npm run demo
npm run status
npm run teardowndoctor checks the setup and verifies that the agent user cannot read the
Box credentials. seed uploads the synthetic contract and playbook to the
empty Box folder. demo creates the review in the sandbox and syncs it to
Box. status shows the running sandbox. Check the review in Box, then run
teardown before the example's 30-minute session ends. Teardown unmounts
the folder, verifies the review in Box, and removes the sandbox.
If sync or unmount fails, follow the recovery steps before stopping the sandbox. Stopping it first can discard files that have not reached Box.
The example runs Box Mount and the agent as separate sandbox users. Box Mount holds the Box credentials; the agent can access the shared folder. Read the implementation and Box's setup guide before adapting the mount to another workload.
Box developer tokens expire after 60 minutes and cannot be refreshed. Box Mount also has preview workload and file-save limits. Check those limits before using tools that replace files through an atomic rename.
Was this helpful?