Some major new features are coming very soon to Tower Pro: a revamped Pull Request area, smarter merge detection, and real, AI-supported code reviews.
Together, these features reshape how you work with pull requests and reviews in Tower; from creating a PR, to checking your own code before you push it, to keeping your branch list clean once everything's merged.
Allow us to walk you through them.
☝️ All three of the features below are expected to land in Beta this Summer, so if you would like to be among the first to try them out, make sure to join our Beta Channel.
Please note that all screenshots and feature details shown here reflect work in progress and may change before the final version ships.
1. A Revamped Pull Request Area
Pull requests sit at the heart of most modern Git workflows, and we're giving Tower's PR area the attention it deserves. Our goal is simple: to allow you to manage the entire lifecycle of a pull request without constantly switching back to your provider's web UI.
You'll be able to search across closed and merged pull requests (not just open ones), and use quick filters like "review requested of me", "authored by me", or "draft" so you always land on what's actionable. Checked-out PR branches get their own dedicated sidebar section, making it easy to spot what's lingering after a merge and clean it up.
Creating a PR gets easier too, with draft PR support and AI-generated descriptions that respect your repository's PULL_REQUEST_TEMPLATE.md. And once a PR exists, you'll manage reviewers, assignees, labels, and milestones right from Tower, see the full event timeline, enjoy GitHub-quality markdown rendering, and spot merge conflicts before they become a problem.
As part of this, reviewing changes and performing formal code reviews will become an essential and well-integrated part of Tower – as we will explore below.
In short, the PR area is becoming a place where you can actually live: fewer browser tabs, fewer context switches, and a workflow that finally feels at home inside Tower.
2. Improved Fully Merged Detection
Tower already flags branches that have been fully merged, so you know which ones are safe to delete. The problem is that the classic detection method only understands standard and fast-forward merges — it misses squash and rebase merges entirely, which happen to be the most common strategies on GitHub, GitLab, and Bitbucket.
We're fixing that by adding PR-based detection: Tower will check your hosting service for merged pull requests, which is definitive proof that a branch was integrated, no matter which merge strategy was used.
Best of all, the old single "Merged" boolean is being replaced with a transparent, expandable checklist that tells you why a branch was flagged — for example, "Merged via PR #66 into release" with a direct link to the PR. And when detection gets something wrong, you'll have an easy escape hatch to dismiss the hint for a specific branch.
The result is a branch list you can finally trust, with the reasoning laid out in plain sight instead of hidden behind a single badge.
3. Code Reviews (AI-Supported and Manual)
This is the one we're most excited about. Tower is gaining a dedicated code review experience — for reviews you run on your own work before pushing it, and for reviewing pull requests as a proper, first-class review. You'll be able to review your working copy or any revision range in a focused review window.
Findings are organized by severity, each accompanied by a clear explanation, file references, and proposed changes that you can accept or decline:
- Must Fix: A critical issue (bug or security vulnerability) that must be addressed.
- Should Fix: An issue worth addressing but not strictly blocking progress.
- Nit: Minor suggestions for improvement; take it or leave it.
Accept what you like, hit "Apply", and the changes land in your working copy.
The reviews are AI-supported, but always opt-in — the manual flow is right there alongside it. And when reviewing pull requests, your feedback is submitted through the provider's review API as a genuine review (Approve / Request changes / Comment), so it shows up just like any other reviewer's. This works across all major services, including GitHub, GitLab, and Bitbucket, as well as self-hosted options like Gitea and Forgejo/Codeberg.
It's a way to catch issues before your teammates do — on your terms, with as much or as little AI assistance as you want.
Further Out
There are a couple more features we're excited to share, though they'll arrive a little later than the three above — we expect both late this summer or in the autumn.
Stacked Branches Improvements
We're planning to improve Tower's Stacked Branches support. Working with a stack is great until it's time to merge: right now, merging a stacked branch is the piece that's been missing. We want to change that with a dedicated flow that properly merges a stacked branch, deletes it, and restacks its children so the stack never breaks.
We're also looking at refreshing an entire stack in one action — pulling in new commits and restacking everything for you.
Sync Branches Improvements
Updating a branch from its parent is already one of Tower's most-loved features — and we're taking it a step further.
Sync Branches will show you at a glance which branches need updating and let you sync several of them at once, including pulling in remote changes. Keeping your branches in line with their parents will be a breeze regardless of the circumstances.
Final Words
Three big features, one focused mission: making Tower Pro for Mac the best place to create, review, and ship your work. We expect all of them to reach Beta this Summer.
As always, we'll be listening closely to your feedback once these features land in betas and releases. Don't forget to join our Beta channel to be the first in line.
Thank you for being part of our journey!
