Make branch-authored MCP config reviewable without executing it - #443
Conversation
…ble-mcp-config # Conflicts: # src/Capacitor.Cli.Daemon/Services/LocalPermissionBridge.cs # test/Capacitor.Cli.Tests.Unit/Services/AcpHostedAgentRuntimeFactoryTests.cs
PR Summary by QodoExpose branch-authored MCP config for borrowed reviews via sidecar + loopback MCP tool
AI Description
Diagram
High-Level Assessment
Files changed (21)
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTo customize comments, go to the Qodo configuration screen, or learn more in the docs. |
|
NO FINDINGS |
Summary
Why
Borrowed reviewers previously had to omit branch-authored MCP configuration to avoid executing untrusted commands, which also made those changes invisible to review. This exposes the staged Git blobs as explicitly untrusted review evidence without placing them in the reviewer worktree.
Validation
BorrowedReviewContextTests: 16 passedLocalPermissionBridgeTests: 49 passedMcpReviewContextServerTests: 6 passedAcpReviewFlowMcpContextTests: 3 passedgit diff --check: cleanFull unit/integration suites and NativeAOT publishing are intentionally delegated to CI to avoid overloading the development machine.
Design
docs/superpowers/specs/2026-08-02-ai1706-reviewable-mcp-config-design.mddocs/superpowers/plans/2026-08-03-ai1706-reviewable-mcp-config-implementation.md