code-investigate

Dual-perspective codebase investigation is an analysis method where two independent agents explore code paths separately before integrating results. This approach reduces analytical bias and improves trust in conclusions by highlighting agreements and divergences between distinct perspectives.

To investigate a feature, initiate a project-wide query and follow the guided workflow to initialize exploration phases. The agents trace files, dependencies, and data flow independently without exposing initial conclusions, then generate a structured, integrated report comparing both perspectives.

Yes, this independent analysis workflow supports architecture reviews alongside feature investigations and debugging tasks. It enforces independent exploration of the codebase using Codex MCP, then integrates the findings into a consolidated report highlighting structural agreements and divergences.

Yes, the guided workflow incorporates tracing files, dependencies, and data flow, allowing you to use grep during the independent exploration phases. Both agents analyze relevant code paths separately before combining their findings into a structured integration report.

The best way to reduce bias during source code exploration is enforcing independent analyses where agents evaluate code paths separately before sharing conclusions. Comparing these distinct perspectives in a structured integration report highlights divergences and builds trust in the final conclusions.