Surface parity
Each family product has a fixed job. Accounts and api.clavue.com are shared; UI and execution hosts are not interchangeable. This page summarizes public doctrine — not a shipped-feature scorecard.
Product roles
Pick the surface that matches the task. Mixing roles (treating Bot as Chat, or GUI as imux IDE) causes wrong expectations.
- imux IDE (com.icc.app) — native Mac/Win AI IDE and command center; thick Agent Chat harness on Mac; Windows is workbench + phone-link, not full Mac harness parity
- imux Mobile (com.imux.mobile) — phone remote to desktop imux; tasks, pair, approvals; no local shell
- Clavue GUI (com.clavue.gui) — standalone Tauri agent workbench; Phone Mirror host; tool ledger
- Clavue Mobile (com.clavue.xw) — phone Chat, Imagine, Discover; opens GUI mirror
- Clavue Chat (web) — lightweight browser chat at chat.clavue.com
- Clavue Bot (com.clavue.bot) — multi-staff bots + cloud PC at /bot/
- Clavue CLI/TUI (npm clavue-v1) — terminal agent; binary clavue-v1
- Models & API — api.clavue.com/v1 for all official models
Shared cloud
One account at www.clavue.com/account. One quota across Chat, imux official models, TUI, Bot, and API. Discover catalog and connectors are shared data — surfacing differs per app.
Honest expectations
Platforms evolve at different speeds. Do not assume every desktop feature exists on phone or Windows day one.
- Windows imux — real workbench and phone-link; not every Mac Agent Chat harness primitive
- Phones — control plane or Chat; never local Ghostty terminals
- Web Chat — no imux socket or multi-pane terminal layout
- Bot — cloud PC and staff bots; not a replacement for IDE terminals
Deep dives
Per-product install and usage live in the docs tree — start from the product you actually use.