gbx

gbx

Manage your fleet of git repos with a pretty TUI.

gbx (git batch executor) is a terminal UI for everyone juggling a directory full of git checkouts — microservices, monorepo siblings, a folder of cloned projects. It shows the branch, ahead/behind, and dirty state of every repo at once, lets you filter or search the list with an fzf-style query, and runs a fixed set of non-destructive git commands across whatever repos currently match.

Install

Homebrew (macOS & Linux):

brew install deemson/tap/gbx

Go:

go install github.com/deemson/gbx@latest

Prebuilt binaries: grab a tar.gz for your platform (macOS / Linux, amd64 / arm64) from the latest release, extract it, and put gbx on your PATH.

Usage

Run gbx in a directory that contains git repositories. It scans the immediate subdirectories (a flat, non-recursive scan), and lists the ones that are repos with their current branch, ahead/behind counts, and working-tree changes.

From the list, single keys run a git command across every repo currently matching the filter:

Every command is non-destructive — there is no force-push, reset, or anything that throws away work. Press ? in the app for the complete, always-current key reference.

Filter & search

Both the filter and the search prompt take the same query — a space-separated list of terms, all ANDed together; a repo matches only if every term matches:

By default terms match against the repo name or branch. ctrl+2 restricts matching to the name, ctrl+3 to the branch, and ctrl+1 returns to both — in either prompt.

Filter (ctrl+f) narrows the list to the matching repos; the git commands then run across exactly that set. Search (ctrl+s) leaves every repo visible and instead jumps the cursor to the matches, dimming the rest — ↓/↑ walk between them. Filter is for acting on a subset; search is for finding one repo in a list you want to keep whole.

Configuration

gbx works with no config at all. Configuration only customizes the actions menu — the tools you can launch in the cursored repo with enter. By default that menu offers lazygit and your shell.

Write the default config (and a companion JSON schema for editor validation) to $XDG_CONFIG_HOME/gbx/config.toml (i.e. ~/.config/gbx/config.toml):

gbx config write-default

It looks like this:

#:schema ./schema.json
[[actions]]
label = 'lazygit'
command = ['lazygit']

[[actions]]
label = 'shell'
command = ['{{ env.SHELL }}']

(The #:schema line points editors like Taplo at the companion schema.json written alongside it, for live validation and completion.)

Each action is a label plus an argument vector run in the cursored repo's directory (it takes over the terminal until it exits). {{ env.NAME }} expands to the environment variable NAME; an unset variable or unknown placeholder aborts the action rather than running the wrong command. Up to 9 actions are supported (bound to digits 1–9).

Requirements

• git must be on your PATH — gbx shells out to it for everything.
• lazygit is optional, needed only if you keep the default lazygit action.

Releases

Binaries and per-release changelogs live on the Releases page.

License

MIT