# Overview GitLab Duo Chat is currently implemented separately in VS Code and JetBrains extensions. This epic tracks the work to migrate both implementations to use a unified WebView implementation hosted in the Language Server (LS), reducing duplication and maintenance overhead while ensuring consistent user experience across IDEs. ## Current State - Visual Studio extension has a working WebView implementation in the Language Server - JetBrains plugin and VS Code extension have their own implemenation - Features are currently being developed separately for each extension ## Goals 1. Migrate VS Code and JetBrains Duo Chat to use the Language Server WebView implementation 2. Ensure feature parity between both extensions 3. Establish the Language Server as the single source of truth for Duo Chat functionality 4. Streamline future feature development by having a unified codebase ## Benefits - **Reduced Maintenance**: Single implementation reduces code duplication and maintenance effort - **Consistent Experience**: Users get the same chat experience regardless of their IDE - **Faster Development**: New features can be implemented once and automatically work across all supported IDEs - **Better Testing**: Consolidated testing approach for chat functionality ## Technical Considerations - Feature parity must be maintained throughout the migration - Existing GitLab UI components will be replaced with Duo UI components - Theme support will be implemented through editor styling variables ## Timeline - Initial scoping of development work: 17.6 - Migration and feature parity: 17.8 - Full implementation and rollout: TBD based on development progress ## Out of Scope - Changes to core chat functionality - Development of new features during migration phase - Modifications to the existing WebView implementation ## Dependencies - Completion of Duo UI migration from GitLab UI - Language Server WebView implementation stability - IDE-specific integration requirements ## Success Criteria 1. VS Code extension successfully using Language Server WebView 2. JetBrains plugin successfully using Language Server WebView 3. All existing features working in both IDEs through Language Server 4. No regression in functionality or user experience 5. Successful theme support across both IDEs 6. Unified development workflow for future features