apex

Apex Directive in the terminal: a multi-model code review on your own keys.

Three models review your changes at once, each with a different lens (architect, tech lead, security). Instead of three walls of text, findings are discovered as a structured list, deduplicated across the panel, and presented one at a time so you can see where the models actually disagree.

npx @apex-directive/cli review

Requires

Node 24 or newer, and your own API keys:

export ANTHROPIC_API_KEY=...
export OPENAI_API_KEY=...
export GOOGLE_API_KEY=...

Calls are billed by those providers directly. Nothing is sent anywhere else.

Commands

apex review [paths]    review the branch's changes, the files named, or --pr <n>
apex ask <question>    one open question: no findings, no merge seat
apex show [id]         the findings, or one finding in full
apex discuss <id>      have the panel talk one finding through
apex final             write the merged document (apex-review.md)
apex dismiss <id>      set a finding aside (-m "reason" required)
apex table             show the panel; add|rm|merge <model> to change it
apex history           saved reviews; history rm <id> deletes one

apex --help has the full flag list.

In CI

--ci runs a review with no prompts and writes apex-review.md in the same run. Exit codes are the contract:

0  ok
1  usage, config or refusal
2  --fail-on tripped
3  over --budget, nothing sent
4  a seat did not answer

apex review --ci --fail-on high --budget 200k

On GitHub, the Apex Directive review action runs this on every pull request and posts the review as a comment:

- uses: Stackforge-Labs-Limited/apex-review-action@v1
  with:
    anthropic-api-key: ${{ secrets.ANTHROPIC_API_KEY }}
    openai-api-key: ${{ secrets.OPENAI_API_KEY }}
    google-api-key: ${{ secrets.GOOGLE_API_KEY }}

Configuration

.apex.toml in the repo, falling back to ~/.config/apex/config.toml.

Reviews are kept in .apex/reviews/, which holds your source code and should stay git-ignored.

License

FSL-1.1-MIT (Functional Source License). Use it, change it and run it for anything except a competing product or service. Each version becomes MIT two years after it is released.