The website is mission control: it configures behavior, defines safety boundaries, and displays outcomes and summaries. It does not execute automation.

Execution and orchestration live outside the control plane:

• Browser extension: senses the page (context/captures), enforces policy (allowed domains, kill switch, mode), and performs browser actions.
• Orchestrator / runtime: plans and coordinates tasks and applies safety enforcement beyond the UI.
• Control plane (this site): config + monitoring only (no chat UI, no task execution).

Architecture diagram

The separation keeps the UI calm and predictable while execution stays contained and stoppable (kill switch).