A multi-model AI council and ad-hoc sidecar, with Claude as orchestrator.
independent reviews→anonymized peer cross-review→non-Claude chair verdict→tiered accept/deny
Hand Claude a doc, a diff, or a design and say council review this — Amicus runs the ritual and hands back a decision. Or skip the ceremony: fork a single conversation to Gemini, GPT, DeepSeek, or any other model, work in parallel with full context, and fold the result back.
Any model — via OpenRouter, or local at $0
Each convening: different lineup, different chair, different material, different verdict. The ritual — independent review, blind cross-review, chair synthesis — never changes.
Say council review this and the material lands in the middle of the table. Every member reads the same doc, diff, or design cold — no one sees another's review while writing their own.
Then the reviews swap hands anonymously: models rank and adjudicate each other's work with the names stripped, so no reputation bias. A non-Claude chair synthesizes the rankings into a single tiered verdict — and it folds straight back into Claude's context.
Convene a council, fan out a wave, gate a release — every run shares your Claude context automatically.
Open the Workspace and watch your council think — seats reporting in, phases advancing, costs ticking per model. Finished runs replay end to end.
Your council ranks every review blind — bylines stripped before the vote, so no model can favor its own. Some have even disputed their own work.
Your plan came from Claude — don't let Claude grade its own homework. A non-Claude chair runs the vote and signs the verdict; Claude only keeps the room in order.
Two reviewers pass your auth refactor; the third catches session fixation. Amicus treats that dissent as the finding — adjudicated and confirmed, not averaged away.
Seat a local model at the same table as the cloud ones — same prompt, same vote, $0.00, and nothing leaves your machine. Sometimes the free seat is the one that catches it.
Models from the same family share the same blind spots — so build a bench that mixes families. Seat 3, 5, or 7 from your own API keys, one OpenRouter key, or local runtimes, each pick earning its chair on specialty, price, or privacy.
Every council prints its estimated cost before a single call goes out — and a hard budget cap bounces the run you didn't mean to launch. The receipt matches the estimate, not your worst fear.
Not just code — hand the council a spec, a plan, even a book chapter, plus the criteria that matter to you. Reviewers judge it independently and you get one adjudicated verdict: what to fix first.
The ritual never changes — critic seat, expert lenses, debate rounds, and a Claude seat are all off until you name them. Dial up what you need and see the exact run shape before anything launches.
A seat dies mid-run? Every surface tells you — the CLI exits 2, verdict.json flips "degraded": true, and the report wears a red banner. Amicus never degrades silently.
Model catalogs rot quietly — an alias that worked last week can 404 today. One live probe proves every seat on your bench actually serves, so you find out in the check, not mid-council.
Configure an MCP server once in Claude Code and every seat picks it up — Gemini, GPT, even your local model. Your tools travel with the council, zero extra setup.
Monday's council flagged two problems, so you rewrote. Pick up the same thread today — one question, and yesterday's findings flip from red to green.
Release night, a 4,000-line RC diff nobody fully read. Put a council between your pipeline and the tag — exit 0 ships it, exit 1 sends it back.
Install as a Claude Code plugin, via one script, or with npm — each delivers both skills, the CLI, and the MCP server. No manual registration required.
A full multi-model council for structured review, or a quick fork to one other model. Both share your full Claude context automatically.
Say council review this. Independent reviews → anonymous cross-review → a non-Claude chair verdict. You accept or deny tiered findings.
Or fork to a single model — Gemini, GPT, DeepSeek, any. It starts with your full Claude context. Work alongside it in a real window.
Click Fold and a structured summary flows back into Claude. Findings, recommendations, decisions. No context switching, no noise.
Amicus can also run headlessly as parallel subagents inside Claude Code or Cowork. Spawn multiple models at once. Each runs independently on its task. All results fold back into Claude.
From inside Claude Code or Cowork, ask Claude to spawn headless Amicus instances using the MCP tool. Each subagent gets your full session context, works autonomously on its assigned task, and returns a structured summary. No window switching, no prompting each model yourself.
Run multiple Amicus instances simultaneously to split work across specialized models. One reviews architecture. Another audits security. A third generates tests. Claude collects every summary and synthesizes the results back into your main context.
Amicus reads your active Claude Code session and hands it to every seat at the table. No export, no copy-paste, no starting from scratch.
Council members are briefed independently: each seat gets the same instructions, material, and criteria, plus your session context. No reviewer sees another's work until cross-review — where authorship is stripped. The chair sees every review and ranking, never the names.
Amicus works natively across Claude Code, Cowork, and Claude Desktop — install once, use everywhere. Support for Claude Code on the web is still experimental.
Use the amicus command directly in your terminal alongside Claude Code. Desktop app and CLI both supported.
Amicus registers as an MCP server automatically. Cowork agents can spawn Amicus instances natively from their sandbox.
Add Amicus as an MCP server in Claude Desktop to run councils and forks as native tools — no terminal required.
Running Amicus from Claude Code on the web is experimental — the local CLI and MCP server aren’t fully available in the cloud sandbox yet.
Use your existing API keys directly, connect everything through OpenRouter with a single key, or run models locally with no key at all.
200+ models from every provider. One API key for everything.
Already have a Google AI, OpenAI, Anthropic, or DeepSeek key? Use it directly. No middleman, no extra accounts.
One key, every model. Automatic fallback, unified billing. Run amicus setup to configure.
Run models on your own machine via LM Studio, Ollama, or vLLM — no key, no per-token bill, private and offline. Run amicus provider add to connect.
Independent reviews → anonymous cross-review → non-Claude chair verdict. Blind spots surface when models from different families disagree.
Spin up one other model in a real window with full context, work alongside it, and fold a structured summary back when you're done.
Run N models on the same prompt headlessly in one wave. Every leg gets the same briefing; results arrive as a single JSON wave document.
No frozen model table. Aliases and validation resolve against a live catalog fetched from provider APIs — model names stay current without a code change.
Developed and tested on Windows 11, no WSL required. Full unit suite runs green on Windows. macOS and Linux supported too.
Auto-registered MCP server and two installed skills (second-opinion, sidecar). Claude drives Amicus; you stay in your editor.
Conversation history passed automatically. Conflict detection warns when files changed externally — a fold never silently overwrites newer work.
Every session is saved. List, resume, or chain new investigations on previous findings. Full JSON output for scripting and agent consumption.
A few things to have in place — and an honest look at what a run actually costs you.
node --version to check.A sidecar is a single model call; a full council is typically ~5–8 paid model calls (3 reviewers across 2 fan-out waves + 1 chair). Amicus estimates the cost up front and a budget gate blocks runaway spend.
Want to try it for nothing? OpenRouter offers free model variants — route a council through those and you pay zero for tokens.
Amicus builds on OpenCode, not around it. OpenCode does the heavy lifting.
Two commands: one installs the CLI, both skills, and the MCP server — the other configures your keys and default model. Amicus can't reach a model until amicus setup has run.