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.
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
- never pulls, pushes or commits
- Fetch 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. Fetch from origin there, or open the last 40 commits as a graph.
Carry on in your own workflow.
Pip reads Git’s own files for what it shows and leaves your branches, index and working tree alone. Switch branches using your usual tools and see the updated ref on the next scan.
Keep your bearings when you switch branches.
Run 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 Pip change my repository?
- Only when it fetches. Pip follows the process’s working directory to the repository root and reads Git’s own files directly, again on each scan, so changes made with your usual Git tools appear automatically. That reading writes nothing. Pip runs the Git installed on your computer for three things: Fetch, when you press Fetch or F, choose it in Quick actions or turn on the 15-minute auto-fetch; Check with git, a git status that writes nothing; and History, which reads recent commits with git log and git show. A fetch updates origin’s remote-tracking branches and FETCH_HEAD, like any git fetch. Pip never pulls, pushes, prunes, commits or switches branches.
- What can I see for worktrees and submodules?
- The server’s Git tab labels a linked worktree, a submodule or a detached HEAD. When a repository has more than one worktree, a Worktrees card lists each one’s branch or commit and its folder, and the Repository card counts submodules, including any not initialised or checked out. 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.