What PwrGit is

PwrGit is a cross-platform desktop git client 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. There is no dependency on the version you have installed, and no separate credential setup — PwrGit uses git’s own credential helpers rather than storing tokens of its own.

The shape of the app is three panes. A sidebar listing every repository it has indexed, each expanding into its worktrees. 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.

What it is built around

• Worktrees are the unit of work, not branches. A repository expands into the worktrees checked out from it, and selecting one is what changes the graph, the changes list, and the sync buttons. You can create one for a local or remote branch, and PwrGit also finds worktrees you made in a terminal. See Worktrees.
• Profiles carry a commit identity. A profile is a workspace: its own repo folders, its own window, and its own commit email. Commits apply that email per-invocation, so PwrGit never rewrites a repository’s local user.email to do it. The commit box names the address it is about to use. See Profiles.
• Finding a repository is one shortcut. Command+K (or Ctrl+K) searches repositories, worktrees, branches and commits across every profile, not just the one in front of you. See Search.
• The graph draws fetched work, not just local work. A branch that is behind its upstream has commits in the object store that no local ref reaches. PwrGit walks those too and draws them dashed, so a branch that needs a pull looks different from one that is current. See History.
• Pull is fetch plus fast-forward. It is not a merge, and it will not create one. When the branch has actually diverged you get a dialog naming both sides and offering rebase or reset, rather than a merge commit you did not ask for. See Sync.
• Pull and merge request status, from the CLI you already use. PwrGit reads GitHub through gh and GitLab through glab — whichever you are already signed in to. It never asks for a password and never stores a token. See Forges.

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 then runs it against a throwaway copy of the worktree first. You approve the plan only after that dry run reports whether it applies cleanly.

Nothing leaves the machine as a result: a rebase rewrites local history, and pushing it is still a separate, explicit step. See Squash and reorder.

Get started

• Install — macOS and Windows builds, first launch, update trains, uninstall.
• Repositories — profiles, repo folders, the sidebar, lenses, search, clone, fork, remotes.
• Worktrees — creating them, finding the ones worth pruning, removing them.
• History — the lineage graph, branch chips, commit details, the diff pane.
• Changes — staging, committing under the right identity, amend, discard, squash and reorder.
• Sync — fetch, pull, push, divergence recovery, Git LFS, the Logs window.
• Forges — connecting GitHub and GitLab, what each one supports.
• Settings — every pane, its default, and when you would change it.

PwrGit is a PwrDrvr product; the marketing site is at pwrgit.com. 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.