Skip to main content
The Dify VFS exposes completed Dify Knowledge documents as text files mounted at a prefix such as /knowledge/. Each file is assembled from the document’s completed, enabled segments. For API key setup and dataset creation, see Dify Setup. For Python, see the Dify (Python) documentation.

Config

The VFS is read-only. Snapshots redact credentials, so Workspace.load needs a live DifyVFS in its third argument for /knowledge/ (e.g. Workspace.load(snapshot, {}, { '/knowledge/': freshDifyVfs })). Restored cache entries are served as saved and un-cached reads reach the live backend. Fields marked secret are redacted in snapshots.

VFS.md

The VFS.md an agent reads with Dify mounted at /<path>.

Virtual Filesystem

/<path> layout

Supported Unix Commands for VFS

Unix commands work on each path as on a local filesystem, as far as the path supports them:

Limitations of Unix Commands for VFS

Where a path differs from a local filesystem:Run man to list every command, and man <cmd> or <cmd> --help for one command’s usage.

Document metadata and paths

Mirage mounts documents using a slug metadata field when present (defaulting to slug), falling back to the document name. Adding a slug metadata field to your Dify Knowledge dataset allows you to organize virtual paths into a clean nested directory structure:

Example