The address the bridge connects to — a meeting join URL/ID for meeting bridges, or a phone number for telephony bridges. Interpretation is driver-specific.
OptionalConfigurationOpaque, provider-specific connection configuration (resolved credential references, region,
bot display name, …) as a parsed JSON object. Typed as a record of unknown values rather
than any so it stays inspectable without losing type-safety at the boundary; the driver
narrows the fields it understands. Never carries inline secrets — credentials resolve through
MJ's credential system upstream and arrive here already resolved or as references.
OptionalContextThe MJ user the bridge session runs as. Every bridge session is owned by a user and fully audited; the driver uses this for any server-side operations that require a context user.
The provider's SupportedFeatures — the capability flags the engine and the driver's
RequireFeature guard gate on. Sourced from the provider metadata row's typed
SupportedFeaturesObject accessor.
The provider's display name (e.g. 'Zoom', 'Twilio'), used in capability-error messages
and logging.
The set of host services a bridge driver sees while running.
The engine (
AIBridgeEngine, server package) constructs this and hands it to BaseRealtimeBridge.Connect. It is deliberately small: a driver should depend only on what it truly needs, and everything richer (the realtime session, the channel plane) is wired by the engine AROUND the driver, not handed into it. This keeps drivers thin and platform-focused.