DELIGHT docs
Architecture, setup, browser compute, p2p direction, API surface, and MCP/OpenClaw context in one place.
How the stack connects
Protocol sets the narrative, the future p2p layer handles transport, the router chooses execution, the compute layer runs work, and the local core keeps identity and control.
System flow
Voice and orchestration pull context from memory, route work into local, browser, or cloud compute, then expose results through automation and API.
Overview
OpenDefines what DELIGHT is, what it is not, and why the site is protocol-shaped.
Role
Defines what DELIGHT is, what it is not, and why the site is protocol-shaped.
Connected with
Architecture, roadmap, risks, ecosystem.
Why it matters
Useful as the first trust layer before deeper technical pages.
Architecture
OpenExplains the five-layer stack and the eight core systems behind DELIGHT.
Role
Explains the five-layer stack and the eight core systems behind DELIGHT.
Connected with
Router, memory, browser farm, local compute, cloud routing, automation, API.
Why it matters
Shows how product narrative maps onto real technical boundaries.
Install
OpenCovers runtime setup, local environment, and first launch path.
Role
Covers runtime setup, local environment, and first launch path.
Connected with
Local compute, API, browser components, orchestration runtime.
Why it matters
Helps developers move from concept into a working stack.
API Surface
OpenDescribes the external interface for chat, tasks, voice, and integrations.
Role
Describes the external interface for chat, tasks, voice, and integrations.
Connected with
FastAPI, orchestration core, auth, rate limits, future ecosystem clients.
Why it matters
Turns the stack into something other systems can actually use.
Browser Farm
OpenDocuments browser-based compute, sessions, profiles, and free-web inference.
Role
Documents browser-based compute, sessions, profiles, and free-web inference.
Connected with
SessionManager, Camoufox, Playwright, memory, routing, automation.
Why it matters
This is the core economic lever for low-cost or zero-API compute.
P2P Layer
OpenCovers the future network layer: peer transport, privacy, and onion-style routing.
Role
Covers the future network layer: peer transport, privacy, and onion-style routing.
Connected with
Protocol layer, router, node discovery, privacy story, compute distribution.
Why it matters
This is what moves DELIGHT from a stack into a network.
OpenClaw / MCP
OpenExplains how DELIGHT can act as a backend or tool provider for MCP/OpenClaw flows.
Role
Explains how DELIGHT can act as a backend or tool provider for MCP/OpenClaw flows.
Connected with
API surface, orchestration, memory, desktop clients, tool ecosystems.
Why it matters
Makes DELIGHT usable as infrastructure, not only as one app.