Desktop Architecture
The desktop app follows the standard Electron split, but MindMux uses that split in a fairly opinionated way.
Renderer
The renderer is a React application that owns:
- session and navigation surfaces
- chat presentation
- page and document browsing
- task views
- settings and configuration UI
The renderer is where users work, but it does not own the durable system state by itself.
Main process
The main process is the orchestration layer. It manages:
- project selection
- session lifecycle
- runtime resolution
- file watchers
- task orchestration
- preferences and auth storage
- IPC between UI and system services
This is where MindMux turns user intent into coordinated app behavior.
Preload and IPC
MindMux uses a preload boundary and typed IPC surface to expose app capabilities safely into the renderer. That boundary is important because many key operations involve filesystem, auth, process spawning, or background services.
Why this split works well for MindMux
MindMux is not a static document viewer and not just a network client. It needs desktop-grade access to:
- local files
- child processes
- watchers
- OS integration
Electron is a natural fit for that shape.