Skip to main content
VoiceGateway ships a command-line interface called voicegw. Its commands are documented across five nav tabs (Agents, SFU, SIP, Manage & Deploy, Reference), grouped by what they’re for rather than by CLI structure. This page is the one flat lookup surface for all of them.

Installation

Every voicegw subcommand needs the livekit extra: the CLI package imports the LiveKit admin client at module load, regardless of which command you run. serve, start, dashboard, and mcp also need dashboard (FastAPI, uvicorn). See Installation for the full extras matrix (livekit, pipecat, dashboard, collector) and every install variant (curl-bash, pipx, uv, Docker, source).

Commands

Admin and operator commands without a reference page yet

These exist and work; they don’t have a dedicated docs page in this tab yet. voicegw check also has a hidden, deprecated alias smoke-test that behaves identically; it’s omitted from --help.

Global behaviour

  • Running voicegw with no arguments displays the help menu.
  • Most commands accept --config (-c) to specify a custom path to voicegw.yaml. If omitted, the gateway searches in this order: ./voicegw.yaml, ~/.config/voicegateway/voicegw.yaml, /etc/voicegateway/voicegw.yaml. The VOICEGW_CONFIG environment variable is used instead of that search when --config is not passed.
  • Commands that need cost or log data require cost_tracking.enabled: true in the config (which activates the SQLite backend), or the VOICEGW_DB_PATH env var pointing at a database path.
  • The CLI uses Rich for formatted terminal output (tables, panels, coloured text).

Quick start

For the full first-run walkthrough see Get started.