imuximux
AI workbench for macOS

Clavue TUI

The TUI is for operators who live in the terminal: interactive agent sessions, plan/apply loops, and headless-friendly workflows without opening the full imux chrome. It shares Clavue membership, models, and API identity with the IDE and web Chat.

Install

Install the global npm package clavue-v1, then log in and confirm the binary name is clavue-v1 (not the imux-bundled icc).

npx -y clavue-v1
# or
npm i -g clavue-v1
clavue-v1 --version
clavue-v1 auth login

When to use the TUI

Choose TUI when you want maximum keyboard density on a single agent stream. Choose imux when you need multi-pane agents, Git sidebar, browser verify, or Mission Control.

  • SSH into a remote box and keep the agent UI local to that shell
  • Scriptable start + interactive takeover mid-task
  • Same official model ids as API (auto, clavue-2.1, …)
  • Cloud model routing at router.clavue.com — same membership login; pull with /provider router pull --apply

Auth

Interactive sessions use device login (clavue-v1 auth login). Headless CI and scripts should use a membership API key from Account → API keys — same token works with OPENAI_BASE_URL for OpenAI SDKs.

  • Device login — clavue-v1 auth login opens a browser flow on www.clavue.com; best for daily TUI use
  • API token — export CLAVUE_TOKEN for scripts; no browser needed
  • Same account as Chat, imux official models, and api.clavue.com/v1
# Interactive
clavue-v1 auth login

# Non-interactive / CI
export CLAVUE_TOKEN=...   # Account → API keys
export OPENAI_BASE_URL=https://api.clavue.com/v1
export OPENAI_API_KEY=$CLAVUE_TOKEN

Relation to CLI

CLI covers one-shot commands, CI, and imux socket control (icc). TUI is the interactive session layer on top of the same platform auth and models. Headless scripts should prefer CLI/API; humans in a terminal prefer TUI.

Next