Agent Chat can use Clavue membership models (product IDs like auto / clavue-2.1 family). Local CLIs (Claude Code, Codex, Grok CLI) use their own auth.
Mixing both is normal: membership for chat/tools, CLIs for heavy implementers.
Prerequisites
- imux with Agent Chat
- Optional Clavue account for membership models
Steps
- 01
Sign in when you want membership models
Open Account from the app or www.clavue.com. Membership unlocks official models, web Chat/Imagine, and the OpenAI-compatible API with shared quotas.
- 02
Pick a product model, not a vendor cascade name
In Agent Chat, choose product IDs (auto, clavue, clavue-2.1-*). Public UI should not promise raw upstream cascade strings. See /docs/models-guide and /docs/public-surface-policy.
- 03
Watch usage and errors
Quota errors point to upgrade/top-up actions. Prefer Account → Usage for resets. API clients should handle membership error codes from the catalog.
- 04
Prefer local CLIs for long implementers
For multi-hour coding agents, run Claude Code/Codex in terminal panes. Use Agent Chat for orchestration, review, and membership tools—not as the only place every tool runs.
FAQ
Is BYOK supported?
Desktop may support provider keys for some paths; membership official models are the default Clavue path. Follow in-app provider settings and never commit keys.
Same models as chat.clavue.com?
Official catalog is shared by design. Surfaces differ (tools, workspaces).