Faster checkouts.A fraction of the disk space.

git-dedup.ben3d.ca · 2026-10-01 · by Long Nguyen ·generic
git-dedup shares one copy of Git history across all your clones, worktrees, and submodules. Checkouts are 6x faster and use 70% less disk.

Faster checkouts.A fraction of the disk space.

6x

Faster checkouts

Repeat clones, worktrees, and submodules reuse history already on disk. Large checkouts drop from over a minute to about 10 seconds.

70%

Less disk space

Every checkout shares one copy of Git history. Across 117 checkouts, Git data dropped from 35.5 GB to 11.1 GB.

0

Changes to your workflow

Checkouts are normal Git repositories. Use git, your editor, and your agents exactly as before.

WHY I BUILT IT

My agents were waiting on Git.

Then my disk filled up.

I run fleets of coding agents, each in its own checkout. Every task started by cloning repositories and submodules from scratch, so agents sat idle waiting on downloads. Then I started running out of disk space, because every checkout held another full copy of the same history. git-dedup fixed both: my agents start dramatically faster, and I got 24 GB of disk back.

BUILT ON GIT

Dogfooded daily.

git-dedup uses Git's own alternates mechanism, so every checkout stays an ordinary repository with its real origin. We have spent a lot of time running it across our own agent fleets and repositories to make it robust and fast. Worktrees, submodules, forks, and existing checkouts all just work.

Read the getting started guide →

↗

REMOTEgithub.com/you/project

↓

◆

\~/.git-dedupone shared copy of history

shared

↙↓↘

agent Aagent Bagent C

Every checkout borrows from the same store.

Keep \~/.git-dedup.Your checkouts read their history from the shared store. Deleting it breaks every repository using it.Read about the store →

git-dedup.ben3d.ca · 1 images · 9 links

Comments (0)

No comments yet