Three-process model#
Helmor has a React frontend, a Rust Tauri backend, and a Bun sidecar. The frontend owns the desktop UI, the backend owns local state and system operations, and the sidecar talks to coding agent SDKs.
Message flow#
User prompt -> Rust streaming command -> sidecar -> agent SDK -> streamed events -> Rust pipeline -> React conversation UI.
Main responsibilities#
- Frontend: workspace navigation, sessions, composer, editor, inspector, settings, and review surfaces.
- Backend: SQLite persistence, Git operations, workspace lifecycle, GitHub integration, IPC commands, and sidecar supervision.
- Sidecar: provider-specific session management for Claude Code and Codex-style agents.
Design goal#
Keep agent execution, local data, and review UI separated. That separation makes the app easier to debug and keeps provider-specific behavior out of the product surface.