Browser surface
apps/chat-web owns the hosted workspace UI, session navigation, runtime panels, and artifact presentation without duplicating persistence logic.
technical architecture
A browser, gateway, worker, and runtime-adapter control plane.
onesagent separates public browser UX from durable control-plane state and runtime execution. The gateway owns sessions and SSE, while workers prepare scoped workspaces and dispatch runtime jobs.
Gateway control plane
apps/chat-gateway owns browser-facing APIs, session history, jobs, runs, uploads, SSE delivery, and scoped runtime settings.
Worker execution plane
apps/worker-cluster prepares workspace custody, dispatches runtime adapters, collects artifacts, and keeps execution separate from the browser surface.
why this page exists
What teams need to understand.
Each page focuses on the actual workflow question: browser access, persistent sessions, durable jobs, artifacts, replay, runtime support, and team-scoped workspace custody.
SSE event streaming and replay
Session-scoped persistent workspaces
Per-job isolated workspaces
Runtime model settings
Provider configuration projection
Artifact metadata stability
FAQ
Direct answers for searchers.
Where does runtime execution happen?
Runtime execution belongs in the worker-cluster through adapter-mediated lanes, not in the browser or gateway.
Why keep the gateway separate?
The gateway is the durable control-plane boundary for sessions, jobs, persistence, uploads, and browser-facing event streams.