Skip to main content
The RAM VFS exposes an in-memory filesystem mounted at some prefix such as /data/. All data lives in process memory and is lost on exit. No setup or credentials required.

Config

RAMVFS() needs no configuration object. RAMVFS(capacity="100MB") caps the bytes the store holds; a write past it fails with “Disk quota exceeded”. See capacity.

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 <cmd> or <cmd> --help for one command’s usage.
The RAM filesystem starts empty. Files and directories are created on demand via commands like touch, mkdir, tee, cp, etc.
Paths are normalized with a leading /. The root directory / always exists.

Cache

The RAM VFS uses IndexCacheStore with index_ttl = 0, so its listings are not cached: the data is in memory, and every listing reads it. A workspace or mount index: block still applies its ttl to this mount.

Integration

What RAM answers through its own API, so fewer files are read. Integration explains each command.

Example

Shell Commands

The RAM VFS supports the full set of shell commands since it handles real file content (text, binary, JSON, CSV, etc.):

Read Commands

Text Processing

File Operations

Path Utilities

Compression

Encoding

Use Cases

  • Testing: Fast filesystem for unit tests without I/O
  • Staging: Temporary data area during pipelines
  • Prototyping: Develop against a filesystem before switching to S3/disk
  • Caching: In-process data exchange between commands
  • Ephemeral workspaces: Create, process, discard - no cleanup needed