Skip to content
agentvfs ★ GitHub
beginner 10 minutes

Give an agent an isolated vault and run a command

This is the core loop: give the agent a task-scoped vault, run one command through the boundary, and inspect the structured result. Nothing touches your host filesystem.

  1. 1

    Fork a task vault

    Clone a base vault into a task workspace in milliseconds so the task is isolated.

    avfs vault fork demo task-1
  2. 2

    Run a command through the boundary

    proxy exec classifies the command, mounts the vault as a real directory, runs it, and returns a structured envelope.

    avfs proxy exec --vault task-1 --json -- git status
  3. 3

    Read the result

    The ExecutionEnvelope carries stdout, stderr, exit code, duration, the policy decision, and a ChangeSummary of files touched. Branch your agent logic on it.

Why standard tools just work

  • ▸The vault mounts over FUSE as an ordinary directory, so git, cargo, npm, and python run unchanged inside the boundary.
  • ▸There is no syscall shimming and no special agent SDK to learn — you call one CLI and parse JSON.

More guides in the index, or read the architecture to see what the boundary is doing.