Git Tower 16
This update introduces Automatic Branch Management, making it easier than ever to keep your repository tidy and clutter-free. We’ve also added significant improvements to the “History” view for better visualization of your work 😎
Tower 16 for Mac is now in beta, and it introduces AI Commits, allowing you to generate commit messages and descriptions with the help of AI directly from your favorite Git client.
Every year there are lots of new features, but it still seems to me that they’re ignoring the basics:
Why can you not search the contents of files/changes?
When I drag and drop a file that’s in one my repositories into Tower, why does it offer to create a new repository instead of showing me that file’s history?
When viewing a file’s history, why is there no way to see the full commit message without copying the SHA-1, switching to a different view, pasting it into the search field, and changing the menu to search by Commit Hashes? This should just take one click or perhaps a hover.
Tower v15.0 got a new liquid glass icon but unfortunately, like some Apple-made icons early in the beta season, it looks blurry in the Dock.
Previously:
Update (2026-05-05): Bruno Brito:
The commit message body field can now be kept always visible — toggle this in Preferences.
Yay!
9 Comments RSS · Twitter · Mastodon
Nothing against Git Tower per se, but I've been quite happy with Sublime Merge for a long time. It also pairs well with Sublime Text, which is still my favorite lite text editor.
> why is there no way to see the full commit message without copying the SHA-1, switching to a different view, pasting it into the search field, and changing the menu to search by Commit Hashes
Yes, why?? Also I believe in some cases the hash is not even selectable/copyable.
I just tried it… and compared to GitKraken much nicer UI and has some good capabilities, but:
- rebase doesn’t “just work” - in GitKraken, it is so easy. Built in diff is so great. Also the rebase broke and I was unable to get out of it; only GitKraken helped me to abort and then rebased without issues
- cannot stage a file just by touching the keyboard
The issue is, these two are a dealbreaker to me, needed for basic flows. I might also add Tower into my workflow, but I can never replace GitKraken until they improve upon this.
You stage by pressing space. If space opens quicklook for you, there is a setting to change it to stage/unstage.
Have you tried Fork? I find it quite wonderful. Super intuitive, and very fast. A few years ago I really tried to like Tower but it completely baffled me.
@gildarts I love how fast Sublime Merge is, but I just found the interface kind of weird from a Mac perspective. I would probably like it a lot better if I were using their text editor. I actually do sometimes use it as a secondary Git client because it can do content searching.
@Fred I definitely remember having to retype some hashes that weren’t selectable, but when I tried to reproduce that before writing this I couldn’t find those places. Maybe they fixed them?
@Jim Fork would probably be my second choice after Tower. It’s competent overall and has some features that Tower doesn’t, but in general I did not find the user interface to be as intuitive or smooth. Tower is just so frictionless for staging files and individual lines and entering the commit message. I do like that Fork uses separate windows more, e.g. for per-file history, but then it’s missing some basics like being able to search in the history window. Crucially, it doesn’t address any of the Tower limitations that I mentioned in the original post: there’s no content search, no dragging in files to see history, and no viewing commit messages from within the file history. Is does let you open a file’s history from the command-line tool, which Tower doesn’t.
@Michael: That is fair, I was using Sublime Text before I was using macOS and spend most of my professional life on Windows, so it working the same on both platforms is more valuable to me than being super native feeling on macOS.
Thanks for spreading the word about the latest Tower release, Michael — as always, it's much appreciated!
And thanks for sharing a few features you'd like us to tackle next. From your list, the first one is definitely the most-requested of the three, but it's still up against a lot of other feedback we're working through.
Being a small team means we're always making tough calls on what to tackle next — but really appreciate you raising it, and I've already made sure the team hears it.
I use SourceTree. Probably doesn't have all of GitTower's features but it's free and good enough for me.