Technology1 min read

Box Mount now runs in Vercel Sandbox

By · Published by Everything Blog

In short

The integration links a specific Box folder directly to a directory inside the execution environment, allowing agents to read and write files natively. To ensure that newly generated or modified files are safely retained in Box after the sandbox is deleted, users must unmount the directory prior to shutdown. Furthermore, an example implementation uses AI Gateway to review a synthetic contract and push the finished document straight back to cloud storage. The tool is currently restricted to a private preview requiring an access request.

Key points

  • Files generated or modified by agents are preserved only if the directory is unmounted be…: Files generated or modified by agents are preserved only if the directory is unmounted before shutdown.
  • Sensitive Box credentials stay isolated from the primary workspace to protect cloud acces…: Sensitive Box credentials stay isolated from the primary workspace to protect cloud access.
  • Access is restricted to a private preview that requires direct approval from Box.: Access is restricted to a private preview that requires direct approval from Box.

Sources checked by our analysis pipeline: 1

Box Mount lets agents running in Vercel Sandbox read and write Box files through standard filesystem operations. It syncs a Box folder with a directory inside the sandbox. Unmount before you stop the sandbox, and everything the agent wrote is in Box after the sandbox is deleted.

The contract-review example uses AI Gateway to review a synthetic contract in Vercel Sandbox and save the review back to Box. The sync process and agent run as separate sandbox users, keeping the Box credentials separate from the agent's workspace.

Box Mount is in private preview. Request access from Box, then follow the Box Mount documentation to set it up in Vercel Sandbox.

Original source: vercel.com

Technology