There are quite a few of those projects already I'm pretty sure, e.g. GitFS.
FUSE isn't new, but GitFS, EdenFS and VFS for Git solve a different problem: lazy fetching from a server. A checkout is cheap until something reads it - e.g agent trying to run rg over the whole tree. That problem is solved in gitfold.
Also gitfold does not need or try to change any existing git behavior, and is fully compatible with existing git binaries without any modifications.
So while used technology is the same, approach is from completely different angle.
> I recently created a project which utilizes FUSE to serve git files directly from object store without a checkout.
this for some reason gives me clearcase vibes...shudder.
Ha, fair: ClearCase dynamic views were a filesystem too. The difference is that nothing is remote and git stays the source of truth. And it's a single binary that runs without root, tiny next to a behemoth like ClearCase.
Re:Jujutsu Primer
by jauntywundrkind on Friday November 20, 2026 @06:57AM
(#50573497)
You made it much further with this effort than i did! https://github.com/rektide/jj-workfuse
I think in truth I 50% of the reason I made it was because I was mad about Anthropic inventing a whole new vcs after blaming git clone speed. I also knew artifact-fs exists, which works lazily to get data on demand, which is cool. https://github.com/cloudflare/artifact-fs https://news.ycombinator.com/item?id=47792374
I recently created a project which utilizes FUSE to serve git files directly from object store without a checkout. Main motivation was to sepeedup a worktrees creation (I work on a huge monorepo). In my case it helps a lot - now I wait a second instead of a minute. But then I realised there are other interesting features which having vfs opened:
- tree structure of related branches (simplest case of that are stacked PRs) which rebases itself
- live preview of merge state or any node of such tree
- on demand creation of a new branch which merges any of the existing ones very cheaply (e.g for a throwaway build check)
- quick and simple comand which shows conflicting files between selected worktree and all others
- agents gets notified about such conflicts when they happen
I was able to design it in a way so git sees those virtual workspaces as normal worktrees, and all git commands works exactly as you would expect. So I think for some people, especially on the very big repositpries, it might solve a few problems they try to solve with jj.
https://github.com/pkukielka/gitfold
A few typical use cases: https://github.com/pkukielka/gitfold/blob/main/docs/guide.md