Configuration

July 31, 2026 · View on GitHub

The plugin is configured by the standard ovos-plugin-manager config block.

{
  "ovos-messagebus": {
    "autoconnect": true,
    "host": "127.0.0.1",
    "port": 8181,
    "timeout": 30,
    "source_name": "messagebus_chat_agent"
  }
}

Keys

KeyTypeDefaultDescription
autoconnectboolFalseIf True, the plugin opens its own MessageBusClient on init. If False, you must inject a connected bus via OVOSMessagebusChatAgent(bus=...) or .bind(bus).
hoststr127.0.0.1OVOS messagebus host. Only consulted when autoconnect is True.
portint8181OVOS messagebus port. Only consulted when autoconnect is True.
timeoutint30Per-utterance wait in seconds. Refreshed every time a speak message arrives, so a multi-speak response does not time out mid-stream.
source_namestrmessagebus_chat_agentValue written to context.source on the outgoing recognizer_loop:utterance. OVOS routing rules that exclude messagebus_chat_agent can use this.

Bus injection

If you already have a connected MessageBusClient, inject it directly. This is the recommended path for tests, multi-tenant servers, and any deployment that manages its own bus lifecycle:

agent = OVOSMessagebusChatAgent(bus=existing_bus, config={"timeout": 15})

If neither bus= is supplied nor autoconnect is set, the agent has no bus and continue_chat raises RuntimeError. Call .bind(bus) later to attach one.

OVOS config interaction

The plugin does not read mycroft.conf directly. All configuration flows through the config dict passed to __init__.


← Architecture · Home · Message flow →