Core System

Architecture

High-Level Components

Repository Layout

• apps/desktop: Electron shell + renderer UI
• apps/daemon: local API, orchestrator, runtime internals
• config: control-plane schemas and runtime JSON config
• plugins: plugin manifests and tool handlers
• data: runtime state and mutable data
• userland: workspace surface for explicit code edits

Runtime Flow

1. Desktop launches and connects to daemon APIs.
2. Daemon loads control plane, tools, policy, and plugins.
3. Jobs and tool calls run through validation and policy checks.
4. Risky operations become approvals before execution.
5. Events and audit records are written for traceability.

Control Plane Validation

Current daemon code validates:

• schema compatibility (tool, policy, job, workflow, ui)
• duplicate UI page/sidebar IDs and paths
• job script safety constraints and dependency format restrictions

This keeps self-editing bounded by explicit rules.

Last updated from repo snapshot: 2026-02-20

Last updated: 2026-02-20