The Web UI can own a standalone runtime or attach to the terminal runtime.

​
Standalone

WebAssistantRuntime(settings, preflight=None, shared=None) creates its own:
  • Conversation.
  • Complexity scorer.
  • Browser session.
  • Approval manager.
  • Tool registry.
  • Connector registry.
  • Durable job store.
  • Trigger store.
  • Background task manager.

​
Shared

When shared is provided, the Web runtime reuses terminal-owned objects:
  • Conversation.
  • Browser session.
  • Approvals.
  • Tool registry.
  • Connector registry.
  • Job store.
  • Trigger store.
  • Task manager.
The health payload reports runtime.scope as shared or standalone.

​
Events

The browser subscribes to /api/events through server-sent events. Task events update the UI without polling.

​
Connectors

The Web UI shows up to six configured connectors with enabled state, acceptance state, and risk tier. Browser actions can run connector acceptance checks or cancel running connector jobs through authenticated server endpoints. Connector chat intents use the same runtime path as terminal connector intents. A run creates a background task and durable job, waits for exact approval when required, records logs and artifacts, and can be cancelled by connector id.

​
Redaction

Web responses redact token query strings, key-like values, OpenAI-style keys, connector destinations, connector output, and local home paths before returning capability and task data.