Desktop
EXEPERT Desktop is a Windows-native Rust application built with GPUI. It owns the workbench shell, Brain canvas, native Chat sources, telemetry, diagnostics, and accessibility surfaces without embedding Electron, React, a WebView, or a browser renderer.
This section is the retrieval entry point for native desktop work. The existing architecture documents remain canonical for runtime behavior; the optimization section explains how to measure and improve that behavior without confusing a GPU-accelerated renderer with a free CPU-side render pipeline.
Start here
| Task | Read |
|---|---|
| Diagnose low Brain FPS or sluggish transcript scrolling | Native desktop performance analysis |
| Plan or review a Rust/GPUI performance change | Rust and GPUI optimization playbook |
| Understand the workbench, worker, canvas, telemetry, or renderer gate | Native desktop GPUI workbench |
| Understand EXEPERT, Codex, and DSH Chat presentation | Native desktop Chat |
| Work on the Codex App Server boundary | Native Codex live client |
| Work on the independent DeepSeek Harness source | Native DeepSeek Harness integration |
Native architecture and UX
- Native desktop GPUI workbench
- Native desktop Chat
- Native Codex live client
- Native DeepSeek Harness integration
- Native human collaboration
- Conversation Brain
- Zed agent UI lessons for EXEPERT
Optimization workflow
- Reproduce the problem in a release build and record the workload, window size, DPI, input device, and active diagnostics.
- Use the performance analysis to separate worker, view construction, layout, scene recording, and GPU presentation costs.
- Apply one method from the optimization playbook, then compare the same workload before and after.
The proposed interactive targets are workload-specific: Chat scrolling aims for a 16.67 ms frame budget, Brain publication-driven rendering aims for 20 ms, and the existing renderer gate retains its separate 40 ms p95 certification threshold. The first two are optimization acceptance targets, not current runtime gates.
Delivery records
These pages record what shipped and how it was validated. They are provenance, not substitutes for current source and runtime measurement.