Architecture
The runtime planes, durable identities and evidence-based operation flow.
Runtime planes
| Plane | Responsibility |
|---|---|
| Chat runtime | Provider adapters, coding tabs, agent tabs, streaming output and command extraction. |
| Extension | Userscript registry, Router Core, Operation Graph, adapters, protection, permissions and UI. |
| Local node | Authenticated IPC, filesystem, process execution, models, MCP, artifacts and libp2p. |
| Peer data | Encrypted capability exchange, invocation, result and artifact transport. |
| Cloud control | Optional registration, rendezvous, relay, project rooms, releases and provenance. |
One operation, one identity
Every effect receives a durable operationId. Browser tabId values are only transport hints; stable tabInstanceId, agentId, endpointId, generations and document epochs drive recovery.
Evidence before success
A click or dispatched event is not success. Prompt insertion, submission, attachment, script mutation, installation and remote invocation must return observed postcondition evidence. Lost confirmation produces UNKNOWN_OUTCOME; non-idempotent work is observed before retry.
origin → router → capability decision → adapter/endpoint
→ effect attempt → observed postcondition → signed result
↘ unknown outcome → state observation → resume or retry