Quorum
Question: how can a developer inspect several model perspectives without losing the disagreement behind the recommendation?
Inspect the repository ยท Install from VS Code Marketplace
The workflow
Quorum runs model panels inside VS Code and produces a decision memo with a recommendation, dissent, confidence, and evidence. Council threads let the developer ask follow-up questions rather than start another disconnected conversation.
The extension supports workflows such as code review, debugging, research synthesis, and architecture tradeoffs. Repository context is opt-in: selected files and direct imports are captured as a redacted, content-hashed snapshot.
The product choice
The interface makes disagreement inspectable instead of presenting only a single polished answer. Keeping the question, memo, and follow-up in the editor connects the deliberation to the developer's existing work.
That is an implemented workflow choice, not proof that a council is always better than one model.
What the artifact establishes
There is a published extension with a documented installation path and source to inspect.
It does not by itself establish decision-quality improvement, independent validation, active-user counts, retention, or commercial success. The research associated with the development name Router Council is a separate publication with its own limits.