GitFuse is a Go CLI for developers who work across multiple machines and want to continue committed Git work without pushing temporary WIP branches. Commit on one device, run `gitfuse sync`, switch machines, and `gitfuse pull`. It only syncs committed Git state — uncommitted changes, untracked files, ignored files, and stashes stay local. The Free version is live on macOS, Linux, and Windows.
I built GitFuse after repeatedly running into the same Git workflow problem when switching between machines.
I’d have committed work locally that I wanted to continue somewhere else, but the branch wasn’t ready to be pushed yet. The usual workaround was to create a temporary WIP branch, push it just to move the commits, pull it on the other machine, and clean it up later.
GitFuse makes that workflow much simpler:
git commit → gitfuse sync → switch machines → gitfuse pull
It works specifically with committed Git state. Uncommitted changes, untracked files, ignored files, and stashes stay local, so GitFuse doesn’t try to become another general-purpose file sync tool.
The CLI is written in Go and runs across macOS, Linux, and Windows. GitFuse also includes trusted-device authorization and a dashboard for repositories, devices, sync history, usage, and account management.
The Free version is live now. Pro and Team plans are coming later with larger limits and additional workspace features.
The goal is simple: make it easier to continue committed Git work on another machine without creating remote branches purely to transport unfinished work.