Skip to main content
The RAM VFS exposes an in-memory filesystem mounted at a path prefix such as /data/. All files live in process memory and are discarded when the process exits. Available across Node, browser, and edge runtimes via @struktoai/mirage-node and @struktoai/mirage-browser. No setup or credentials required. For Python, see the RAM (Python) documentation.

Config

RAMVFS() requires no configuration object.

VFS.md

The VFS.md an agent reads with RAM mounted at /<path>.

Virtual Filesystem

Supported Unix Commands for VFS

Unix commands work on each path as on a local filesystem, as far as the path supports them:

Limitations of Unix Commands for VFS

Where a path differs from a local filesystem:Run man to list every command, and man <cmd> or <cmd> --help for one command’s usage.
The RAM filesystem starts empty. Files and directories are created on demand via shell commands such as touch, mkdir, tee, and cp. Paths are normalized with a leading /. The root directory / always exists.

Cache

The RAM VFS does not cache directory listings (index_ttl = 0): because data resides entirely in memory, every listing reads the live tree directly without network latency. A workspace or mount index: configuration still applies its ttl if specified.

Integration

Commands like find, du, ls -R, and tree execute directly in-process via a single recursive tree traversal.

Example