Nicheloom visits: 63,141 all-time · 8,415 in the last 7 days

The opportunity tracker for new startups.

Today: 1,441 launches · Niche of the day: digital marketing agency services · See what launched today →

Git-lazy-mount mount a repo without cloning it. Works with ordinary Git

Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.

Want to reach these readers? Sponsor an issue.

Hello!This is an attempt to make google3 style repo clones work with Git. In a HN thread a few days ago the idea sparked for me.It can be super useful for very large repos that need to be cloned for AI coding sessions that might only need a subset of files to accomplish something.Similar to google3, files appear to be there and can be read and edited but they are only fetched when they are needed.It works with normal Git commands so there is no need for a new CLI.On huge catch is, running grep will force fetch all files that grep glob matches. AI coding sessions run the Grep tool quite often. To mitigate this, git-lazy-mount comes with sgrep that offloads grepping to a remote code search engine like SourceGraph.With this, microVMs that run AI sessions can stay lean and start up much faster.I am guessing this is probably faster than baking in the git repo in the image but I have not measured performance of it yet. It is definitely useful if the microVM is spun up with unknown repositories (something like Claude on web).Curious to hear your thoughts and criticismThanks!

HN · launched Jun 26, 2026 · 9 upvotes (top 45%) · 0 views

Niche: git management and workflow tools · 227 launches, 12 in the last 7 days ▼ -8% · Explore this niche →

Category and tags

  • Horizontal
  • Dev tools
  • Developer
  • Not AI
  • Hobby / open-source project

Visit website ↗ Source listing ↗

Could you build this?

No Virtualizing a Git repository via partial lazy mounting mimics enterprise systems like Google's GVFS/EdenFS, requiring deep virtual filesystem (FUSE/VFS) and low-level Git protocol/packfile internals.

What it would actually take: This requires a user-space file system (FUSE or Windows Projected File System) integrated with Git's partial clone and sparse-checkout protocols. The daemon intercepts filesystem read calls, parses remote Git tree objects and commit packs on demand, and populates files lazily with smart caching. Building it requires deep knowledge of OS kernel filesystem interfaces, low-level C/Rust systems programming, and internal Git object storage formats.

Discussion

3 comments analyzed.

Competitors mentioned: git worktrees, sgrep code search backend

Concerns raised: single machine performance compared to worktrees, private repo configuration complexity, unclear applicability to language porting use case

Feature requests: smooth worktree initialization tooling, cloud/multi-VM scaling documentation, language porting workflow support

Competitors

Other products that read as similar to this one : 333 launches clear the similarity bar, closest 8 shown.

Attention rank: #131 of 334 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 239 days after the earliest competitor.

  • GWZ · hn · 2026-07-15 · 5 upvotes · similarity 0.52
  • RepoFlock · ph · 2026-09-15 · 2 upvotes · similarity 0.48
  • GiTRay · ph · 2026-11-13 · 1 upvotes · similarity 0.48
  • Commitdog · hn · 2026-03-02 · 5 upvotes · similarity 0.47
  • I built a tool to manage work and personal Git repos · hn · 2026-03-07 · 6 upvotes · similarity 0.47
  • Gat · hn · 2026-09-27 · 7 upvotes · similarity 0.47
  • FinderGit · ph · 2026-10-16 · 61 upvotes · similarity 0.47
  • skipper · github · 2026-09-22 · 19 upvotes · similarity 0.46

The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.