Investigation: Remove Classic Duo Code Review

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Overview

We've transitioned Duo Code Review to use the Duo Agent Platform with an agentic architecture, but the original implementation likely remains in the codebase. We need to understand what technical debt exists from the legacy version and determine when we can safely remove it.

Current state

Duo Code Review now uses the agentic architecture built on the Duo Agent Platform. The legacy (non-agentic) implementation may still exist in the codebase to support customers who haven't migrated to the new version.

Questions to research

• What legacy code and infrastructure still exists from the original Duo Code Review implementation?
• How many customers are still using the legacy version vs the agentic version?
• How do we track usage to know when all customers have migrated?
• What's our plan for migrating remaining customers to the agentic version?
• When can we set a sunset date for the legacy version?
• What are the maintenance costs of keeping both versions active?
• What technical debt or complexity does the legacy code create for ongoing development?
• Are there any feature flags or configuration that control which version customers use?
• What testing or validation do we need before removing legacy code?
• What's the scope of code removal (backend services, frontend components, database migrations, etc.)?

Expected outcome

A follow-up issue with recommendations on:

• Timeline for deprecating and removing legacy Duo Code Review code
• Migration plan for remaining customers on the legacy version
• Estimated effort for cleanup work
• Risks and dependencies for the removal