GitView: the fleet-first git client

Made for a fleet

Other clients open one repository at a time. You keep twenty.

The question you ask in the morning is which of your projects need you today. GitView answers it on the first screen, then leaves the commands to you.

The fleet is the home screen

The scanner reads branch, ahead/behind, dirty files and merged branches for each repository and streams the rows in as it goes. A cold start paints the list from SQLite before it opens a single repository.

Every button shows its command

Hover to read it, click to run it in that repository’s shell, or shift-click to type it at the prompt and edit it before you press Enter. You keep the habit of typing git, and the buttons make it faster.

Nothing is generated for you

There is no commit-message AI, no agent panel, no account and no telemetry. Repository reads go through libgit2, and anything that touches a remote shells out to git.exe, so your credential helper and SSH agent keep working.

Built for the solo dev with too many repos

Sync the whole fleet from one button.

Sync and prune across repositories. The transcript keeps the command as typed, the exit code and the output for each repository, so you can read what ran and copy a line out of it.
Reads again between commands. A fetch changes ahead and behind, so the batch reads the repository again before it decides whether to pull.
Pin the repositories you are working on and hide the rest. A hidden repository or script leaves the Ctrl+K palette too, so a project’s thirty npm scripts stay out of your way.
GitView finds the tasks. package.json, Cargo.toml, Makefile, justfile, pyproject.toml, .csproj, CMakeLists.txt, Compose files, Unity projects.

Fleet · 6 need attention

4 behind, 2 with merged branchesSync all

The terminal is the app

One shell per repository, and it outlives the view.

Switch projects and come back: the scrollback and the dev server you left running are still there.

Command blocks. PowerShell tells GitView where each command started and how it exited. A bar in the scrollback turns green or red with the exit code, and violet while the command runs.
Ports as chips. A running command prints localhost:5183 and GitView shows it as a chip. Click it and GitView types Start-Process, the same as any other button.
Keep a command you already ran. One button saves the last block as a task for that repository. GitView writes nothing into the repository itself.
A failing build, in one copy. One button copies the command, its directory, its exit code and its output together, ready to paste into whatever you debug with.
Your prompt survives. Starship and oh-my-posh keep working. GitView wraps the prompt in memory and writes nothing to your profile.

pwsh · orbit-api · ↑1 ↓4

ready+ Save as task

GitHub, without the browser

Reads GitHub out of sight, writes to it by typing.

One aliased GraphQL query through gh pulls the pull requests, issues and check runs for the whole fleet. gh holds the token; GitView has no HTTP client and no place to store one.

The inbox. Open pull requests, issues and check runs from all your repositories in one list, each row labelled with its repository.
The PR desk. Push, open a pull request from a form, watch the checks by name, then merge and delete the branch. GitView types each step as a gh command into that repository’s shell.
Updates that name their command. GitView checks its own latest release through gh release view and hands you the gh release download line to run yourself.

Inbox · 5 across 3 repos

gh pr merge 42 --squash --delete-branch

0commits in the history pane, 140 ms a page

0 queryfor the whole fleet’s PRs, issues and checks

0 tokensheld by GitView. gh and git.exe own auth

0 byteswritten to your repositories, your profile, or a server

Install

Download it and point it at a folder.

GitView_x64-setup.exe Build from source

PS F:\GitHub> gh release download -R JacobPoteet/GitView -p "*setup.exe"
PS F:\GitHub> Start-Process .\GitView_0.6.0_x64-setup.exe

Windows 10 / 11git on PATHgh logged in, for GitHubPowerShell for command blocksInstalls per user, no elevation

Unsigned, so SmartScreen will ask once. More info → Run anyway.