Connector overview
Universal AI Bridge already exposes a reference creative connector and a desktop-oriented Satellite runtime, while keeping the platform itself explicit about workspace, connector type, capability metadata, and target session identity.
Public messaging stays tied to the shared connector catalog. The platform does not market unsupported connector families as current functionality.
figma
Reference connector implemented through the Figma plugin runtime. Runtime channel: Embedded plugin runtime. Proves governed in-product execution, active-file context, and explicit session targeting from a real creative surface.
satellite
Satellite-backed runtime entry point for desktop and restricted-network integrations. Runtime channel: Satellite runtime agent. Proves connector-neutral desktop and restricted-network execution through a bounded runtime instead of a plugin-only model.
The current product maturity is about governed execution and connector-neutral contracts, not about listing every future integration up front.
| Dimension | What it proves now | Why it matters later |
|---|---|---|
| Figma reference connector | In-product execution, active-context publishing, and explicit runtime registration from a real end-user surface. | Shows that product UX can stay grounded in live context instead of abstract agent orchestration alone. |
| Satellite runtime | Connector-neutral bounded execution for desktop and restricted-network environments, including host-aware actions. | Shows that the bridge can extend beyond one plugin while keeping the same policy and audit posture. |
| Future connector growth | The platform vocabulary already centers on connectorType, capability metadata, data scopes, and explicit session routing. | New connectors can fit the same transport-agnostic execution path instead of forcing a second architecture. |
The same capability metadata that powers HTTP and MCP discovery also powers the secure workspace shell. Public positioning stays aligned with that shared model instead of inventing connector-local marketing categories.
Next step
Use the docs when you want the current technical contract, or use the enterprise branch when you want a conversation about deployment fit and rollout posture.