A vendor-neutral specification for exposing any data source to AI agents as a filesystem-shaped interface.
Read the spec → · Build a provider → · Governance → · AEPs →
LLM agents are converging on filesystems as their primary interface for
exploring information. The same ls, cat, grep, find skills the
model learned from code work equally well for docs, tickets,
transcripts, and agent state.
Several teams have built essentially the same thing in isolation — Mintlify's ChromaFs, Supabase's supabase.sh, Turso's AgentFS — with slightly different shapes and no interoperability.
AFI is the shared shape. Any store — SQLite, vector DB, object store, HTTP API — can implement AFI and become a provider that any AFI-aware agent can talk to.
| Path | Contents |
|---|---|
docs/specification/ |
The normative specification (draft) |
docs/community/ |
Governance, contributor ladder, AEP process |
docs/providers/ |
Adapter notes for existing systems |
docs/aeps/ |
AFI Enhancement Proposals |
mkdocs.yml |
MkDocs Material site configuration |
.github/workflows/ |
Docs deploy + CI |
Everything is served as a searchable site at ucalyptus.github.io/afi.
- I want to add AFI support to my product → Build a provider
- I'm building an agent that consumes AFI → Build a client
- I want to understand the design → Learn
- I want to propose a change → AEP guidelines
v0.1 draft. The specification, four transport bindings, and conformance profiles are drafted and searchable at the docs site above.
Already published:
- Draft specification, four transport bindings, conformance profiles
- Adapter sketches — AgentFS, ChromaFs, supabase.sh, Cloudflare D1
Remaining v1.0 gate criteria (all 5 must be true):
- ⏳ Two or more independent conforming implementations exist across two or more organizations
- ⏳ At least one implementation is not maintained by AFI core (or by any organization that has held a core-maintainer seat in the past six months)
- ⏳ Conformance test kit is at v1.0 and both implementations pass all scenarios at the level they declare
- ⏳ A neutral home has been identified and accepted the project
- ⏳ No accepted AEP proposing breaking changes is still open
Read CONTRIBUTING.md and the
contributor ladder.
Substantive changes ship via AFI Enhancement Proposals.
Please read the Code of Conduct — we're serious about a welcoming project.
- CSI (Container Storage Interface) — the model of "an interface, not an implementation"
- LSP (Language Server Protocol) — proof that a small, well-scoped interface can outlive its originating vendor
- MCP (Model Context Protocol) — the transport AFI happily rides
- 9P / FUSE / POSIX — the mental model everyone already shares
- Specification and reference code: Apache License 2.0
- Documentation prose (
docs/non-normative pages): CC BY 4.0
To report a security issue, please use the private security advisory process. See SECURITY.md for the full policy.