PwrGit
A desktop git client for people who keep hundreds of repositories.

What PwrGit is

These pages describe PwrGit 0.32.0 and later. The version you are running is in Settings → About and Settings → Updates.

PwrGit is a desktop git client for macOS, Windows and Linux, built around three things most clients treat as edge cases: worktrees, hundreds of repositories, and more than one commit identity on one machine.

It ships its own Git and Git LFS, so a fresh machine needs nothing else installed — and you can point it at your installed Git instead. It reads GitHub, GitLab and GitCafe through the CLI you already sign in with, and stores no forge token of its own.

The window is three panes. A sidebar listing every repository it has indexed, each expanding into its worktrees, pull requests, branches, tags and remotes. A lineage graph for whichever worktree you selected. A rail on the right holding that worktree’s changes, or the files of a commit you clicked.

The full PwrGit window. The sidebar, in the All lens, has openclaw expanded: a fork badge 2 behind upstream, main marked primary, and six worktrees with pull request chips, feat/token-miser selected with 1 uncommitted change. The lineage graph shows the fork's branches with PR chips and author avatars. The rail lists one unstaged file, extensions/token-miser/src/config.ts.
Repositories and their worktrees on the left, the lineage graph in the middle, that worktree's changes on the right.

The parts you will use every day

The request view for openclaw #166249, fix(comfy): report completed local workflows without outputs, by chelsealong from upstream, fix/codex-openclaw-166210 into main, 3 files, 1 commit. A line reads pull/166249/head, fetched from upstream holds 46c5361, above the diff. The rail lists the three files. The sidebar has the request selected under openclaw's pull requests.
A pull request read in place — files and commits — without checking out its branch.

What it is built around

Squash and reorder are checked before they run

Selecting commits in the graph and choosing Squash or Reorder builds a plan you can read — the pick/squash list, in the order it will execute — and runs it against a throwaway copy of the worktree first. You approve the plan only after that dry run reports whether it applies cleanly. This needs no agent and works with AI features off.

A rebase rewrites local history only; pushing it is still a separate, explicit step. See Squash and reorder.

Get started

PwrGit is a PwrDrvr product; the marketing site is at pwrgit.com and the source is pwrdrvr/PwrGit. The desktop app is MIT-licensed, and its license and third-party notices ship inside the app under Help → View License and Help → Third-Party Notices.