feat(magi): add weighted consensus across providers - #1
Closed
Quicksaver wants to merge 2 commits into
Closed
Quicksaver wants to merge 2 commits into
Quicksaver wants to merge 2 commits into
Conversation
🤖 Co-authored by GPT-6 in Codex via T3 Code
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Magi lets a conversation ask several model participants to assess a candidate and reach weighted consensus. The conversation's existing agent arbitrates the result, so users can combine providers without handing their task to a separate coordinator.
Users can arm the next message, including a new conversation's first message, or explicitly ask the agent to start Magi during a turn. Consensus never expands the initiating request's permission to act.
What changed
Validation
216 focused tests passed across 25 files; branch diff check passed.
vp test run apps/server/src/magi apps/server/src/persistence/Layers/ProjectionMagi.test.ts apps/server/src/persistence/Migrations/055_MagiProjections.test.ts apps/server/src/mcp/MagiMcpRouting.test.ts apps/server/src/provider/ProviderMagiConformance.test.ts apps/server/src/provider/ProviderMagiProfile.test.ts packages/contracts/src/magi.test.ts packages/client-runtime/src/state/magi.test.ts apps/web/src/components/magi apps/web/src/components/settings/MagiSettingsPanel.environment.test.tsx apps/web/src/components/settings/magiSettingsSaveScheduling.test.ts apps/mobile/src/features/threads/MagiPanelSheet.logic.test.ts apps/mobile/src/features/threads/magiParticipantIds.test.tsgit diff --check base/main...HEADIntegrated web and mobile verification and before/after UI evidence are still pending. This PR publishing pass changed no implementation files.