Quickstart
Zero to a mounted workspace with an agent working in it, in five minutes: create and mount, point your agent at durable storage.
Give your coding agent a filesystem that survives its sandbox. In the next five minutes you'll mount a workspace at /mnt/work and point an agent at durable storage. No object-store SDK, and no changes to the agent's code.
Building a platform that provisions isolated storage for your own customers (sandbox runtimes, agent platforms)? Start with Quickstart for platform users instead.
Prerequisites: a Linux x86_64 host to mount on (sandbox VM, EC2, Fly machine, dev box). No Linux box handy? Any throwaway cloud VM works. macOS can't mount in v0.
1. Sign up and authenticate
Register or sign in at user.tonbo.dev with GitHub or Google.
# Install the CLI:
curl -fsSL https://artifacts.tonbo.dev/install.sh | bash
# Then sign in via browser OAuth (GitHub or Google):
artifacts login
On a host that can't open a browser (CI, a sandbox shell), use an API key instead; see Log in.
2. Create a workspace and mount it
A workspace is the shared filesystem your agent works in. Think of it as a network drive for your agents: it exists independently of any machine, and any Linux host you authorize can mount it, several at the same time. Pick any name you like; these docs use my-workspace as the example name throughout.
One command creates the workspace and mounts it:
# "my-workspace" is the workspace name; /mnt/work is where it appears.
artifacts workspace create my-workspace /mnt/work
What you should see:
Creating workspace my-workspace (provisioning storage credentials)…
Formatting workspace my-workspace…
Activating workspace my-workspace…
Workspace my-workspace is active.
Mounting /mnt/work ...
The prompt returns and the mount stays up in the background. Verify it with mount | grep /mnt/work.
For runtime-specific setup, see Mount on Linux, Mount in Kubernetes, or Mount in a container.
3. Point your agent at it
/mnt/work is a regular directory, so an agent uses it natively. Nothing in its code or tools changes.
cd /mnt/work && claude # or opencode, codex — anything that works on files
# Try: "Look around this directory, then write notes/findings.md
# describing what you see."import fs from 'node:fs/promises';
// Persist whatever your agent should remember across runs.
await fs.mkdir('/mnt/work/memory', { recursive: true });
await fs.writeFile('/mnt/work/memory/run-001.md', '# Notes from run 001\n');Every read, glob, and grep -r the agent runs now goes through the workspace. The agent doesn't need to know Tonbo Artifacts exists.
Next steps
Turn step 3 into a production loop: sandbox boot scripts and a memory contract for your agent.
Share files across machinesMount the same workspace from a second machine; the files are already there.
Quickstart for platform usersProvision isolated storage for your own customers: tenants, runtimes, grants, and mount tickets.
Bring your own bucketKeep file data in your own S3 bucket; Tonbo never sees the credentials.