Tower – Git client for Mac and Windows
Build Better Software
Start new thread

Tower 18 for Mac - The most powerful Git client with a better CLI experience

by
•
Tower 18 for Mac is here! This update is all about improving the Tower experience in the terminal: the Tower Command Line Tool can now take you straight to any view in Tower (History, Blame, the Working Copy, Branches Review, and more) with a single command.

Add a comment

Replies

Best
Maker

Thanks for hunting Tower 18, !

Hi everyone, I’m Bruno from the Tower team. This release is all about improving Tower’s Command Line Tool, so that you can jump from the terminal straight to the right view in Tower for any task.

Here's a 5-minute video to quickly bring you up to speed:

We’ve also put together an Agent Skill, so that your AI agent knows all the new commands at your disposal.

In my day-to-day, two things stand out:

  • Reviewing your agent’s work. When the agent finishes a task, it offers to open the Working Copy in Tower, so you can go through every changed file in a proper diff view before anything gets committed.

  • Seeing what’s unique to a branch. The agent can record which branch its work started from, and Tower then shows the Fork Point in History. This is useful for pinpointing a branch's unique commits before merging.

There are plenty of other commands, but these two have already changed how I work with agents.

Would love to hear what you think! 😊

Congrats Bruno and the Tower team on launch number 15. Jumping from the terminal straight into Working Copy to review what an agent just changed fixes the review step I tend to skip. Does the Agent Skill let the agent open Tower on its own when it finishes a task, or does it only teach the agent the commands so I still trigger the view myself?

Maker

 Thanks for the kind words, Gene!

You can tell the agent that you'd like it to review every change in Tower from that moment forward, and it will do just that. Sometimes, if you ask a couple of times, it will simply add that task to its routine for the remainder of that conversation.

Typing a blame in the terminal and then hunting the same line down in the GUI has always felt silly, so one command that jumps straight into the History or Blame view is a small thing I will use daily.

Maker

 Glad to hear, Kareem! I find myself using the History command very often in my day-to-day tasks 😎