ClaimFS is literally just an instant file system in the cloud for AI agents.

• Create a writable cloud filesystem in one command.
• No account required for anonymous filesystems.
• Anonymous filesystems last 24 hours and are limited to 250 MB.
• Authenticated filesystems are permanent and have higher launch limits.
• Agents can use the CLI, HTTP API, exec endpoint, or local native mount.

Install the ClaimFS skill so your agent knows how to create, mount, share, and clean up filesystems automatically.

npx skills add financialvice/claimfs --skill claimfs -g

For repo-pinned or project-local installs, run the same command without -g.

If the skill installer is unavailable, use the fallback CLI installer:

curl -fsSL https://claimfs.com/install.sh | bash

Once installed, agents can claim a filesystem, write files, mount it locally, and hand scoped workspaces to other agents.

Create and use an anonymous filesystem. No account needed.

claimfs create "Agent workspace"

# Save the one-time accessToken and claimToken printed by create.
claimfs write <slug> /hello.txt "hello world" --grant <accessToken>
claimfs read <slug> /hello.txt --grant <accessToken>
claimfs mount <slug> ./workspace --grant <accessToken>

Anonymous creates return one-time secrets. Save them immediately; ClaimFS cannot show them again.

ClaimFS has two modes: anonymous and authenticated.

• Anonymous: omit Authorization. Use the returned accessToken as a grant token.
• Authenticated: run claimfs login <email> to get an account API key.
• Grant tokens go in --grant <token> for CLI commands.
• HTTP grant tokens go in X-ClaimFS-Grant: <token>.
• Only account API keys go in Authorization: Bearer <CLAIMFS_API_KEY>.

claimfs login user@example.com
claimfs create "Permanent workspace"

# Preserve an anonymous filesystem:
claimfs claim <slug> <claimToken>

Create via CLI or API. The response includes the slug, filesystem metadata, one-time secrets, and ready-to-run commands.

claimfs create "Research workspace"

curl -sS https://claimfs.com/api/v1/filesystems \
  -H "content-type: application/json" \
  -d '{"name":"Research workspace"}'

Anonymous filesystems include accessToken, claimToken, claimUrl, and expiresAt. Authenticated filesystems do not expire.

Use the CLI for common file operations, or the /files endpoint for direct API access.

claimfs write <slug> /notes/today.txt "ship it" --grant <accessToken>
claimfs read <slug> /notes/today.txt --grant <accessToken>
claimfs files <slug> / --recursive --grant <accessToken>
claimfs mkdir <slug> /drafts --grant <accessToken>
claimfs mv <slug> /notes/today.txt /drafts/today.txt --grant <accessToken>
claimfs rm <slug> /drafts/today.txt --grant <accessToken>

curl -sS -X PUT "https://claimfs.com/api/v1/filesystems/<slug>/files" \
  -H "X-ClaimFS-Grant: <accessToken>" \
  -H "content-type: application/json" \
  -d '{"path":"/hello.txt","content":"hello world\n","encoding":"text"}'

Exec runs shell commands against the filesystem and checks out the selected working directory by default, so file changes persist.

claimfs exec <slug> --grant <accessToken> --workspace /agents/claude -- "mkdir -p docs && echo hi > docs/hello.txt"

• Use relative paths inside exec commands.
• Use --workspace <path> to give an agent its own directory.
• Use --no-checkout only for intentional read-only sandbox commands.
• Absolute shell paths refer to the sandbox host unless you use $CLAIMFS_ROOT or /mnt/archil.

Native mounts are core to ClaimFS. Anonymous filesystems can be mounted at launch.

claimfs doctor
claimfs mount <slug> ./workspace --grant <accessToken>
# edit files normally
claimfs unmount ./workspace

Mounts are shared by default so many agents can work in the same filesystem. Use per-agent workspaces for normal collaboration.

Use agent workspaces when multiple agents need to work in one filesystem. Each workspace is a normal directory plus a scoped grant.

claimfs agent join <slug> claude --agent-id claude --grant <accessToken>
claimfs agent join <slug> codex --agent-id codex --grant <accessToken>

Direct grants are available when you want to share a specific path or capability set.

claimfs grant <slug> "reviewers" --path-scope /shared/review --grant <accessToken>

Grant defaults are intentionally agent-useful: read, write, mount, and exec. Pass explicit capabilities only when you want narrower access.

Agents can submit optional product feedback when ClaimFS blocks progress or behaves unexpectedly.

claimfs feedback <slug> "exec path behavior was surprising" \
  --category confusing \
  --severity low \
  --trying-to-do "write a generated file from exec" \
  --tried "used an absolute path, then retried relative" \
  --tool cli \
  --grant <accessToken>

Never submit secrets, personal data, proprietary source snippets, raw chat transcripts, customer data, or other sensitive information.

• /agent.md is the terse agent guide.
• /llms.txt is the full LLM-facing reference.
• /openapi.json is the API contract.
• /api/commands is CLI metadata for agents.
• /.well-known/agent.json advertises machine-readable entrypoints.