Four read tools over a real filesystem, hosted.
Fast enough to call in a loop, scoped to one tenant, logged end to end.
No sandbox to provision before the first read
Reads hit a hot, per-workspace index. Nothing to boot, nothing to mount, no first-call penalty.
Read the quickstartPer-session tokens, scoped to one tenant
What a token cannot reach is absent from every listing, glob, and grep hit, not denied.
How access control worksEvery read on an append-only audit log
Which token, which verb, which argument, and what came back. Filter it or export it.
See the audit APIThe four unix verbs agents already know
ls, find, cat, grep. No query language, no schema, no framework glue.
A filesystem beats a vector database for agent retrieval.
+16.7 points over naive RAG across an 18,340-file corpus, graded blind.
Agent filesystem beats naive RAG on retrieval accuracy
97.9% of held-out questions answered correctly, 16.7 points ahead of naive RAG. Here is how we ran it.
Everyone is building a filesystem for their agent
Mintlify, Anthropic, and Turso each built one independently. Here is why the same primitive keeps reappearing.
A TypeScript SDK that drops into your agent loop.
Four read tools over the /v1 API, ready to hand to the Vercel AI SDK.
├─ policies/ │ ├─ returns.md grep "refund" ×3 │ └─ privacy.md ├─ support/ │ └─ faq.md cat └─ contracts/ └─ msa.md find **/*.md
Give your agents a filesystem.
Create a workspace, push your files, and your agents can ls, find, cat, and grep in minutes. Free to start.