SOTA code review that uses your session context.

With traditional code review, developers held the context for code changes, but now AI sessions hold that context. This can improve code review drastically, keeping both session history and informing future sessions of best practices.

Get started

Install GX locally:

curl -fsSL https://download.gx.run/install.sh | sh

Inside your repo:

gx init
gx auth login

Then use Git as usual. gx hooks record each commit and publish on push:

gx review

git add -p
git commit -m "some commit message"
git push

Sign up at gx.run. Re-run the install command to upgrade.

Commands

Command	Alias	Purpose
gx init		Set up this repo (identity, hooks, MCP, agent /gx command)
gx auth login		Log into gx Cloud
gx auth status		Show login status
gx auth logout		Log out
gx review [intent]	gxr	Review the current change
gx enhance [intent]	gxe	Top fix from that review, as a prompt for your coding model
gx doctor		Diagnose (and optionally repair) local gx state
gx update		Install the latest published build
gx version		Print version
gx help		Help

Most commands auto-init the repo on first use. Run gx init once so identity and AGENTS.md are set the way you want.

gx init

gx init                 # this repo
gx init --global        # machine-wide hooks via core.hooksPath
gx init --yes           # defaults, quiet on success
gx init --name "…" --email "…"

gx review [intent]

Reviews the working tree by default. Additional flags based on desired direction of review.

gx review
gx review --base origin/main #Review a specific branch
gx review --json #For agents

Flag	Effect
--base <ref>	Review <ref>...HEAD instead of the working tree
--repo	Review the whole repository (wins over --base)
--fast	One reviewer, no verification pass
--deep	More local + indexed context
--focus <path>	Limit to files under a path prefix
--json / --md	Machine / PR-comment output
--no-comment	Skip PR comment; still record history
--no-publish	Skip PR comment and history
--fail-on <level>	Gate: none, any, speculative, worth-exploring, strong, blocking
--scope <lane>	architecture (default), security, performance, onboarding, docs, dependencies, testing, maintainability
--verbose	Include repo facts, docs, and changed files
--max-findings <n>	Cap reported recommendations
--client <name>	Invoking surface (cli, mcp, skill, …)

Findings: blocking (exit 3) vs advisory. A finding blocks only when both reviewers raised it and verification confirmed it.

gx enhance

Same review, narrowed to the single highest-value fix, written as a prompt for a coding model. Always exits 0.

gx enhance | pbcopy
gx enhance "fix the auth timeout" | claude -p "apply this"
gx enhance --base origin/main --fast

gx doctor / gx update / gx version

gx doctor
gx doctor --fix
gx doctor --json
gx doctor --report          # send diagnosis + recent logs to support

gx update
gx update --check

gx version
gx version --json

gx auth

gx auth login
gx auth login --name "studio-mac"
gx auth status
gx auth status --json
gx auth logout

Uninstall

rm -f ~/.local/bin/gx ~/.local/bin/gxr ~/.local/bin/gxe ~/.local/bin/gx-mcp
rm -f ~/.local/share/bash-completion/completions/gx ~/.zfunc/_gx

Local data stays in ~/.gx (or $GX_HOME).

Links

• Product: gx.run
• Installer: download.gx.run/install.sh