Runtime Manual/Agent & Advanced/In-Memory Virtual Filesystem Sandbox

In-Memory Virtual Filesystem Sandbox

Deterministic Copy-On-Write (COW) in-memory filesystem for safely executing untrusted AI Agent code with zero host disk mutation

1. Why an In-Memory Virtual Filesystem?

Executing untrusted AI-generated scripts or autonomous Agent workflows frequently entails:

  • Writing dynamic configuration and temporary artifacts;
  • Creating, modifying, or unlinking project files;
  • Risking accidental data corruption or pollution of host directories.

Traditional sandboxes like Docker or Firecracker microVMs suffer from:

  • High Startup Overhead: 500ms to several seconds cold boot, impeding sub-millisecond agent execution;
  • Resource Heaviness: Demands container daemons, root privileges, and storage layers;
  • Cluttered Teardown: Requires explicit cleanup scripts to avoid orphan files on disk.

Amber v1.3.0 provides a thread-safe, high-performance Virtual Filesystem (VFS) sandbox:

  • Pure In-Memory Storage: Writes and mutations occur in RAM with zero host disk side-effects;
  • Copy-On-Write (COW): Allows reading base host files transparently while isolating all writes;
  • Strict Mode: --virtual-fs-strict cuts off host read fallbacks for a completely blank in-memory workspace;
  • Instant Reset & Snapshot: Export JSON filesystem snapshots or reset state in less than 1 microsecond.

2. CLI Usage

Enable with CLI flags on any command without code changes:

code
# 1. Enable standard Copy-On-Write (COW) Virtual Filesystem
amber run --virtual-fs ./untrusted_script.js
amber eval --virtual-fs "require('fs').writeFileSync('/etc/secret.txt', 'test'); console.log('Isolated!')"

# 2. Enable strict pure-RAM mode (disables host read fallback)
amber run --virtual-fs --virtual-fs-strict ./agent_task.ts

# 3. Combine with full permission sandbox
amber run --sandbox --virtual-fs ./agent.js

3. JavaScript / TypeScript API (amber:vfs)

Control the virtual filesystem lifecycle programmatically:

code
import fs from 'fs';
import * as vfs from 'amber:vfs';

// 1. Inspect status
console.log("VFS Enabled:", vfs.isEnabled());
console.log("COW Mode:", vfs.isCow());

// 2. Enable dynamically in code
vfs.enable(true);

// 3. Standard Node.js fs APIs transparently route to memory
fs.writeFileSync('/workspace/output.txt', 'Agent generated summary');
console.log("File exists:", fs.existsSync('/workspace/output.txt')); // true
console.log("Content:", fs.readFileSync('/workspace/output.txt', 'utf8'));

// 4. List virtualized files
console.log("Files in RAM:", vfs.listFiles());

// 5. Export JSON snapshot
const snapshot = vfs.snapshot();
console.log("Snapshot files:", snapshot.files);

// 6. Reset or disable
vfs.reset();
vfs.disable();

4. Security & Performance Comparison

MetricTraditional Docker / VMAmber --virtual-fs
Host Disk SafetyRelies on mount isolation100% in-memory; zero physical mutation
Startup Latency500ms – 3000ms< 0.001ms instantaneous
Teardown Cleanuprm -rf / volume cleanupAuto-freed on isolate teardown
Snapshot SpeedDisk image / git commitvfs.snapshot() instant JSON export