Extend a working application

Start here after Connect your data produces a rendered result. Keep one working request as a reference while adding each capability. If a new request fails, inspect its receipt and preserve the last authorized result while correcting the cause.

Compose screens and preserve state#

Use workspaces for multiple coordinated surfaces and host-owned layouts. Read state ownership before moving a selection, focus, or a dirty draft between views. Follow custom views when built-in presentations cannot express the task, and responsive behavior to understand how available container space affects the choice.

Connect production data#

Define stable resources, then replace local fixtures with an HTTP data adapter. Check permissions and scope changes before enabling writes. Add actions through your existing business command path with fresh authorization and explicit confirmation where required.

Connect an agent or protocol#

The agent overview explains the shared request boundary. WebMCP exposes a browser session to a compatible browser agent; MCP connects an external host. The model adapter guide covers a host-owned model loop. Diagnose expired, rejected, and interrupted requests with agent recovery.

Prepare for production#

Use SSR and hydration for server-rendered hosts, including the maintained Next.js fixture. The shipping guide covers bounded data, performance, lifecycle, and accessible interaction checks. Confirm the actual browser support and support matrix for your environment; fixture results are not universal capacity claims.

Look up a contract#

Find entry points in the package map, signatures in App API, and outcomes in diagnostics. Check release notes and the migration guides before an upgrade. Contribute links to repository setup and reporting paths.