Skip to content

CLI

CLI

ProxAI keeps CLI flags intentionally small. They are for temporary overrides such as local testing or one-off route changes. Long-lived behavior belongs in config.toml.

Executable

proxai.exe

Runtime flags

proxai \
  --config <path> \
  --upstream <url> \
  --api-key <key> \
  --port <port> \
  --log-level <level> \
  --log-format <human|json> \
  --route-override ROUTE.FIELD=VALUE

Flag	Purpose
`--config`	Path to a config file (defaults to app dir `config.toml`)
`--upstream`	Temporarily override the `openai_responses` default provider upstream URL for this run
`--api-key`	Temporarily override the `openai_responses` default provider API key for this run
`--port`	Override the local proxy listen port
`--log-level`	Override log level
`--log-format`	Override log output format (`human` or `json`)
`--route-override`	Temporarily override a named `[[routing.routes]]` field

Route overrides

--route-override can be repeated. Supported override fields are request_protocol, match_kind, model_pattern, provider, and upstream_model. Use an empty value to clear optional fields.

proxai --route-override minimax_m3_chat.model_pattern=MiniMax-M3-preview \
       --route-override minimax_m3_chat.upstream_model=MiniMax-M3

Capture subcommand

proxai capture status
proxai capture enable  [inbound-request|provider-request|upstream-response|outbound-response]
proxai capture disable [inbound-request|provider-request|upstream-response|outbound-response]

These persist local capture defaults. For one-shot debugging you can also use single-run flags:

proxai --capture-inbound-request
proxai --capture-provider-request
proxai --capture-upstream-response
proxai --capture-outbound-response

For what each capture phase means, see Observability. For default endpoints and other runtime limits, see Defaults and Limits. MCP is a local-only control surface — see Behavior Contract C5 and C6.