Skip to content

Download · v0.21.1

A Git client for macOS that opens fast.

One universal build for Apple Silicon and Intel. The window is WKWebView, the one Safari uses, and the engine is Rust and libgit2 in the same process, so there is no daemon and no bundled browser.

It is not signed with an Apple developer certificate yet, so macOS asks once on first launch. Homebrew clears that flag for you, which is why it is the install I recommend.

Download for macOS AngKorGit_0.21.1_universal.dmg · Intel and Apple Silicon, one file

First launch

  1. 01 Open the .dmg and drag AngKorGit into Applications. Launch it from there, not from inside the dmg window, or macOS runs it from a temporary location where folder permissions cannot be saved.
  2. 02 On first launch macOS says the app cannot be opened. Close that, open System Settings, Privacy and Security, scroll down and click Open Anyway next to the AngKorGit line. That happens once.
  3. 03 When you open a repository under Desktop, Documents or Downloads, macOS asks whether AngKorGit may read that folder. Allow, and it is remembered.

Homebrew

terminal
brew install --cask cheat2001/tap/angkorgit

From the terminal

macOS
curl -L https://github.com/cheat2001/angkorgit/releases/download/v0.21.1/AngKorGit_0.21.1_universal.dmg -o ~/Downloads/AngKorGit.dmg
xattr -cr ~/Downloads/AngKorGit.dmg
open ~/Downloads/AngKorGit.dmg

What you get

AngKorGit showing a side by side diff with the commit graph behind it
The same interface on macOS as on every other platform.

Questions

Does it run natively on Apple Silicon?
Yes. The .dmg is a universal binary, so it runs native on M series and on Intel from the same file. Homebrew installs the same build.
Why does macOS warn me?
There is no paid Apple certificate on the build yet, so Gatekeeper asks once. The folder permissions you grant are remembered for that build, and an update asks for them once more. Every update is verified with a signature before it installs.
Does it work with the keys in ~/.ssh and the macOS keychain?
Yes. SSH remotes use your agent or the keys in ~/.ssh. HTTPS remotes use an account you add in Settings, Authentication, whose token is stored in the keychain, or fall back to the same git credential helper the command line uses.
Which macOS versions?
The build targets macOS 10.13 and later. I test on the current release and the one before it, so if you are on something older and hit a problem, open an issue.