Gitfox 4.3.1 fix

Gitfox is a native macOS Git client that puts repositories, history, staging, commits, and hosted service accounts in one AppKit-style app instead of juggling terminal commands and browser tabs.

What it does on Mac

You manage local and remote repos from a repository manager, review inline diffs with line-level staging, resolve conflicts in the diff view, and commit with syntax-aware messages and multiple identities. History views cover branch logs, graphs, tags, stashes, reflogs, blame, bisect, interactive rebase, and Git Flow actions. Gitfox integrates with GitHub, GitLab (cloud and self-managed), Bitbucket, and Gitea for cloning and account management, and supports external diff/merge tools when you use builds outside the Mac App Store sandbox limits.

Typical workflow

A common Mac flow opens a repo, scans changes in the sidebar, stages hunks or lines, writes a commit, and pushes from the same window—or uses Quick Actions (⌘P) and keyboard navigation to stay off the mouse. Notifications can alert you to new commits on tracked remotes. The App Store build is free with optional Gitfox Pro subscriptions (about $7.99/month or $49.99/year on the listing); Setapp also distributes Gitfox on some plans. The current App Store release requires macOS 26.0 or later.

Version 4.3.1 (fix)

Build 4.3.1 is a maintenance release in the 4.3 line. Apple’s What’s New text adds a small blame-view enhancement (open the blamed commit from the line popover) and focuses on fixes: selection double-click crashes, ISO8601 timestamp parsing crashes, stray text selection in the editor, changes-view flicker, SIGPIPE crashes, excessive refresh churn from filesystem events, and branch outline refs clearing after a failed refresh. Larger 4.2.x features such as whitespace diff controls are documented in earlier App Store notes, not re-listed here.