Git terminal for Mac — run git and your dev servers in one window.

No branch graph and no hunk-by-hunk staging: the commit dialog commits whole files, and your shell is there for everything else.

1. 01

   You stop losing your dev server every time you switch branches.

   lpm never stops or restarts a service because you checked out a branch. Your npm run dev keeps streaming and hot-reloads while you rebase, resolve conflicts, and push, and a worktree keeps a second branch running at the same time.

2. 02

   You stop toggling between a GUI git client and a terminal.

   One lpm window has a shell pane for git commands, service panes for your running stack, and a Git bar for the clicks: switch branches, commit, open a PR. You keep typing the git you know without leaving your running services to do it.

3. 03

   Context switching between repos stops wiping your git state.

   Jump to another project, fix a blocking bug, push it — your original project is still on its branch, with its services up, with its terminal history intact. Come back and keep rebasing.

4. 04

   Starting fresh after a big merge is two clicks, not a script.

   After pulling a release branch or merging a long-running feature, Stop and Start bring the whole defined stack back fresh in two clicks. No mental dependency graph, no --force-recreate flags typed from memory.

• Built-in diff review and commit dialog

  • lpm: yes
  • GitKraken: yes
  • iTerm2: no
  • Terminal.app: no
  • tmux: no
  • SourceTree: yes

• Full-stack stop and start after a rebase or merge

  • lpm: yes
  • GitKraken: no
  • iTerm2: no
  • Terminal.app: no
  • tmux: no
  • SourceTree: no

• Services detected from the repo when you add it

  • lpm: yes
  • GitKraken: no
  • iTerm2: no
  • Terminal.app: no
  • tmux: no
  • SourceTree: no

• Every repo in one sidebar, each with its running services

  • lpm: yes
  • GitKraken: no
  • iTerm2: no
  • Terminal.app: no
  • tmux: no
  • SourceTree: no

• Free

  • lpm: yes
  • GitKraken· Local and public repos
  • iTerm2: yes
  • Terminal.app: yes
  • tmux: yes
  • SourceTree: yes

• Open source

  • lpm: yes
  • GitKraken: no
  • iTerm2: yes
  • Terminal.app: no
  • tmux: yes
  • SourceTree: no

• Can I use lpm as my primary git terminal on Mac?

  Yes, and the git-specific plumbing carries over untouched. A pane is a real login shell in a real terminal session, so your credential.helper keeps talking to the macOS Keychain, your SSH agent still authenticates pushes, your commit-signing key still signs commits, and every alias in your ~/.gitconfig — the git lg you have muscle memory for — expands the same way it does in Terminal.app. Nothing about the git in your shell is wrapped or re-implemented; you get that shell right beside your running service panes.
• Does lpm replace a GUI git client like GitKraken or SourceTree?

  For the everyday loop, often yes. lpm has a branch switcher with search, a diff review of every uncommitted change, a Commit dialog that drafts the message with AI and can Commit and Push, and Create PR for GitHub. It does not draw a branch graph or stage individual hunks; for those you run git log --oneline --graph or git add -p in the shell pane, or keep your GUI client open alongside lpm.
• Will my dev server stop running when I switch git branches inside lpm?

  No. lpm never stops or restarts a service because you ran git checkout feature/xyz. Services run from the project folder, so after the checkout your dev server is serving the new branch's files, and most hot-reload on their own. If a branch needs a dependency install or a migration, you decide when to stop and start. To keep one branch running while you work on another, open it with New Worktree.
• How does lpm help with PR review workflows on Mac?

  Choose New Worktree on the project. lpm makes a separate checkout on its own branch with its own services, listed under the original in the sidebar. Check out the review branch there and start the services you need to test it; if one wants a port your original is still using, lpm flags the clash when you press Start. Your original branch keeps running untouched, and when you're done you delete the worktree from the sidebar.
• Can lpm write my commit messages and PR descriptions?

  Yes, through the AI coding agent you already have installed: Claude Code, Codex, Gemini CLI, or OpenCode. Generate with AI in the Commit dialog writes a conventional-commit message from the selected files, and Create PR drafts the title and description. You can add your own instructions globally or per project. lpm hosts no model, so it runs on your own account.
• Can I run git bisect or long-running git operations inside lpm?

  Yes. A shell pane in lpm is a full terminal session — git bisect, git rebase -i, git filter-branch, and any other long-running git operation runs exactly as it would in iTerm2 or Terminal.app. The other service panes keep running alongside it so you can see the effect of each bisect step on your live stack.
• Is lpm a good terminal for Mac developers who use the GitHub CLI?

  Yes. lpm shell panes run your full shell configuration, so gh pr create, gh pr checkout, gh run watch, and any other GitHub CLI command work with your existing auth and aliases. Run gh run watch in a shell pane while your dev server streams in the next pane — you get CI output and local output in the same window without a browser tab. With gh signed in, the footer also shows the current branch's PR number and state.