Quanta Control is a local-first Git workbench for people who want a focused desktop UI for day-to-day repository work without leaving the normal Git and GitHub tooling they already use.
It runs on your machine, talks to your repositories through the system git executable, and gives you a clean interface for reviewing changes, committing, switching branches, checking history, and working with remotes.
I initially built this project for myself as a companion to AI coding tools such as OpenCode or Codex which don't natively support git source control like IDEs such as VS Code or Zed.
Quanta Control follows the same lightweight, low-fuss philosophy employed by CLI coding tools.
Quanta Control is built around a few common Git workflows:
- inspect working tree changes and staged files
- review diffs before committing
- stage, unstage, discard, and ignore files
- create commits and push them upstream
- switch, create, and delete branches
- inspect commit history
- explore files, blame, search, tags, TODOs, and compare refs
- visualize repo structure in an interactive dependency graph
- manage stashes and guided rebases
- review repository stats and local setup health
- fetch, pull, and push remotes
- verify local Git and GitHub readiness with a pre-flight checklist before opening a repo
The app is intended to complement normal CLI-based development, not replace it. It uses your existing local Git configuration, credentials, and remote setup.
Quanta Control is not a hosted service and it does not proxy your repositories through a cloud backend.
- repositories stay on your machine
- Git operations are executed through the local
gitbinary - GitHub access uses your normal local credentials
- the app reads your environment and Git config rather than inventing its own auth system
If you already work with git, gh, SSH remotes, or HTTPS remotes locally, Quanta Control is designed to fit into that setup.
- open a repo by path
- browse directories to find a repository
- reuse recent repositories
- adjust startup defaults before opening a repo
- view modified, staged, untracked, renamed, and conflicted files
- see addition and deletion counts per file
- inspect diffs in the main workspace
- stage and unstage individual files
- discard changes
- add files or patterns to
.gitignore
- write commit messages and create commits from the UI
- optionally push immediately after a commit
- fetch, pull, and push using the current repo's remotes
- see ahead/behind status from the current branch
- list local and remote branches
- switch branches
- create new branches
- delete branches
- inspect recent commit history
- browse the repository file tree
- open files with blame and file history side panels
- search code with grep-style results
- run pickaxe searches to find when content was added or removed
- compare two refs and inspect changed files
- scan TODO-style comments across the repo
- view, create, and delete tags
- render an interactive deep-space dependency graph for the current repo
- inspect file and symbol nodes with hover labels and a sidebar inspector
- filter graph nodes by name or group
- tune layout physics for charge, link distance, and simulation iterations
- right-click graph nodes to open their backing file in the Explorer
- use GitNexus data when available, with a local import-scan fallback for dependency edges
- view and apply local stashes
- pop stashes back into the working tree
- drop stashes you no longer need
- build an interactive rebase plan from recent commits
- reorder, squash, fix up, reword, or drop commits before starting the rebase
- review the last 12 months of commit activity for your configured Git identity
- use the stats view as a quick personal activity snapshot for the current repo
- optionally generate commit messages from the current diff
- configure an OpenAI-compatible endpoint
- set the model name and API key through local settings
- test model availability from the settings screen
- keep the feature disabled when you want a fully manual commit flow
Before opening a repo, the app can check:
- whether
gitis installed - whether GitHub CLI is installed
- whether GitHub CLI is authenticated
- whether your Git identity is configured
That checklist stays useful after initial setup because it gives you a quick sanity check that your local environment is ready before you start working.
- Node.js 20+
gitcurlandtarfor the hosted installer
Optional but recommended:
ghfor the smoothest GitHub authentication flow
Install from GitHub with:
curl -fsSL https://raw.githubusercontent.com/unmodeled-tyler/quanta-control/main/scripts/install.sh | bashThe installer:
- downloads the app into
~/.local/share/quanta-control - installs dependencies
- builds the production frontend and backend
- creates a launcher at
~/.local/bin/quanta-control
If ~/.local/bin is not already on your PATH, add it to your shell profile:
export PATH="$HOME/.local/bin:$PATH"Then start the app with:
quanta-controlQuanta Control does not create or store a separate GitHub auth model. It uses the same local credentials your Git tools already use.
The simplest GitHub setup is:
gh auth login
git config --global user.name "Your Name"
git config --global user.email "[email protected]"If you prefer SSH or HTTPS remotes without GitHub CLI, that works too. The app's pre-flight checklist will tell you what is available on the current machine.
Typical flow:
- Launch
quanta-control - Check the pre-flight panel
- Open a local repository
- Review changes and diffs
- Commit, branch, fetch, pull, or push as needed
The app is especially useful when you want a faster visual pass over repository state while still keeping your normal terminal-based workflow.
Install dependencies:
npm installRun the standard dev servers:
npm run devRun the production build locally:
npm run build
npm startRun the compiled production launcher:
npm run start:cliRun the repo-local desktop dev launcher:
npm run dev:cliThat launcher starts the local API server and Vite client, then opens Quanta Control in a minimal Electron window for testing.
- Quanta Control is currently centered on local repository operations, not GitHub PR review or hosted account management.
- The app depends on your system Git installation being available in
PATH. - GitHub CLI is optional, but it improves first-run GitHub connectivity for most users.
- This is really just a side project for me - I update it when I can/feel the inspo. I'm open to suggestions/PRs/etc.