Provider Commands
Theomni providers command group manages AI and agent provider connections. Providers define how Omni routes messages to AI backends — each provider has a schema type, connection config, and optional agent resources.
Provider Schemas
omni providers list
List all providers.
omni providers get
Get full details of a provider.
omni providers create
Create a new provider.
Common Options
Claude Code Options
Genie Options
OpenClaw Options
Examples
omni providers update
Update a provider’s configuration.
Schema-specific options (
--project-path, --agent-name, --target-agent, etc.) are also available on update.
omni providers delete
Delete a provider.
omni providers test
Test a provider’s health and connectivity.
omni providers setup
Interactive setup wizards that guide you through creating a provider with all required configuration.
omni providers setup openclaw
Set up an OpenClaw provider — generates keypairs, pairs the device, and creates the provider.
omni providers setup genie
Set up a Genie provider — configures Claude Code team inbox integration.
Agno Resource Listing
For Agno providers, you can list remote resources:Handoff payload (Gupshup)
When a Gupshup provider triggers a human handoff viaPOST /v2/messages/handoff, the request body now uses structured fields. The legacy extra_info is still accepted but new integrations should send dadosLead and motivoHandoff.
dadosLead and extraInfo are sent, dadosLead wins; the legacy field is silently ignored. motivoHandoff is appended to the Gupshup notification only when present.
The
handoffFields object maps directly onto Gupshup template variables. Keys you don’t define in your Gupshup flow are dropped server-side.