Definition: A Virtual File System (VFS) is an abstraction that exposes a unified file-and-directory tree on top of underlying storage. The Taskade VFS is the shared workspace backend that Taskade EVE, AI agents, and bash-backed tools all read and write inside Taskade Genesis apps and Space Agents.
Why a Virtual File System Matters in 2026
AI agents fail when each tool keeps its own copy of state. The agent edits a doc, the bash sandbox edits a config, the automation reads a stale snapshot, and the result is conflicts. A shared VFS removes that failure mode. Every actor reads and writes the same tree, so an agent that creates a project file can hand it to a bash command, which can hand it to an automation, with no serialization layer in between. That is what makes the Taskade bash sandbox and custom bash commands safe to use inside production Genesis apps.
How the Taskade VFS Works
- Unified namespace. Every Project, file, and folder appears at a path EVE and agents can address.
- Shared mount across actors. EVE, Taskade AI agents, bash tools, and automations all see the same tree at the same time.
- Workspace-scoped permissions. Reads and writes respect the workspace RBAC tier (Owner, Maintainer, Editor, Commenter, Collaborator, Participant, Viewer).
- Live diffs. When EVE writes a file, Taskade EVE Memory and the project view both update in real time.
Connection to Taskade
The VFS is the substrate underneath every Taskade Genesis app. When EVE generates an app, the resulting Projects, files, and configuration land in the VFS. When an agent runs a custom bash command, the command runs against the same tree. When the MCP server accepts an edit_space call from Claude or Cursor, it routes through the VFS as well, which is why external clients see workspace state instantly.