Skip to main content
SmolFS gives an AI agent a folder it can come back to later. Your agent can write files, stop, and then open the same workspace again from another process.
SmolFS is early. These docs cover the first stable path and keep the surface small while the project evolves.

​
What you can do

Keep work across runs

Save files in a workspace folder and reopen them after the agent process exits.

Try it locally

Start with a local --dev volume before connecting shared storage.

Use one command flow

Check the machine, create a workspace, open it, save changes, and close it from the CLI.

Wrap it in agent code

Use Python or TypeScript when your agent runner should manage the workspace directly.

​
Core idea

A SmolFS volume is a named workspace. Mounting a volume makes that workspace appear as a normal local folder. After your code writes files there, you can flush important changes, unmount the folder, and mount it again later. For the first release, start with local development volumes: 
smolfs init demo --dev
smolfs mount demo ./workspace
Cloud-backed volumes are available, but they are intentionally documented lightly for now. Use them when you are ready to provide explicit metadata and object storage settings.

​
Start here

Installation

Install the CLI, check your machine, and add an SDK if you need one.

Quickstart

Create a local workspace, write a file, close it, and open it again.
Last modified on June 24, 2026