Feature guide · Electron

The control room is local. The work stays quiet.

The Electron client is a manual GUI for the MCP, while the older home page remains the explanatory documentation surface.

Behavior

Workspaces create rooms, host or schedule the API, launch hidden applications, save named computers, and persist subagent lanes. Quick launch includes an inline application browser beside its command field, while the runner also browses files and folders into JSON parameters. Tool runner accepts any tool name and routes locally or over the saved LAN connection. History, notifications, changelog, settings, and the regex builder are browser-style tabs. History combines text/regex search, date ranges, and action counts derived from the records, then exports the filtered view. Settings includes a continuous color field and local HEX/HEX8/RGB/RGBA/alpha/HSL/HSV/HWB/CIELab/LCH/OKLab/OKLCH/CMYK/CSS-name conversion with gamut and contrast feedback. Right-click or the keyboard context-menu path opens a per-target typography and color editor with resettable overrides; built-in and named presets persist and export with the profile.

Configuration

Run npm install and npm start from electron/. On Windows startup, hidden dependency repair includes AutoHotkey when it is absent, and the launcher repairs a missing Electron runtime cache. Settings persist language mode, independent funny levels, theme, density, appearance, tab layout, connections, agents, and history.

Failure modes

Dependency failures identify their stage.
Invalid regex patterns show inline syntax feedback without changing the previous result.
Import/export reports malformed JSON rather than silently dropping values.
Canceling a native path picker leaves its original field unchanged.

Security

Context isolation and disabled Node integration protect the renderer. The main process validates external links and API schemes, never uses shell execution, and spawns child processes hidden. Trusted-LAN connections remain powerful by design.

Verification