an instant filesystem · for AI agents, mostly

A filesystem at a URL.
For agents, mostly.

Claim one in 200ms. Mount it from any process. Read and write paths like local files — durable, ordered, shareable. No SDK, no console, no per-project setup. Drop the access token into your agent and go.

$claim a filesystem↵read the docs →open console

U40HERO

filesystems live14,208

ops · last 1m3.1k

p50 latency11ms

uptime · 30d99.99%

U36STAT

quickstart · 4 linesworks on macOS arm64 + linux

> curl -fsSL claimfs.com/install.sh | bash
> claimfs create "agent workspace"
  { slug: "fs-7k2n", accessToken: "cfs_••••", expiresAt: "+24h" }
> claimfs exec fs-7k2n -- "echo hi > /scratch/hello.txt"
> claimfs mount fs-7k2n ./workspace
  mounted · 24h ttl · 12ms rtt

anonymous by default · run claimfs login <email> to claim into your account and drop the TTL.

U32QSTART

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

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?

A claim is a single POST. You get back a slug, a one-time claim token, and an access token in under 200ms. No accounts, no projects, no provisioning step.

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?

You pick a TTL between 1 and 168 hours at create time (default 24h). Run `claimfs claim <slug> <claimToken>` to transfer it into your account and remove the expiration.

How do I share access?

Issue scoped grants with `claimfs grant <slug>` — pick a capability (read, write, mount, exec, delete, duplicate, admin), an optional path scope, and a TTL between 60s and 30 days.

U20FAQ

A filesystem at a URL.For agents, mostly.

A filesystem at a URL.
For agents, mostly.