ClavueClavue
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, Clavue GUI, and web Chat.

When to use the TUI

Choose TUI when you want maximum keyboard density on a single agent stream. Choose Clavue GUI for multi-project desktop chrome (media, automations, permissions). Choose imux when you need multi-pane terminals, 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, …)
  • Same binary as CLI: clavue --ui=pager / --pager

Auth

Device-code login against www.clavue.com, or export a membership API token for non-interactive runs.

npm i -g iclavue
clavue auth                 # device-code → www.clavue.com
clavue --ui=pager           # native TUI

export CLAVUE_TOKEN=...     # Account → API keys (headless)
export OPENAI_BASE_URL=https://api.clavue.com/v1
export OPENAI_API_KEY=$CLAVUE_TOKEN

Relation to CLI · GUI · imux

CLI covers one-shot commands and CI. TUI is the interactive terminal layer on the same binary and ~/.clavue. Clavue GUI is the desktop workbench that spawns the same CLI. imux is the family IDE (terminals + Agent Chat + supervisor), not a second TUI.

Next