ShimX is composed of the Flutter desktop app, local proxy, MCP server, CDP injection layer, and in-page bridge.

1. The Flutter app initializes windowing, tray, theme, localization, and persisted config.
2. If enabled, the local proxy and MCP server start on launch.
3. On injection, ShimX launches or attaches to Codex Desktop and enables the remote debugging port.
4. ShimX connects through CDP, registers Dart bridge routes, and injects bridge_bootstrap.js, built-in enhancements, and user scripts.
5. The injected page scripts call Flutter features through the bridge for provider switching, session reading, export, logs, plugins, and Claude Bridge.
6. With takeover enabled, Codex requests go to the ShimX local proxy first, then to the selected upstream provider, protocol, and model.

Contributors: 挽风

Previous pageQuick Start

Next pageProviders and Proxy