This reference is currently available in English. The Cloud console remains in your selected language.
BEEOS CLOUD / DEVELOPER REFERENCE
UI and deployment architecture
Design A2UI, A2HTML, collaboration, and deployment across Cloud runtimes
BeeOS brings agent output into product applications through structured UI, shared state, and scoped data channels. Keep rendering and authority separate: an agent may describe a UI, but the product app decides what to display and which actions to allow.
| Capability | Integration boundary | Developer responsibility |
|---|---|---|
| A2UI | Structured Canvas state and agent UI events | Validate components and user actions |
| A2HTML | Agent-produced HTML artifact rendered in a sandbox | Sanitize or sandbox output; restrict scripts and origins |
| Yjs | Shared document state | Authorize collaboration and persist state |
| WebRTC viewer | Remote video and input | Exchange scoped signaling descriptors |
| ACP and terminal | Interactive runtime streams | Connect using issued transport descriptors |
| Multi-cloud and local runtimes | Control plane plus regional execution | Query providers, regions, and templates at deployment time |
A2HTML rendering boundary
A2HTML describes a rich HTML output path, not a Server SDK method. The agent produces an artifact, the product backend authorizes its retrieval, and the app renders it in an isolated frame with a restrictive content security policy. Do not give generated HTML access to product session tokens, bsk_ keys, or a privileged parent window. Treat links, forms, navigation, script execution, and cross-origin requests as explicit product decisions.
Use files for artifact transport and data channels for live updates. A2UI is the structured Canvas path; choose it when the app needs typed actions and state instead of arbitrary markup.