@cef-ai/widget-runtime
v0.2.1
Published
Browser runtime for CEF widgets. It boots from `window.WidgetSandbox.manifest`, resolves the user's identity, exposes `window.WidgetRuntime` (`query` / `publish` / `connect` / `connectAgent` / `agentStatus` / `identity`), and renders config-driven widget
Downloads
448
Readme
@cef-ai/widget-runtime
Browser runtime for CEF widgets. It boots from window.WidgetSandbox.manifest,
resolves the user's identity, exposes window.WidgetRuntime
(query / publish / connect / connectAgent / agentStatus / identity),
and renders config-driven widget kinds (record / list / dashboard / submit /
conversation / composite) plus custom widgets. It also carries the audio
capture/upload path. The runtime reads a manifest; the @cef-ai/cli build
tooling builds one.
The esbuild IIFE build emits dist/widget-runtime.js (the browser bundle) and
dist/widget.html (the shell); tsc emits the library entry (dist/index.js)
for consumers that import the helpers directly.
Identity (multi-source)
The runtime resolves a signing identity from the best available source:
- Embedded (host): when iframed by the Cere Vault, it signs through the host's postMessage sign-bridge.
- Standalone (interactive wallet): when there is no responding host — the
widget is opened top-level via a direct link — it connects an interactive
Cere embed-wallet built from
manifest.wallet.{appId,env}(opens the wallet UI) and signs locally.
Both paths feed the same @cef-ai/vault-sdk client, so cubby reads, connect,
publish, and audio uploads behave identically embedded or standalone.
Build
pnpm --filter @cef-ai/widget-runtime build # esbuild bundle + tsc + fix-extensions
pnpm --filter @cef-ai/widget-runtime test