LoonFS is a fully-featured cloud drive built on object storage. Give Claude Code, AI apps, and sandbox environments a real shared filesystem—with history, predictable sync, and links you can safely share.
Use LoonFS from a CLI, an internal tool, or a sandbox platform. Give agents a shared workspace with history, and give your product a durable filesystem abstraction instead of a temp directory.
import loonfs
# Open a versioned namespace for an agent workflow
ns = loonfs.open_namespace("customer-support")
# Read shared context, then write new output
brief = ns.read_text("/briefs/today.md")
ns.write_text("/handoff/reply.md", draft_reply(brief))
# Publish a new revision and keep history intact
rev = ns.commit(message="claude: drafted reply")
# Create a short-lived link for a human reviewer
link = ns.share(
"/handoff/reply.md",
expires_in="24h"
)
# Sync only the remote changes you have not seen yet
changes = ns.changes(after_seq=last_seen_seq)Every change lands in an ordered namespace history. Restore old revisions without overwriting the present, and give agents a drive with real memory.
Start with a great CLI. Layer in APIs, SDKs, and agent tooling as you need them. LoonFS is designed for people, scripts, and sandboxes at the same time.
Publish files and folders to teammates or outside reviewers with identity-based access and short-lived links. Exact-revision sharing fits review and handoff workflows.
If you run sandboxes, background agents, or internal AI systems, LoonFS gives you a durable shared drive on top of object storage with shared hot caches for repeated workloads.
LoonFS stores durable data in object storage and exposes a shared drive on top: namespaces, revisions, sync, and shareable links. It is built for AI-native teams and platform builders that need agent-friendly filesystems, not just another mounted folder.
Hot-cache warming improvements and bug fixes for concurrent namespace access under high read throughput.
Shareable links, revision history, and the new sync engine for real-time multi-agent collaboration on shared namespaces.
Object storage backend, namespace isolation, and the CLI for local development and sandbox environments.
loon init, loon sync, loon statusBefore mounting volumes, initialize the LoonFS kernel. Use the CLI to generate your local manifest and set up sync credentials.
Open source for self-hosting and early product work. Managed cloud and BYOC are the natural next steps for teams that want share links, org controls, and faster repeated reads.
For self-hosting, internal prototypes, and product teams that want to build on LoonFS directly.
Hosted namespaces, share links, and a simpler control plane for AI-native internal teams.
Customer-owned object storage, private networking, and a deployment model built for regulated environments.