Skip to main content
A workspace describes itself to an agent in two Markdown files, in the VFS.md format:
  • VFS.md: every mounted path, its layout and which Unix commands work there.
  • SKILL.md: the registered CLIs, with each one’s help.
Both are built from the live workspace and follow 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.

Get them

  • 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

  • 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, which of them use the service’s own search, and the path’s own commands, such as chroma-query on Chroma.
  • 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; Custom VFS lists them.