Gitork

Gitork is a desktop Git client for one person with too many machines and the same repositories on all of them. GitKraken is the obvious reference; the point of Gitork is where it goes the other way.

Small on the machine. Nothing to install but Gitork. Your secrets stay where you keep them.

Three rules it is built around

• Small on the machine. Memory is a budget, measured in the test suite, not a hope. A release build idling at its home screen sits around 200 MB across the whole process tree -- GitKraken's gigabytes are the anti-model.
• Nothing to install but Gitork. libgit2 and libssh2 are compiled in. It runs on a machine with no git and no ssh, and no feature may quietly start depending on one.
• Secrets stay where you keep them. Gitork stores where your credentials live -- a key file's path, "use my agent" -- and reads them when an operation needs them. A passphrase typed into a prompt lives for that one operation and is dropped. Nothing secret reaches a config file, a log, or a cache.

Profiles, because one key per customer

A profile carries an SSH key (or your agent), a commit identity, and the repositories that belong to it; a project inside a profile, or a single repository, can override the key. Switching customers is no longer ssh-add -D && ssh-add -- the right key is whichever profile the repository sits under.

What is built

A home screen with every repository grouped by profile and project, each row showing uncommitted work, commits to push, commits to pull, branches never pushed, and how long ago anything happened; Refresh at any level fetches everything under it and says what came in. A repository view with branches, a commit graph laid out in Rust and drawn only where visible, commit details and diffs, and a working-changes panel to stage and commit. All of it on demand: no file watchers, no polling, ever.

Where it is going

Merge with a three-pane conflict picker is designed and next. After it, Warboss: a small server of your own that your Gitorks report to, so from any one machine you can see every repository's state on every other machine -- and hand your work over from the one you are leaving to the one you are sitting down at. One person's fleet, not a team tool.

Where it stands today

Linux is where it is built and tested, through both a mocked backend and the real binary; Windows and macOS are untested so far. Apache-2.0; the name and the Gk tile stay ours.