System architecture

How the web application, control plane and Host work together.

Three cooperating parts

The web application presents Workspaces, Projects, Tasks, Sessions and results. The cloud control plane manages membership, authorization, conversation records, integration state and delivery requests. The paired Host provides repository access, worktrees, editable files, provider execution and live previews.

A request path

A person sends a request from the web app. The control plane checks current access and routes the command over a secure outbound connection to the authorized Host. The Host runs the selected provider in an isolated execution environment and streams events back. Large file and result transfers use HTTPS; the live control channel carries commands, events and metadata.

Where state lives

Conversation records are durable cloud state. Working source files and live previews belong to the Host’s Task work area. Provider-native state is private to its Session. Successfully uploaded result artifacts have their own object identity and access metadata. These are separate stores with separate lifecycles.

Delivery stays explicit

GitHub and Vercel integration credentials and delivery requests are managed by the control plane, while trusted source capture happens at the Host. These integrations are available only in selected, configured Workspaces. An external push, Page publication or deployment is an intentional action with an attributable result.