System architecture
Follow a request from an interface through the Rust orchestrator, policy boundary, workers, and durable state.
One observable path from request to bounded execution
Control plane
Axum exposes the local HTTP and WebSocket surface on port 18789. Tokio coordinates scheduling, event delivery, and worker lifecycles while SQLx persists sessions, tasks, approvals, memory, and ledger state in PostgreSQL.
Model and execution planes
A TypeScript model gateway on port 18790 separates model-provider routing from agent logic. Skills execute through isolated Node.js, Python, WebAssembly, or trusted native Rust workers rather than inheriting unrestricted host authority.
Desktop surface
The Dioxus desktop interface observes the same event stream used by API clients. It presents tasks, agents, skills, approvals, memory, MAGIC, ledger history, and settings without becoming a second orchestration authority.
Durable data model
- Identity and Soul establish the agent operating context
- Sessions and messages preserve channel-specific transcripts
- Tasks and runs track work from intent through execution
- Skills, XP, memory, and Elixirs capture reusable capability and learning
- Approvals, capabilities, attestations, and the ledger record authority and evidence
Configuration precedence
Runtime configuration resolves explicit command-line choices before environment and file defaults. Machine profiles keep host-specific model, GPU, service, and workspace choices separate from portable project configuration.