FILESYSTEM.md
A standardized, interoperable spec for Agent-Native Filesystems.
Think of FILESYSTEM.md as a README for agents: a dedicated, predictable place to define how AI coding agents interact with your project's filesystem.
# ANF workspace (minimal)
├── FILESYSTEM.md # MUST
├── AGENTS.md # SHOULD
├── TOOLS.md
├── SECURITY.md
├── SKILLS/
├── PROJECTS/
├── MEMORY/
│ ├── daily/
│ ├── observations/
│ └── learned/
└── LOGS/
Start Here
Everything you need to evaluate, adopt, and contribute to FILESYSTEM.md.
Manifesto
Read the full Agent-Native Filesystem specification for humans and AI agents.
For Agents
Executable bootstrap, operations, memory, skills, and safety procedures for coding agents.
Build
Implement virtual FS, tool layers, sandboxes, and composite backends under FILESYSTEM.md.
Infra
Linux VFS/FUSE, EFS-like cloud filesystems, and mountable storage patterns.
Getting Started
Set up a project with deterministic bootstrap, memory layers, and skill loading.
Why Filesystems
See why Amplify, Vercel, Box, and LangChain converge on filesystem context — and where FILESYSTEM.md fits.
FAQ
Get answers to common implementation and interoperability questions.
Showcase
Explore real projects using agent-native filesystem patterns in production.
Community and Contribution
Learn how to propose changes, submit examples, and shape the spec.
Why FILESYSTEM.md?
The filesystem is the most natural abstraction layer for agentic systems. Rather than building complex memory APIs, leverage what LLMs already understand. Read why the industry is converging on this pattern →