Shared project storage

Use the /project folder for files you want to read and update from several devboxes, such as reference material or notes for another agent. Every machine in the project — its Template box, if it has one, and each devbox — opens the same stored files rather than a copy synchronized onto each machine. Project storage is on by default during open beta.

Project storage connects the shared /project folder to the project's machines. Select the image to enlarge it.

Choose appropriate files

Ask your agent to save a handoff note under /project, or write a file there yourself from a machine's Terminal. You or an agent on another devbox in the same project can then read that file without copying it between machines. For example, an agent finishing an investigation on one devbox can leave /project/findings.md for the agent that will implement the fix on another.

Anyone or any software able to operate one of the project's machines can read and change the files in /project. Sharing an agent transcript with a teammate does not, by itself, give them machine or storage access.

Keep source repositories in the normal devbox filesystem and Git. Project storage is not intended for databases, package caches, logs, queues, build trees, or other files that many processes change rapidly.

Machines see each other's writes with a short delay: an update can take about a second to appear on another machine. Avoid having several agents or processes write to the same file at once — simultaneous writes can fail or conflict — and don't put software there that depends on local-disk latency, file locks, strict cache consistency, or atomic appends from several writers.

Share Claude's project memory

When project storage is connected, boxes.dev directs Claude's automatic project memory to /project/.claude/memory, so a memory Claude saves on one devbox can inform its work on the project's other machines. Claude's own settings still take precedence: if you've turned off Claude's automatic memory or set an explicit memory directory, Claude will follow that setting instead. If storage is turned off or unavailable, Claude returns to its normal local memory behavior.

Codex can read and write ordinary files under /project, but boxes.dev does not move Codex's state or transcripts there.

Understand persistence

Files in /project outlive the machines that use them. They survive machine sleep and reset, and they survive destroying or replacing a devbox: destroying deletes that machine's own files, while the shared stored files remain. A Template box snapshot doesn't copy or replace them either — a new devbox created from the snapshot will reconnect to the same storage before it's ready to use.

The storage belongs to the project, so deleting the project will delete its project storage with it. During open beta, keep another copy of files you cannot recreate.

Turn storage off or on

Open Project settings → Project storage in the desktop app. Turning storage off will disconnect /project from the project's machines without deleting the stored files; turning it back on will reconnect the same storage. While storage is disconnected or unavailable, boxes.dev does not create a replacement /project folder on the machines.