drive9

Provide persistent network filesystem storage with natural-language search for AI agents.

85|12|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/mem9-ai/drive9 --skill drive9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drive9
Source: https://github.com/mem9-ai/drive9/tree/main/site
Command: npx skills add https://github.com/mem9-ai/drive9 --skill drive9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

drive9 lets you persist files across agent handoffs and session resets, so you can store outputs once and retrieve them later using natural-language search instead of brittle filenames or forgotten context.

Core Features & Use Cases

  • Persistent workspace storage: create isolated workspaces and keep credentials/config locally for repeat access.
  • Filesystem-like operations: upload, download, copy, move, and delete using familiar commands and remote paths (e.g. :/data/file.txt).
  • Hybrid semantic + keyword search: run grep for meaning-based retrieval and find for exact structural filters like tags, dates, and sizes.
  • Agent-ready mounts and zero-copy workflows: mount with FUSE for local tooling and perform metadata-only copies/renames for fast, space-efficient duplication.

Use case: store a set of project notes, datasets, and generated reports during an agent run, then later ask for “the pricing strategy draft” and retrieve the exact files even if you don’t remember the filename.

Quick Start

Ask your agent to install drive9, provision a workspace, and then search by meaning: run curl -fsSL https://drive9.ai/install.sh | sh && drive9 create && drive9 fs grep "pricing strategy" /.

Frequently Asked Questions about drive9

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve files using semantic search after an agent session resets?

Hybrid retrieval combines semantic search and keyword filters to locate files across projects. You run `grep` for meaning-based retrieval and `find` for exact structural filters like tags, dates, and sizes, allowing precise file discovery across directories.

How do I provision a persistent workspace for AI agents?

Workspace provisioning creates isolated storage for AI agents to keep credentials and config locally. You run `drive9 create` after installation to establish a persistent network filesystem, enabling repeat access to stored outputs across agent handoffs and session resets.

Can I mount a network filesystem with FUSE for local tooling?

Zero-copy linking performs metadata-only copies and renames for fast, space-efficient file duplication. Instead of moving actual file contents, it manipulates metadata within the network filesystem to rapidly duplicate or restructure files without consuming additional storage space.

What is the best way to store agent outputs across multiple projects?

Storing agent outputs across multiple projects requires a persistent network filesystem with hybrid semantic search. You upload files once using filesystem-style commands, then retrieve them later across projects and directories using natural-language queries instead of relying on exact filenames.

Do I need a root-name entry to discover files in a network filesystem?

A root-name entry is required for discovery in the network filesystem. It uses an SKILL.md entry to establish the root directory structure, enabling the semantic search and indexing mechanisms to properly locate and retrieve files across isolated workspaces.