How it works
From install to mirrored, in seconds.
A walkthrough of the GitLove flow: what runs in Chrome, what runs on your machine, and what never leaves it.
Jump to setup guide →Chapter 01 — Workflow
Three steps.
Then forget it's there.
Your code never leaves your machine. The extension talks only to 127.0.0.1; the helper pushes directly to GitHub over your own SSH key.
Install once
Drop the Chrome extension into your browser and run the helper script on your machine. Five minutes, one time.
Open the side panel
Click the GitLove icon in Chrome. Pick the repo to copy from and where to copy it to — search your own repos or paste any GitHub URL.
Done in seconds
The helper streams every branch, tag, commit, and LFS object directly to your destination over SSH. No upload caps.
Side panel ──► Helper ──► GitHub
(just the (does the copy (source +
buttons) on your computer) destination)
╰──── nothing is uploaded to GitLove servers ────╯Chapter 02 — Capabilities
Built for the boring
parts of git.
No magic. No telemetry. No "AI-enhanced" anything. Just the boring, reliable plumbing for moving repositories from A to B.
No rate limits
Uses your local git over SSH. No API throttling, no upload caps, no per-file ceilings.
Full mirror
Every branch, every tag, every commit. The destination ends up identical to the source.
Large files supported
Repos with Git LFS files (over 100 MB) are copied too — turn it on with a checkbox when you need it.
One-click re-mirror
Your last 5 runs are saved with a Run again button — keep any mirror fresh in one click.
Type-to-filter
Got 100+ repos? Fuzzy search picks source and destination instantly, with favourites pinned on top.
Stays on your machine
Your code never touches our servers. The extension talks only to 127.0.0.1.
End of manuscript
Stop fighting
with rate limits.
Install GitLove once. Mirror any repo, any time. Your mirrors stay fresh, your code stays yours.