Implement Chromium Embedded Framework (CEF) for Desktop Agent WebView

[paulpv]

Summary

Refactor the Desktop Agent's WebView component to use Chromium Embedded Framework (CEF) for improved compatibility, performance, and future extensibility.

Context

This feature is part of modernizing the codebase and is needed to:

• Enable cutting-edge web rendering on desktop devices (JVM)
• Prepare for advanced agent UX that may require more robust browser features
• Align with industry standards for embedded browsers in desktop apps

Current State:

• ✅ Desktop agent uses a basic WebView (likely JCEF, JavaFX, or Java platform default)
• 🔴 CEF is not currently integrated
• 🔴 Embedded browser feature set is limited compared to Chrome

Dependencies:

• Blocked by: None
• Depends on: Analysis of CEF integration feasibility within Kotlin/Compose Multiplatform

Acceptance Criteria

• Desktop agent uses CEF as the embedded browser (or explains fallback)
• All interop/JS-BRIDGE functionality continue to work with CEF
• Feature parity (or clearly documented gaps) between legacy and new webview
• Documentation updated in IMPLEMENTATION_STATUS.md
• All sub-issues completed

Sub-Issues

• Integration POC: Run CEF from Kotlin/JVM app-desktop
• Refactor existing desktop webview module for new architecture
• Document any migration issues/project-specific quirks

AI Implementation Prompt

Research the process for integrating Chromium Embedded Framework (CEF) in a Kotlin/Compose Multiplatform desktop app. Identify suitable JVM bindings (e.g., JCEF) or alternatives, assess compatibility with Compose, and create a migration plan for the agent's current WebView solution. List obstacles, workarounds, and proposed APIs for JavaScript/agent bridge.
Consider, and document, if similar improvements are feasible/valuable for Android (recommended: Android WebView/Chromium) and iOS (recommended: WKWebView, Chromium on iOS).

Reference: See IMPLEMENTATION_STATUS.md, ARCHITECTURE.md, and platform-specific modules.

Testing Plan

To verify:

Manual Verification:

1. Build and launch desktop agent on all supported platforms (Windows, macOS, Linux)
2. Navigate to key agent workflows using embedded webview
3. Confirm modern web standards support and agent-JS bridge functioning
4. Compare performance and bug reports vs legacy version
5. If applicable, verify documentation for Android (WebView/Chromium) and iOS (WKWebView) is updated accordingly

Related Documentation

• IMPLEMENTATION_STATUS.md: [platform migration status]
• ARCHITECTURE.md: [agent/webview integration]