Webview hosts

These replacement contracts belong to PS-806’s 0.44 implementation. Extension adoption requires the published 0.44 SDK and matching workbench. Older releases do not provide these replacements.

Workbench hosts share capability validation and response shapes. Supply service adapters when embedding extension webviews.

Create capabilities

Import createExtensionWebviewHostCapabilities and ExtensionWebviewHostAdapters from @pstdio/workbench/extensions. The factory provides every supported host capability name. Each handler validates its parameters before invoking its service. The factory wraps results such as { outcome }, { location }, and { name, value } consistently.

createWorkbenchWebviewHostAdapters binds a workbench’s commands, navigation, page parameters, placement, preferences, notification display and terminal. Extension contribution registration adds project-aware command execution, files and artifact reads. Pass additional services using createWebviewHostAdapters; do not build or override a capability registry.

The dashboard binds HTTP-backed services. The testbench binds its preview services through the same contribution registration. Services without a backing implementation stay undefined. Their handlers throw WebviewHostCapabilityError with code: "unsupported" and data: { capability }. Invalid parameters use code: "invalid_params" with validation issues.

Frame lifetime

Pass the frame’s stable hostEvents publisher to the adapters. The factory owns command abort signals and the stream manager. Disconnect aborts pending commands and streams. Recreating the adapters during a React render keeps the stream manager for that publisher.

A stream preserves its final command outcome. It never retries a disconnected command. A frame accepts at most 16 active streams and 8 MiB of unread data; acknowledgements release buffer capacity. These limits apply to all hosts.

See extension webviews for author-facing APIs.