// the find
subramanya1997/markdownfs
A high-performance, in-memory virtual file system for Markdown files. Unix-like commands, Git-style versioning, content-addressable storage, and multi-user permissions — built in Rust.
markdownfs is an in-memory virtual filesystem that only stores Markdown files, built in Rust. It layers Unix-like file operations, Git-style commits, content-addressable storage, and multi-user permissions on top of a single concurrent core. The MCP server makes it a drop-in durable memory store for AI agents running in Cursor, Claude, or similar tools.
The architecture is disciplined — one MarkdownDb core shared across CLI, HTTP, and MCP transports means you're not maintaining three divergent implementations. The permissions model is unusually complete for a project this size: users, groups, chmod, chown, su, and adversarial test coverage to match. The content-addressable store gives you deduplication and cheap snapshots without the overhead of a full Git object model. Test coverage is genuine — 239 tests split across unit, integration, permissions, and perf suites, not just happy-path smoke tests.
The 102.8x speedup claim compares in-memory to native filesystem I/O, which is roughly measuring 'RAM is faster than disk' — not a meaningful benchmark for the use cases described. The whole-system snapshot VCS model (commit = snapshot of all files) won't scale past a few hundred files before revert and log become expensive; there's no path-scoped commits or staging area. The FUSE mount binary exists in the tree but isn't documented, which suggests it's either incomplete or broken — that's the one integration that would make this genuinely useful outside AI agent contexts. Markdown-only by design sounds clean until you need to store a config file or a generated artifact alongside your notes.