Your private sandbox

A private, temporary workspace: your files, your project map and your edit history, invisible to every other user.

What is inside

• Your files: repositories you clone and files you create.
• Your project map: master_architect keeps its index of your code inside your sandbox, not in a shared database.
• Your edit state: read_file buffers, verification results and undo history live here too.
• 2 GB of storage: each sandbox is its own ZFS dataset with its own quota.

How long it lives

• It starts on your first tool call, not when you connect.
• Every tool call keeps it alive.
• After 10 minutes without activity, its files, project map and edit history are deleted.
• Your login stays valid for up to 30 days, so the next tool call gets a fresh, empty sandbox without signing in again.

What it cannot reach

• Anything outside the sandbox folder, including through symlinks.
• Private networks and this machine's own services: web_skeleton reaches public internet addresses only.
• Remote repositories for writing: git has no push.

Why temporary

A sandbox that empties itself needs no account, no storage plan and no cleanup policy, and it keeps 500 spots available for everyone who wants to try the tools.