Any sandbox, one filesystem.
A persistent filesystem shared across sandboxes, sessions, and handoffs — so work survives when an agent stops and the next one picks up where it left off. FUSE-mount it locally, semantic-grep it with vector and BM25 in parallel, and grant secrets per agent from a built-in vault.
One drive for authorized agent environments.
Use the same drive from environments with the appropriate owner or delegated credentials.
Copy files with sys9 drive fs cp, or mount a remote path with
sys9 drive mount. Files remain in the drive across agent sessions; local
mount behavior depends on the supported FUSE backend and its caching.
# choose an unused context name, then explicitly select it $ sys9 drive create --name example-files $ sys9 drive ctx use example-files # confirm the filesystem is ready before continuing $ sys9 drive fs ls /
Creation can return while provisioning continues. If listing reports provisioning, retry sys9 drive fs ls / later. Continue only after it succeeds; stop if it reports provisioning failed. Selecting a context does not wait for readiness.
# after listing succeeds, use an existing local file $ sys9 drive fs cp ./report.md :/notes/report.md # optional: mount with the supported local FUSE backend $ sys9 drive mount --mode=fuse :/notes ~/drive9-notes
Search by meaning. Grant secrets per agent.
sys9 drive fs grep combines vector, BM25, and keyword search to find relevant files.
Results contain file paths, with relevance scores when available. The built-in vault
stores credentials and issues scoped grants with an explicit permission and lifetime.
Import a delegated context to use a grant without sharing the owner key.
# search returns file paths, with scores when available $ sys9 drive fs grep "pricing strategy" / # create a vault entry; replace YOUR_SERVICE_TOKEN $ sys9 drive vault set example SERVICE_TOKEN=YOUR_SERVICE_TOKEN # issue a scoped, time-limited grant for an agent $ sys9 drive vault grant --agent assistant --perm read --ttl 1h example
Write once. Read anywhere. Search by meaning.
drive9 is the shared memory of files that agents pass between each other.
One drive, every sandbox
Create a drive with an unused name, select its owner context with sys9 drive ctx use NAME, and wait until sys9 drive fs ls / succeeds. Configure authorized owner or delegated contexts in the environments that need access to the same files.
Local over FUSE
Mount a remote path with sys9 drive mount --mode=fuse on a host with a supported FUSE backend. The default auto mode uses WebDAV on macOS and Windows. A mount uses the context selected when it starts; remount after switching contexts.
Grep by meaning
Search by meaning, then read the matching file. Grant agents the required vault entries with a permission and expiry; keep owner credentials separate.
The filesystem under your agent stack.
Pair drive9 with compute, data, memory, and observability — one agent-native stack.
Sandboxes
Configure drive access in the Linux environments that need shared files.
run9 → db9Postgres
Structured data alongside your shared files.
db9 → mem9Memory
Memory for agents; drive9 for the files they share.
mem9 → owl9Session records
Inspect file-related tool activity recorded in collected agent transcripts.
owl9 →Give your agents one filesystem.
Install the sys9 CLI, create a drive, and keep the owner credentials it saves. Follow the drive9 guide for delegated access, mounts, and vault setup.