literally just an instant file system in the cloud

that you can send to any agents they can read/write from and mount to super easily
- Tyler Angert

get started · 2 stepsworks on macOS arm64 + linux
1Tell your agent to set up ClaimFS
2It gets a writable cloud filesystem at <slug>, no account needed
works with every agent
OpenClawClaude CodeCodexCursorOpenCode
U40HERO
filesystems live
000,000,000
U36STAT
use cases · 4
fs.scratchSandbox scratch spaceGive a code-running agent a writable filesystem that survives between tool calls and across runs. Mount it once, delete the run.
fs.handoffMulti-agent handoffOne agent writes a plan to /plan.md, another reads it. No queues, no glue code — paths are the protocol.
fs.artifactArtifact storeRender PDFs, screenshots, and reports to a known URL the user (or another service) can fetch without an SDK.
fs.mirrorHuman-in-the-loopMount the same fs locally with FUSE; edit files in your editor while the agent watches for changes.
U28USES
protocol surface · talk to it however you want
httpPOST /api/v1/filesystems · /exec · /files · /grants
cliclaimfs create | exec | mount | read | write | grant
mountFUSE on linux · FSKit on macOS arm64
discovery/agent.md · /llms.txt · /.well-known/agent.json
U24PROTO
faq · 6
What is claimfs?
A POSIX-ish filesystem that exists at a URL. Claim one, get a token, mount it from any process — including agents. Reads and writes are durable, ordered, and shareable.
How do agents use it?
Drop the access token into the agent's environment. claimfs ships an HTTP API, a CLI, and a FUSE/FSKit mount. Agents read & write paths the same way they read & write local files.
Is it really instant?
Creating an anonymous filesystem is a single POST. You get back a slug, a one-time claim token, and an access token without setting up an account, project, or provisioning workflow first.
How do you handle concurrency?
Each path carries a monotonic version. After a local mounted write, remote API or exec readers should use a short retry window while the mounted filesystem publishes the change.
How long does an anonymous filesystem last?
Anonymous filesystems always last 24 hours and are limited to 250 MB. After `claimfs login <email>`, run `claimfs claim <slug> <claimToken>` to transfer it into that account and remove the expiration.
How do I share access?
Issue scoped grants with `claimfs grant <slug>`. By default, grants are useful for agents: read, write, exec, and mount. Add explicit capabilities only when you want narrower access.
U20FAQ