The single-model problem
One model answer isn’t always enough.
When the stakes are high, a single response can miss tradeoffs, bury contradictions, or commit to one viewpoint before alternatives are even considered.
Model fusion for Pi agents
Pi Fusion turns a single high-stakes prompt into independent model answers, surfaces contradictions instead of hiding them, and lets a judge model synthesize, verify, and report the final answer — right inside Pi.
pi install git:https://github.com/aa2246740/pi-fusion@main
You choose the models · Optional evidence tools · Local artifacts and cost reporting
The single-model problem
When the stakes are high, a single response can miss tradeoffs, bury contradictions, or commit to one viewpoint before alternatives are even considered.
The fusion answer
Pi Fusion runs multiple participant models in parallel, compares their answers, and uses a judge model to synthesize a final response — with optional evidence gathering, verification, and durable artifacts kept locally.
Capabilities
Use it for research, planning, architecture decisions, debugging hypotheses, code review, vendor comparisons, writing, and document synthesis.
Independent answers from multiple models, side by side.
A judge model reconciles, notes contradictions, and reports the final answer.
Optionally re-check and refine before the answer is final.
Connect provider-agnostic search and fetch tools when current, sourced answers matter.
Evidence summaries, token usage, and cost reporting stay with you.
Configurable fallback and retry behavior keeps panel runs resilient.
Workflow
The panel fans out, evidence is attached when available, and the judge turns disagreement into a stronger answer.
One prompt enters the fusion panel.
Participant models respond independently.
Search, fetch, and local read-only context can be used when configured.
The judge compares agreements, contradictions, and missing evidence.
The final answer, evidence summary, token usage, and cost report are saved locally.
Pi-native
Configure the panel, diagnose availability, then run fusion from the place you already work.
/pi-fusion-config Configure participants, judge, fallbacks, tools
/pi-fusion-doctor Diagnose model and evidence backend availability
/pi-fusion <prompt> Run a fusion panel/pi-fusion Should we migrate this module to a plugin architecture?
/pi-fusion --fast Summarize the tradeoffs of these three plans.
/pi-fusion --quality Compare vendors and cite current sources.DRACO benchmark
Pi Fusion is not just a demo of multi-model prompting. We tested it on the same DRACO 10-case benchmark protocol used to evaluate Fusion API budget mode. Pi Fusion exceeded the 64.70 Fusion API budget baseline, reaching 66.40 in full validation and 66.20 in the latest repeat validation, with all 10 cases completed and no judge failures.
| System / run | full10 score | Δ vs Fusion API budget |
|---|---|---|
| Fusion API budget baseline | 64.70 | — |
| Pi Fusion kept validation | 65.30 | +0.60 |
| Pi Fusion best validation | 66.40 | +1.70 |
| Pi Fusion latest validation | 66.20 | +1.50 |
Generation used sanitized prompt-only case files. The benchmark answer/rubric/scoring artifacts were not available to Pi Fusion during generation and were used only after generation by the scorer.
Safety & control
No multi-agent writes to your real workspace. Evidence and artifacts are explicit, reviewable, and local.
Deterministic calculations run in a sandboxed environment.
Imported files are explicit evidence, not hidden state.
Fusion still works without search or fetch tools.
You choose the models, fallbacks, tools, and reporting behavior.
Docs
The GitHub repository is English-first for open-source discoverability, with Chinese documentation for local users and contributors.
Install
Install Pi Fusion, configure your participant and judge models, then run your first fusion panel in minutes.