CLI Reference

Connect a harness with fireconnect <harness>. Use off to restore its previous settings, status to inspect the connection, and help to see harness-specific options. The optional on command remains available for backward compatibility. For model selection, see Open Models. For router behavior and account-level credentials, see FireRouter and Provider Keys. For cross-harness support, see Harness Compatibility.

Global commands

fireconnect login        # Sign in: browser (creates a key) or paste a key you have
fireconnect logout       # Clear stored Fireworks credentials
fireconnect status       # Sign-in state, environment, storage, and harness key sources
fireconnect configure    # Set the provider, Foundry endpoint, or Anthropic and OpenAI keys
fireconnect model list   # Browse the global Fireworks coding model catalog (alias: fireconnect models)
fireconnect claude demo  # Race two models in live Claude Code sessions
fireconnect upgrade      # Update FireConnect (curl/git install only)
fireconnect uninstall    # Disable all harnesses, restore configs, remove CLI
fireconnect help         # Show help
fireconnect --version    # Print the installed CLI version (-V also works; --json for machine-readable)

Global options for model list:

fireconnect model list --search glm    # filter by name
fireconnect model list --refresh       # bypass the 1-hour cache
fireconnect model list --json          # machine-readable output

The list opens with the smart routers, which pick a model per user turn. auto balances cost and quality across open models. auto-instant is latency-first. If your account disables fast models, stay on auto. Run fireconnect help for the overview, or fireconnect claude help (and similarly for other harnesses) for harness-level options.

Flag	Use when
`--paste`	Skip the browser chooser and paste a key at the prompt
`--api-key fw_...`	Sign in with a key directly (no prompt)
`--with-token`	Read a key from stdin (handy in CI): `echo "$FIREWORKS_API_KEY" \| fireconnect login --with-token`
`--account <id>`	Enterprise SSO sign-in (same account id as `firectl signin`)
`--force`	Replace an existing stored key without a confirmation prompt
`logout --revoke`	Clear local credentials and revoke the machine key on Fireworks

fireconnect status --json   # machine-readable sign-in and key-storage details

For direct Fireworks routing, ~/.fireconnect/config.json usually stores a secret-store reference or {env:FIREWORKS_API_KEY}, not the key itself. Run fireconnect status to see which backend is active. FireConnect may store an Anthropic or Azure key literally when you pass --api-key. It writes files containing literal keys with mode 0600.

Configure a provider

fireconnect configure sets the default provider, Foundry endpoint, Azure key, or shared Anthropic and OpenAI keys for FireRouter. It does not store your Fireworks API key. Use fireconnect login for that.

fireconnect configure \
  --provider azure \
  --base-url "https://YOUR_RESOURCE.services.ai.azure.com" \
  --api-key $AZURE_API_KEY

fireconnect configure --anthropic-api-key sk-ant-...
fireconnect configure --openai-api-key sk-...
fireconnect configure --provider fireworks

In configure, --api-key is the Azure endpoint key and requires --provider azure. For Fireworks keys, use fireconnect login.

Providers

Provider	Where inference runs	Credential
`fireworks` (default)	Fireworks gateway	Fireworks API key
`azure`	Fireworks on Microsoft Foundry	Azure API key

See Foundry for Coding Harnesses for current compatibility. Connections use the configured provider by default. To use Foundry for one command, pass --azure, or pass both --base-url and --api-key.

Harness commands

CLI harnesses support connect, off, status, and help. Claude Code also supports usage, live, and demo. Claude Desktop (macOS) uses fireconnect claude-desktop on, off, and status, plus mcp list, mcp add, mcp remove, and mcp sync for connectors. IDE commands require you to quit the app before FireConnect writes settings. status is read-only. See Coding Harnesses for app-specific commands and restart rules.

Choose a model or router

Use --model <id> to select a model. The rest of the catalog stays in the picker. In Claude Code, the model becomes your default and appears in /model; native tiers remain unchanged unless you pin them.

fireconnect model list --search glm
fireconnect claude --model glm-fast-latest
fireconnect opencode --model glm-fast-latest

In Claude Code, pin a tier slot with --opus, --sonnet, --haiku, --fable, or --subagent. Pins persist when you run fireconnect claude again. Pass native to release a slot:

fireconnect claude --sonnet deepseek-flash-latest --subagent deepseek-flash-latest
fireconnect claude --sonnet native

On Microsoft Foundry, pass the Azure deployment name, such as FW-GLM-5.2. When using a model router:

Pass any router ID with --model, such as firerouter, firerouter/opus, firerouter/claude-opus-5-5, or a custom route such as firerouter/opus/glm-5p3.
Pass --anthropic-api-key sk-ant-... when the route contains a Claude family alias or Anthropic model ID and the harness must forward a local key.
Optional: pass --openai-api-key sk-..., or save it once with fireconnect configure, so FireRouter can reach GPT models. FireConnect sends it on bare firerouter and on routes that name a GPT model ID. Harnesses that cannot send a local key, such as Cursor IDE, reject the flag.
Pass --routing-preference <level> on supported harnesses. Claude Code accepts this flag when a Claude slot is set to bare firerouter.

API key resolution

After fireconnect login, run fireconnect <harness> without --api-key. The flag on connect commands is an optional override (CI, rotation, or a key you have not stored yet). For the normal path, sign in once and omit it. Direct Fireworks routing (--provider fireworks)

Explicit --api-key on the connect command
FIREWORKS_API_KEY environment variable
Stored credential referenced by ~/.fireconnect/config.json

When FIREWORKS_API_KEY is set, login uses it without storing a copy. Unset it before login --api-key, --with-token, or browser sign-in. When no global key resolves, connect can reuse a Fireworks key already stored in that harness’s config. Claude Code status and usage also read its connected key from ~/.claude/settings.json. Fireworks on Microsoft Foundry (--provider azure)

Explicit --api-key
Existing Azure key stored by the harness
Literal Azure key saved by fireconnect configure
AZURE_API_KEY, including a saved environment reference

Nexus

Connect

Choose models

Operate

Reference

Global commands

Configure a provider

Providers

Harness commands

Choose a model or router

API key resolution

​Global commands

​Sign in and key storage

​Configure a provider

​Providers

​Harness commands

​Choose a model or router

​API key resolution

Global commands

Sign in and key storage

Configure a provider

Providers

Harness commands

Choose a model or router

API key resolution