Skip to main content
VFS.md lists every mounted path, its layout and which Unix commands work there, in the VFS.md format. It is built from the live workspace and follows the session’s profile: a command the profile denies, or a path it hides, is never mentioned. Each VFS page shows its VFS.md, such as Gmail. The CLIs are in SKILL.md.

Get it

  • No session or profile: what the workspace’s default profile allows.
  • A session: what that session’s agent sees.
  • A profile: a preview of what a session with that profile would see.
  • A path: the file appears in the workspace, read-only and always current, so the agent runs cat /VFS.md. Each session reads its own version.

What VFS.md says about each path

  • VFS: its name, for a VFS with its own layout or its own search, such as Google Drive. Plain files, on s3 or ram for example, show only the mode: which VFS holds them changes nothing an agent does.
  • Mode: read, write or exec. A path whose VFS cannot change files shows read, whatever mode it is mounted with.
  • Layout: how its files are organized and what they hold, for a VFS that has one. A VFS sets it with vfs_md.
  • Supported commands: the Unix commands that work there, and which of them ask the service which files may match. CLIs such as gh are in SKILL.md, not here.
  • Limitations: where it differs from a local filesystem, such as being read only, or the walk_limit on large folders.
Which commands can change files depends on the methods the VFS implements; Adding a New VFS lists them.