TEXT.PARTS / AGENT RUNTIME
Build it. Use it. Keep the same file.
A JSON recipe chooses the interface. UI SDK makes its components understandable to agents. The host supplies editing, file sync, and Dots permissions.
Layout + theme→text.parts
Real app components↔UI SDK + WebMCP
Read + act→Host controller
Files + sync + access
Try the actual runtime
Synthetic content · stays in this tab · Browser WebMCP unavailable; the local bridge still works
One foundation, two agent paths.
Create: discover the catalog, generate a constrained JSON layout, validate it, then preview it against the current layout revision. Save it through the existing file flow when ready.
Use: UI SDK exposes component state and allowed actions through snapshot, query, and act. The writing adapter currently supports generated note titles and text editors. Read-only controls and host permission checks still apply.
Collaborate: the host owns the active document, persistence, sync and Dots group access. A layout cannot grant access, publish content, or create a second copy of the file. This sandbox does not create a collaboration session.
Studio WebMCP tools
text_parts_catalog— components, contracts, layout instructions.text_parts_layout— current recipe and revision.text_parts_validate— validate without changing the interface.text_parts_preview— apply a validated local preview with a revision check.
Other app parts remain available in the source catalog. They gain direct agent actions as their runtime adapters are implemented.