Bharath-code/git-scope
Bharath-code/git-scope has 131 GitHub stars and 12 forks. GitHot measured 0 stars in 24 hours and +1 in 7 days. Last checked 2026-11-17 02:12 UTC. Last push 2026-11-05.
What you can do
- π― Attention Summary β At-a-glance verdict of your whole workspace: β² to push Β· βΌ behind Β· β dirty Β· β clean. Repos are ranked into Action / Watch / Clean tiers and sorted by default so what needs you lands at the top.
- π Workspace Switch β Switch root directories without quitting (w). Supports ~, relative paths, and symlinks.
- π Fuzzy Search β Find any repo by name, path, or branch (/).
- π‘οΈ Dirty Filter β Instantly show only repos with uncommitted changes (f).
Measured star growth
- in 24h
- 0
- in 7 days
- +1
- in 15 days
- Collecting history
- in 1 month
- Collecting history
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
About
A fast TUI to see the status of all git repositories on your machine.
Developer ToolsREADME.md
Originalgit-scope
A fast TUI dashboard to view the git status of all your repositories in one place. > Stop the
cdβgit statusloop.
π Website: bharath-code.github.io/git-scope

π‘οΈ Trust & Safety
git-scope is designed to be safe to run frequently and safe to recommend.
- Read-only by design β it does not modify repositories
- Local-first β no network access, no telemetry, no accounts
- Predictable β no background services or daemons
- Conservative scope β focused on visibility, not automation
These choices make git-scope suitable for daily use and work environments where reliability and transparency matter.
β‘ Installation
Get started in seconds.
Homebrew (macOS/Linux)
brew tap Bharath-code/tap && brew install git-scope
Update
brew upgrade git-scope
Universal Installer (macOS/Linux)
curl -sSL https://raw.githubusercontent.com/Bharath-code/git-scope/main/scripts/install.sh | sh
Scoop (Windows)
scoop bucket add git-scope https://github.com/Bharath-code/git-scope
scoop install git-scope
From Source (Windows)
go install github.com/Bharath-code/git-scope/cmd/git-scope@latest
If you find this useful, please consider giving it a β star to help others find it!
π Usage
Simply run it in any directory containing your projects:
git-scope
Commands
git-scope # Launch TUI dashboard
git-scope init # Create config file interactively
git-scope scan # Scan and print repos (JSON)
git-scope status --json # Repo state sorted by attention (JSON)
git-scope mcp # Read-only MCP server on stdio for AI agents
git-scope scan-all # Full system scan from home directory
git-scope issue # Open GitHub issues page in browser
git-scope -h # Show help
By default, it recursively scans the current directory. You can configure permanent root paths later.
π€ Use with Claude Code / Cursor
Running several coding agents across repos and worktrees? git-scope mcp lets an agent see every repo's state β uncommitted files, unpushed commits, ahead/behind β before it starts or ends a task. It is read-only, local-only (no network calls, no telemetry) and scans the roots from your config.
| Tool | Returns |
|---|---|
list_repos |
Every repo, most urgent first |
needs_attention |
Only ACTION / WATCH repos (unpushed on any branch, behind, uncommitted, or stashed) |
repo_status(path) |
One repo under your configured roots |
Claude Code:
claude mcp add git-scope -- git-scope mcp
Cursor (~/.cursor/mcp.json), or any client using the mcpServers format:
{
"mcpServers": {
"git-scope": {
"command": "git-scope",
"args": ["mcp"]
}
}
}
Append directories to scan specific roots instead of your config: "args": ["mcp", "~/code", "~/work"].
Same data for scripts:
git-scope status --json | jq '.[] | select(.tier != "CLEAN") | {path, reason}'
π git-scope vs. lazygit
- git-scope is for your workspace (bird's-eye view).
- lazygit is for a specific repository (deep dive).
| Feature | git-scope | lazygit |
|---|---|---|
| Scope | All repos at once | One repo at a time |
| Primary Goal | Find what needs attention | Stage/Commit/Diff |
| Fuzzy Search | Find repo by name/path | β |
| Integration | Press Enter to open editor |
Press Enter to stage files |
| Performance | ~10ms startup (cached) | Slower on large monorepos |
β¨ Features
- π― Attention Summary β At-a-glance verdict of your whole workspace:
β² to push Β· βΌ behind Β· β dirty Β· β clean. Repos are ranked into Action / Watch / Clean tiers and sorted by default so what needs you lands at the top. - π Workspace Switch β Switch root directories without quitting (
w). Supports~, relative paths, and symlinks. - π Fuzzy Search β Find any repo by name, path, or branch (
/). - π‘οΈ Dirty Filter β Instantly show only repos with uncommitted changes (
f). - π Pagination β Navigate large repo lists with page-by-page browsing (
[/]). Shows 15 repos per page with a dynamic page indicator. - π Editor Jump β Open the selected repo in VSCode, Neovim, Vim, or Helix (
Enter). - β‘ Blazing Fast β JSON caching ensures ~10ms launch time even with 50+ repos.
- π Dashboard Stats β See branch name, staged/unstaged counts, and last commit time. The Hidden column counts stashes plus unpushed commits on other local branches, work
git statusdoesn't show. - πΏ Contribution Graph β GitHub-style local heatmap for your activity (
g). - πΎ Disk Usage β Visualize
.gitvsnode_modulessize (d). - β° Timeline β View recent activity across all projects (
t). - π Symlink Support β Symlinked directories resolve transparently (great for Codespaces/devcontainers).
π― Use Cases
git-scope excels in environments where multi-repo complexity is a daily burden:
- Microservices Management β Quickly verify if all your services are on the correct branch and have no unpushed changes.
- OSS Contribution Tracking β Keep tabs on various upstream forks and personal branches in one view.
- Infrastructure as Code (IaC) β Monitor multiple Terraform/CloudFormation repos for configuration drift or uncommitted edits.
- Context Recovery β Instantly see where you left off after a weekend or a holiday without running
git status20 times.
π The git-scope Advantage
While many Git tools focus on the micro (committing, staging, diffing), git-scope is built for the macro.
Typical git workflows involve "tunnel vision"βworking deep inside one repository. git-scope provides the "command center" view. It is intentionally read-only, local-first, and blazing fast (<10ms), making it the perfect companion to tools like lazygit, gitui, or VS Code.
β¨οΈ Keyboard Shortcuts
| Key | Action |
|---|---|
w |
Switch Workspace (with Tab completion) |
/ |
Search repositories (Fuzzy) |
f |
Filter (Cycle: All / Dirty / Clean) |
s |
Cycle Sort Mode (Attention / Dirty / Name / Branch / Recent) |
1β4 |
Sort by: Dirty / Name / Branch / Recent |
[ / ] |
Page Navigation (Previous / Next) |
Enter |
Open repo in Editor |
c |
Clear search & filters |
F |
Fetch All β update remotes across every repo (safe, read-only) |
r |
Rescan directories |
g |
Toggle Contribution Graph |
d |
Toggle Disk Usage view |
t |
Toggle Timeline view |
q |
Quit |
The dashboard sorts by Attention on launch (Action repos first). Press
sto cycle to the classic sorts, or1β4to jump directly.
βοΈ Configuration
Edit workspace location and code editor of your choice in ~/.config/git-scope/config.yml:
# ~/.config/git-scope/config.yml
roots:
- ~/code
- ~/work/microservices
- ~/personal/experiments
ignore:
- node_modules
- .venv
- dist
editor: code # options: code,nvim,lazygit,vim,cursor β use {path} to place the repo path, e.g. "lazygit --path {path}"
π‘ Why I Built This
I work across dozens of small repositoriesβmicroservices, dotfiles, and side projects. I kept forgetting which repos had uncommitted changes or unpushed commits.
My mornings used to look like this:
cd repo-1 && git status
cd ../repo-2 && git status
# ... repeat for 20 repos
I built git-scope to solve the "Multi-Repo Blindness" problem. It gives me a single screen to see what is dirty, what is ahead/behind, and where I left off yesterday.
πΊοΈ Roadmap
- In-app workspace switching with Tab completion
- Symlink resolution for devcontainers/Codespaces
- Background file watcher (real-time updates)
- Bulk fetch all remotes (
F) - Attention summary + tiered scoring (at-a-glance verdict)
- Quick actions (bulk pull / stash, with confirmation)
- Repo grouping (Service / Team / Stack)
- Custom team dashboards
β FAQ
How do you manage multiple Git repositories locally?
git-scope provides a fast, read-only terminal dashboard that shows the status of many local Git repositories at once. It helps developers regain context across projects without switching directories or running commands repeatedly.
What problem does git-scope solve?
git-scope reduces context switching when working across many Git repositories, such as microservices, tools, or configuration repos. It gives a single overview of repository state so developers can quickly see what needs attention.
Is git-scope safe to use at work?
Yes. git-scope is read-only by design, runs entirely locally, has no network access or telemetry, and does not modify repositories. This makes it safe for daily and work use.
Does git-scope replace git commands?
No. git-scope does not perform git actions like commit, push, or pull. It focuses on visibility and orientation, not automation.
Is git-scope suitable for monorepos?
git-scope is designed for multi-repo (polyrepo) workflows. It is not intended to manage monorepos.
What platforms does git-scope support?
git-scope runs on macOS, Linux, and Windows.
How is git-scope different from other git TUIs?
Most git TUIs focus on interacting with a single repository. git-scope focuses on visibility across many repositories and stays intentionally read-only.
π License
MIT Β© Bharath-code
π Acknowledgements
Built with these amazing open-source projects:
- Bubble Tea β The TUI framework
- Lip Gloss β Style definitions
- Bubbles β TUI components (table, spinner, text input)
β Star History
π₯ Contributors
Made with contrib.rocks.