Run CodeCouncil 100% free with an NVIDIA API key (full setup guide) #1
adigo-pro
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Run CodeCouncil 100% free with an NVIDIA API key
CodeCouncil's default model is NVIDIA-hosted Nemotron 3 Super — chosen in our bake-off for zero false positives — and NVIDIA hosts it (plus 100+ other open models) behind a free API key. No credit card, no pi login, no trial clock. This guide walks through the whole thing end to end, including how to switch models and how to run council mode entirely free.
1. Get the free key (≈2 minutes)
nvapi-. One key works for every model in the catalog.What the free tier gives you (as of mid-2026): new Developer Program accounts get ~1,000 free inference credits (1 credit ≈ 1 API call) and a rate limit of ~40 requests/minute. That's far more headroom than CodeCouncil needs — the critic only calls the model when your code actually changed, with a floor between calls, so a typical coding session uses a handful of calls per hour. (NVIDIA's own reference: docs.api.nvidia.com.)
2. Install CodeCouncil
curl -fsSL https://raw.githubusercontent.com/adigo-pro/CodeCouncil/main/install.sh | shThat checks Python 3.10+, clones to
~/.codecouncil/app, putscodecouncilon your PATH, wires up pi (the model runtime) if npm is available, and scaffolds~/.codecouncil/envfor the next step. (install.sh is ~102 audited lines —git clone+python3 -m codecouncilworks identically if you prefer manual.)3. Add the key
~/.codecouncil/envlives outside any repo, so the key can never end up in a commit — CodeCouncil loads it automatically on every model call. (Alternatively, run/keysinside a running council for a guided, hidden-input setup.)4. Run it
codecouncil /path/to/repo-you-code-in # defaults to the current directoryWith
NVIDIA_API_KEYpresent and no model configured, CodeCouncil defaults to NVIDIA-hosted Nemotron automatically — nothing else to configure. Code with Claude Code in another terminal; findings arrive in your terminal, on the dashboard (localhost:4700), and inside your coding agent's own context.Switching models (still free)
The running council is interactive — switch the model in place, no restart needed on your side:
/model <provider/model-id>sets and persists the primary model (it restarts just the critic). Every one of these is served by the same free NVIDIA key:/modelvaluenvidia-nim/nvidia/nemotron-3-super-120b-a12bnvidia-nim/nvidia/nemotron-3-ultra-550b-a55bnvidia-nim/nvidia/nemotron-nano-3-30b-a3bnvidia-nim/deepseek-ai/deepseek-v4-pronvidia-nim/deepseek-ai/deepseek-v4-flashnvidia-nim/z-ai/glm-5.2You can also set it before launch with
COUNCIL_MODEL=nvidia-nim/... codecouncil /path/to/repo— precedence is CLI flag > env var > saved config./statusshows what's currently resolved and/configshows where each value came from.Bonus: council mode, also free
Council mode adds a second, independently-trained model (the prober) that reviews the exact same evidence — a prober-only finding is only delivered after CodeCouncil reproduces it for real. The README's example prober uses OpenRouter, but you can run a fully-free council off the one NVIDIA key by picking a prober from a different model family than the primary:
(
/prober offturns it back off.) Different training lineage is the point — the whole premise of CodeCouncil is a second pair of differently-trained eyes, and Nemotron + DeepSeek don't share blind spots.Troubleshooting
401/ auth errorsnvapi-line in~/.codecouncil/env(no quotes needed, no spaces around=)404on model callsnvidia-nim/...values from the table above/statusin the council to see daemons, last verdict, and key state;/verboseunmutes idle-beat chatter/keys+/modelQuestions welcome below — and if you get it running, the 60-second start in the README is the short version of this guide.
All reactions