Lazily mount a git repo without cloning it. Files materialize as they are read or edited.

git lazy-mount https://github.com/example/huge-repo ~/huge-repo

After it returns, your ordinary git and tools just work:

cd ~/huge-repo
vim src/main.rs
git commit -am 'Some edit'
git switch -c feature
git push

Why?

This is aimed at microVMs that spin up to run coding agents against a git repository. The idea is that the coding agent can start working immediately without having to wait for a full clone.

When the agent runs a test or build, only relevant files are downloaded on demand.

Grep tool in AI session

Tools like rg and git grep read every file, so they pull the whole repo and undo the point of lazy-mount.

To mititgate this, we can route search through sgrep instead. It queries a code-search index (Sourcegraph by default, and pluggable) and overlays your uncommitted edits, fetching nothing.

More in crates/sgrep.

Performance in real world

Measured cold in a Linux container, with one real claude prompt per repo:

Linux Only

Linux only: because almost all microVMs are Linux-based.

The whole stack (a transparent kernel-mounted working tree) is built on Linux FUSE (libfuse3, /dev/fuse).

Windows and macOS

Windows and macOS are not supported. The design notes and feasibility studies are kept under docs/future-platforms/ if we pick them up later.

Install / build

# Linux. Needs libfuse3 + the system git (>= 2.36).
cargo build --release -p glm-cli --features fuse   # produces `git-lazy-mount`

Docs

Everything is in docs/:

• Using it: compatibility (which git commands work, and how lazily) and limitations (what's deferred, and why).
• How it works: the architecture overview, then deep-dives into the worktree model, FUSE semantics, and object fetching.

License

MIT + Apache