A Git client for teams whose repositories are full of art assets, where the artists have to use it too — not just the engineers.
One repository, three ways to reach it.
Repositories and sections on the left, changes and the commit panel on the right. Made for a mouse and a big monitor.
Commit and update without leaving the engine. The panel keeps the same layout and skin as the app.
Scan a code and the phone takes over the local repository: history, branches, pull and push. Nothing to install.
Not another Git GUI. The parts that break most often in a team, and need someone watching them, were rebuilt.
Repositories full of art assets keep working: no random freezes, and no assets quietly turning into empty files.
When one change mixes assets and code, the tool splits it into groups for you instead of making you pick file by file.
Two machines on the same network can pull and push from each other. No server to set up first.
Scan a QR code and a phone browser can read history, switch branches, pull and push.
Type commands without leaving the window. Output stays readable and long tasks can be interrupted.
Commit and update from inside the Unreal editor instead of switching windows.
What shipped recently, newest first. The client follows its own updates, so there is nothing to babysit.
What is being built and what is planned. The order changes.
What changed in the last few months, and why it matters for a client like this one.
Seven engineers moved a ~100 GB monorepo onto an in-house system called Scion in five months. Merged changes went from about 2,500 a day in May to over 30,000 in September. The storage format survived; the client did not.
GitHub counts 34.3 billion commits this year, and the share of pull requests whose first draft came from a coding agent rose from 17% to 40% in roughly six months.
Jujutsu treats the working copy as a commit and conflicts as first-class, and it runs on ordinary Git repositories. Its creator now leads engineering at East River Source Control, building the server side of the same idea.
Origin puts hosting, cloud agents and stacked pull requests inside the editor, and the Graphite acquisition fills in stack-aware merge queues. Git stays the wire protocol; the review surface is what moved.
All four point the same way: a repository is no longer a folder you clone, it is a service you ask. The storage format survived; the weight moved to the client and the review surface. FGit sits on the client side of that line, and the parts it makes thick — large assets, the local network, the phone — are exactly the parts that stay local.