Configuration

Configure the Opta CLI with persistent settings, environment profiles, and a TUI settings menu. All configuration is stored in a single JSON file and can be managed via commands or edited directly.

Overview

The Opta CLI stores its configuration in a JSON file at ~/.config/opta/config.json. Settings control connection parameters, default model selection, provider fallback behavior, UI preferences, and more. You can manage configuration through three interfaces: CLI commands, the TUI settings menu, or direct file editing.

Config Commands

Listing Config

opta config list displays all current configuration values in a readable format. Settings are grouped by category.

connection.host     lmx-host.local
connection.port     1234
model.default       qwen3-30b-a3b
provider.fallback   true
ui.theme            dark
ui.streaming        true

Get and Set

Use opta config get to read a single setting and opta config set to update one. Settings use dot notation for nested keys.

lmx-host.local

connection.host = lmx-host.local

model.default = deepseek-r1

TUI Settings Menu

opta config menu opens an interactive terminal UI for browsing and modifying settings. This is the easiest way to explore available options and understand what each setting does.

Opta Settings
━━━━━━━━━━━━━
> Connection
    Host: lmx-host.local
    Port: 1234
  Model
    Default: qwen3-30b-a3b
    Fallback: Anthropic (enabled)
  UI
    Theme: dark
    Streaming: enabled

[Enter] Edit  [Tab] Next section  [q] Save & Quit

Config File Location

The configuration file lives at ~/.config/opta/config.json and follows the XDG Base Directory specification. On Linux, it respects $XDG_CONFIG_HOME if set.

{
  "connection": {
    "host": "lmx-host.local",
    "port": 1234
  },
  "model": {
    "default": "qwen3-30b-a3b",
    "aliases": {
      "qwen": "mlx-community/Qwen3-30B-A3B-MLX-4bit",
      "deepseek": "mlx-community/DeepSeek-R1-0528-MLX-4bit"
    }
  },
  "provider": {
    "fallback": true,
    "anthropicKey": null
  },
  "ui": {
    "theme": "dark",
    "streaming": true
  }
}

Environment Profiles

Environment profiles let you save and switch between named configuration snapshots. This is useful when you work with different LMX servers, switch between local and cloud inference, or maintain separate configs for different projects.

Profile 'home' saved.

Profile 'office' saved.

Switched to profile 'home'.\nconnection.host = lmx-host.local

Profiles:
  * home    (active)
    office

Key Settings Reference