Skip to content

Install the CLI

Install the lgtmaybe command-line tool once; then point it at any provider. This page is only about getting the CLI onto your machine. Choosing a model backend — a hosted API, keyless cloud, or a local model — comes after, in the provider how-tos.

Install (pip)

Works on any OS with Python 3.11+:

pip install lgtmaybe

Verify it:

lgtmaybe help

That prints the command list with usage examples; lgtmaybe help <command> (e.g. lgtmaybe help review) shows the full option reference for one command.

Upgrade later with pip install --upgrade lgtmaybe.

Install on macOS (Homebrew)

On macOS (and Linuxbrew) you can install from the project's Homebrew tap instead of pip:

brew tap MattJColes/lgtmaybe
brew trust MattJColes/lgtmaybe
brew install lgtmaybe

The middle step is required: current Homebrew refuses to load a formula from a third-party tap until you explicitly trust it (Error: Refusing to load formula … from untrusted tap). This is a one-time, per-machine decision that applies to every tap outside Homebrew's core — the tap author can't waive it for you, by design. To trust only this one formula instead of the whole tap, use brew trust --formula MattJColes/lgtmaybe/lgtmaybe.

Tapping and installing in one line (brew install MattJColes/lgtmaybe/lgtmaybe) works too, but still needs the brew trust … step first — otherwise the install stops at the untrusted-tap error.

Upgrade later with brew upgrade lgtmaybe.

Homebrew installs lgtmaybe into its own isolated virtualenv, so it never touches your system or project Python. The formula creates the venv and installs lgtmaybe and its dependencies from prebuilt PyPI wheels (no compiling), so a first install takes about a minute, mostly download time. It works on any architecture and macOS version — there's no prebuilt bottle to match. It also pulls the ast-grep formula, which lgtmaybe uses for cross-file symbol resolution during review.

Cloud providers need extras

The base install (either method) covers every API-key and local provider:

Providers Covered by base install?
openai, anthropic, openrouter, zai — set the provider's API key in your environment ✅ Yes
ollama, openai-compatible — fully local, point --api-base at the server ✅ Yes
bedrock, vertex, azure — keyless cloud (OIDC/WIF) ❌ Needs an extra

The keyless cloud providers need extra cloud SDKs that the base install (and the Homebrew formula) does not bundle. Install the CLI from PyPI with the matching extra:

pip install 'lgtmaybe[bedrock]'   # or [vertex] / [azure]

or run them through the GitHub Action, where the image bundles all three and wires up the OIDC/WIF auth for you.

Next steps