A deleted file is a poor place to discover that your agent's workspace was connected to everyone else's. DigitalOcean's new Cuttlefish app puts an approval screen on an iPhone. Its Box integration makes the other half of that story harder to ignore: the files an agent changes can be the files a team actually uses.

DigitalOcean announced Cuttlefish on November 5 as a mobile companion to Managed Agents. People can follow sessions, inspect a command, file path or diff, and approve or deny tool calls. Requests classified as high risk require Face ID or a passcode. That is useful control. It is not evidence that every risky consequence will be recognized before it happens.

The folder is a working copy, not a prop

The launch pairs the app with Box Mount, which synchronizes a chosen Box folder into a Managed Agents environment. DigitalOcean says edits upload to Box, changes in Box return to the workspace, and deletions sync back too. Each person connects their own Box account, preserving that account's permissions, version history and audit trail.

That makes a small pilot folder a better starting point than a department's whole document library. This is our recommendation, not a restriction the launch automatically applies. A user who can edit a file may still want the agent to leave it alone.

Box's developer documentation supplies an important qualification to the reassuring phrase "version history": atomic save is not supported. An application that writes a temporary file and renames it over the original can cause the replacement to sync as a new file, losing the original file's Box version history. Ordinary-looking save behavior can therefore change the recovery story.

The same documentation says simultaneous edits are preserved as a new Box version or a separate conflict copy. Preserving both results is better than silently overwriting one. It still leaves someone to decide which result belongs in the final document.

A checkpoint needs an external check

Cuttlefish can pause or stop sessions and lets people create checkpoints, fork and roll back, according to DigitalOcean. Its Managed Agents product page describes checkpointing and forking a session into an independent session. Neither statement establishes that rolling back a session also reverses changes already synchronized to Box.

Before relying on recovery, demonstrate both sides with disposable content: restore the agent's workspace, then inspect the actual Box file, its identity and its versions. Check that a deleted file has the expected recovery path. A reassuring state inside the session is not sufficient evidence about the shared destination.

This is a proposed evaluation, not a test we ran. We have not installed Cuttlefish, joined the Box Mount preview or measured synchronization and rollback behavior.

Availability has three different answers

The joint launch announcement says Cuttlefish is available on the App Store for Managed Agents customers. Managed Agents is in public preview. Box Mount for Managed Agents is in private preview. The release also says the preview services are not supported for production workloads and may change or be discontinued. App availability does not make the whole workflow production-ready.

Box's explanation of the architecture is equally worth reading: the sandbox contains a synchronized working copy, and developers remain responsible for its local data and security. Existing Box governance does not remove that separate responsibility.

The useful promise is less time stranded at a desk waiting to approve work. The useful question is what that approval changes outside the phone. Start with a small folder, inspect the proposed action, and verify the shared result. The app can move the decision into your pocket. It cannot make the consequences smaller.

Reporting note: This is a documentation-led reading of the November 5 launch and current Box guidance, not a product review. Investing.com's coverage also reports the launch but is explicitly based on the press release, not an independent test.