The branch behind
your localhost.
Switch from a feature branch to a hotfix without losing track of what’s checked out. Pip shows the branch, commit and remote alongside the server running from that repository.
macOS + Windows. Pay once. Future updates included.
The right context for every project.
When several servers are running, the branch can tell you more than the port. Pip connects each server’s working directory to its repository and keeps that context close. Check the branch in the list, then open the details for its commit and remote.
- branch updates with each scan
- Live
- repository inspection
- Read only
- Git details beside each server
- In context
See what you have checked out.
Branch names sit alongside your projects. A detached HEAD shows its short commit hash, so you can recognise the state you’re working in.
Keep repository details close.
The server’s Git tab brings together its commit, origin remote and last fetch time, with badges for linked worktrees and submodules.
Carry on in your own workflow.
Pip reads repository metadata directly without writing to it. Switch branches using your usual tools and see the updated ref on the next scan.
Keep your bearings when you switch branches.
Read the Git guideRun a project from your repository.
Pip follows the server’s working directory to the repository root and reads its Git metadata.
Check the branch beside its port.
Find your server in the list, then open its Git tab when you need the commit or origin remote.
Switch branches and keep going.
Use Git as you normally would. Pip refreshes the displayed ref on each scan without needing a restart.
Git has a few states worth recognising.
A branch name is only one way a repository can identify your checkout. Pip keeps the other states visible too, alongside the server they belong to.
- Why do I see a commit hash instead of a branch?
- A short commit hash indicates a detached HEAD, which can happen when you check out a tag or specific commit, or during a rebase. If there’s no Git information at all, the server may be outside a repository. It can still appear in Pip through its runtime or development port.
- Does reading Git details change my repository?
- Pip follows the process’s working directory to the repository root and reads the Git metadata directly. It does not invoke the Git binary, spawn a shell, or write back to the repository for this inspection. The ref is read again on each scan, so changes made with your usual Git tools appear automatically.
- What can I see for worktrees and submodules?
- The server’s Git tab includes HEAD badges for linked worktrees, submodules and detached states. You can also see the commit, origin remote and when the repository last fetched. These details help you recognise the checkout behind a running server, especially when several copies of a project are open at once.
Keep your Git context beside your running work.
Every Pip tool. $29 USD, once. One machine at a time.