Generate and edit inside Chat.
Product
Open and ask.
Product
Native macOS command center.
IDE
Desktop agent workbench.
Mac · Windows
Stable ids, built as products.
auto · 2.1 · Pro
The same account in a terminal.
npm clavue-v1
A standalone bot surface.
Product
Two phone products. Distinct jobs.
Clavue · imux
Hosted working copies. Origin stays on GitHub or Origin.
Working copies
What do you want to know?
Chat, workbench, terminal. One account.
Chat, imux, and CLI. Distinct jobs. Shared membership.
One job
One account. Keep the jobs distinct.
01
One product, one job
Chat, Bot, GUI, CLI, imux, and the two Mobile apps keep distinct bundles. Chat lives on chat.clavue.com.
02
One membership
Account lives on /account. Calls go to api.clavue.com.
03
Working copies are not origin
Push returns to GitHub or Cursor Origin.
How work moves
Emit a card. Stop. Wait for a human.
01
CI / PR wake
Supervisor reads already-fetched sidebar checks, emits an approvable card, and stops. Not a webhook.
02
Queue is visible
Task phase is queued / claimed / running. It does not replace waiting-approval on the phone.
03
One card schema
IDE inbox and imux Mobile share the card. Decide on the Mac; the phone is read-only this slice.
Approve records the decision. It does not start another silent loop. Bot decide/API is not in this repo.
What we don’t add
- A seventh login or a seventh billed product
- A third git review host
- A meeting bot or a second ticket tracker
- “No prompts / no scheduling” as a brand claim
Models
Built as products.
Stable product ids. The same names in Chat, imux, CLI, and the API.
Model catalogAPI
A standard API.
OpenAI-compatible chat completions. Membership keys. Shared quota with web Chat and imux.
curl -s https://api.clavue.com/v1/chat/completions \
-H "Authorization: Bearer $CLAVUE_TOKEN" \
-d '{"model":"clavue-2.1",
"messages":[{"role":"user",
"content":"Hello"}]}'Start now.
A free account includes daily quota. Alipay / WeChat. One login on desktop and web.