Toolchain

qmt, qmtcode, and qmtui: one installer, three jobs.

A practical guide to the three command-line tools installed with QueryMT.

The installer gives you three binaries because QueryMT separates provider operations, agent runtime, and terminal interaction. Use them together, or pick the one that matches what you are doing right now.

Core CLI

qmt

The general QueryMT command-line interface for direct model and provider work.

  • Run quick chat, completion, and embedding flows.
  • List and configure providers, models, tools, and policy files.
  • Handle local secrets, auth, and service commands without starting an agent UI.
Agent runtime

qmtcode

The config-driven agent runner for coding agents, dashboards, API servers, ACP integrations, and mesh nodes.

  • Run a TOML agent profile or the embedded default coder profile.
  • Start ACP stdio, local API, or browser dashboard modes.
  • Join or host mesh sessions so agents can collaborate across machines.
Terminal UI

qmtui

A Rust terminal interface for operating QueryMT agent sessions from your shell.

  • Connect to a running qmtcode API server or auto-start one locally.
  • Switch sessions, modes, models, and thinking display from a TUI.
  • Persist interface preferences in ~/.qmt/tui.toml and session cache under ~/.cache/qmt/.

Which one should you run?

Goal Run
Test a provider or send a quick model request qmt
Run an agent from a TOML config qmtcode path/to/agent.toml --dashboard
Use the browser dashboard qmtcode --dashboard
Expose an agent server for terminal or custom UIs qmtcode --api
Work with sessions from the terminal UI qmtui
Integrate with an editor or ACP client qmtcode --acp
Join or host an agent mesh qmtcode --mesh

How they fit together

Use qmt when you want the core CLI: provider setup, direct model calls, embeddings, secrets, auth, and other one-shot operations.

Use qmtcode when you want an actual agent process. It loads profiles from TOML, owns the session runtime, exposes ACP/API/dashboard transports, and can participate in a mesh.

Use qmtui when you want a terminal-first interface on top of that runtime. It connects to qmtcode, or starts it for you, then gives you a focused session UI without opening a browser.

Common starting commands

qmtcode --dashboard
qmtcode --api
qmtcode path/to/agent.toml --dashboard
qmtcode --mesh
qmtui

Where to go next

Browse the showcase Why config matters Provider sharing