While the product docs cover imux, Clavue CLI/TUI, models, and the OpenAI-compatible API in depth, this page collects the most common questions about billing, usage limits, accounts, and everyday product use — website, apps, CLI, and API.
Where you manage it depends on where you subscribed:
Refunds depend on local payment rules and purchase channel:
No — prepaid boost packs and unused top-up credits are non-refundable once purchased, unless required by law. Plan included weekly/monthly quotas are not cash balances.
Not necessarily. Unexpected charges are often a higher plan tier (×5 / ×20) or annual billing, not pure pay-as-you-go API. Check Account → orders and usage before disputing. Contact support with the order number so we can confirm what was charged.
Membership is tied to the Clavue account you purchased with. Sign in with the same account everywhere (web, imux device login, API key).
Paid and Free plans share one membership quota across products — imux Agent Chat, Clavue Chat (web), CLI/TUI agent turns, and the OpenAI-compatible API — so you are not managing separate wallets per surface.
Each successful model turn consumes from the matching pool. Different products cost different compute: a short chat uses little; long agent loops, search, and image generation use more.
Paid features that need official models pause until reset or you add headroom. You can:
Boost packs add extra usage after included plan quota is exhausted. They are account-level and shared across web Chat, imux, CLI, and API.
Upgrade when you regularly exhaust weekly/monthly included usage — ×5/×20 give far more headroom at better value. Use boosts for occasional spikes.
On www.clavue.com use email OTP, password (if set), or Google where enabled. imux and Clavue CLI use device-code login that opens the browser to approve.
Update profile email from Account when available, or contact support if you lost access to the old address. Linking a new Google sign-in does not always merge old quota — verify before creating a second account.
Contact support immediately with user id / email and proof of ownership. Support can revoke sessions and API keys, cancel renewals, and lock the account. Compromised usage may not be refundable when the purchase location matches your history.
Use Account settings delete flow when available, or request deletion via support. Deleting removes membership access, API keys, and Chat history retention subject to legal hold. Restore windows (if any) are stated in the product UI at deletion time.
Sign out and back in, retry device login, clear site cookies for clavue.com, try another browser, and confirm system clock is correct. On imux, update to the latest stable build and re-run device approve.
Keep names clear:
Pick one primary surface per task:
Official product ids (membership + API): auto, clavue, clavue-2.1, clavue-2.1-fast, clavue-2.1-pro, clavue-2.1-rev, clavue-2.1-search, clavue-img. Non-official model strings return official_models_only.
Use https://api.clavue.com/v1 (OpenAI-compatible chat completions and models list). Membership auth and device codes live on https://www.clavue.com. imux downloads and Sparkle feeds use https://www.iccjk.com.
No. The local Unix socket (icc CLI /integrations) controls the running imux app on your Mac. The HTTP API calls official models on Clavue servers with your membership token. Most automation uses both: socket for workbench control, HTTP for model inference.
In web Chat and imux Agent Chat, use the attachment control next to the composer (or drag-and-drop on web). imux can also @-mention workspace files and apply reviewable diffs without uploading to the cloud when work stays local.
Common documents and code (PDF, TXT, MD, CSV, JSON, source files) and images (PNG/JPEG/WebP) are supported on web Chat. imux local tools can read/write project files under workspace policy. Very large binaries should stay on disk and be referenced by path in the IDE.
Delete conversations from Chat history UI when available. imux conversation tabs can be closed/deleted in-app. Account deletion removes cloud history subject to legal retention. Local project files are never deleted by Clavue unless you run tools that modify them.
Education plans offer lower pricing after qualification. Teachers can create passworded student seats for a class (subject to seat limits). Usage multiplies match paid ×1 for qualified education accounts unless stated otherwise.
Open /education, submit the verification flow, and wait for approval. Abuse (account sharing, resale) can revoke education pricing.
Use official model clavue-img in web Chat, imux Agent Chat, or the API. Replies typically include Markdown image links that products render inline.
Safety systems always apply. Enabling any creative/NSFW preference does not disable moderation. Prohibited categories include child sexual content and non-consensual intimate imagery. Support cannot provide full rule lists; repeated abuse may lead to enforcement.
Yes — images draw from the premium pool and cost more compute than a short chat turn. Prefer text models for pure Q&A.
Yes for Chat Completions and models list at https://api.clavue.com/v1. Use standard OpenAI Python/Node SDKs with base_url / baseURL pointed at Clavue.
pip install openai or npm install openai. No proprietary Clavue SDK is required. See /docs/sdk for full multi-language first-request samples.
Set stream: true on chat completions. Protocol matches OpenAI SSE. Details: /docs/streaming.
Yes — OpenAI tools schema on the API, Official MCP web_search, and imux native tools. See /docs/function-calling.
Treat production prompts as sensitive. Training/improvement policies are disclosed in Privacy and product controls. Full security FAQ: /docs/security.
Immediately disable or delete the key in Account → API keys, create a new one, update deployments, and review Usage for unexpected traffic.
Include: account email, surface (imux / web Chat / CLI / API), OS/browser version, imux version if applicable, and the full support Ref line (requestId + code) from any error. Attach screenshots or a minimal repro.
Start with Quickstart and product surface docs (IDE, CLI, TUI, models, membership, API). For usage anomalies, open Account → Usage and confirm plan reset times before opening a ticket.
