Agents and models
Qwen
Configure Qwen in Happier via ACP-backed local runtime integration.
Happier supports Qwen as a local CLI-backed provider.
Qwen Code is an experimental integration. It works and people use it daily, but its surface is younger than Claude, Codex or OpenCode and is more likely to change. What it supports today is in Agent capabilities.
Requirements
- Qwen CLI installed locally.
- Binary available on
PATH(or setHAPPIER_QWEN_PATH).
Install Qwen
Happier can install it for you:
happier install provider qwen
qwen --versionOr install manually (macOS / Linux):
curl -fsSL https://qwen-code-assets.oss-cn-hangzhou.aliyuncs.com/installation/install-qwen.sh | bash
qwen --versionWindows (Run as Administrator in CMD):
curl -fsSL -o %TEMP%\\install-qwen.bat https://qwen-code-assets.oss-cn-hangzhou.aliyuncs.com/installation/install-qwen.bat && %TEMP%\\install-qwen.bat
qwen --versionLocal authentication in Happier
Qwen supports launching its native auth flow from:
- Settings → AI & Agents → AI backends → Qwen Code
Happier opens Qwen and sends /auth for you.
Auth-status detection for Qwen is currently conservative, so Happier may still show Unknown even though the login flow is available.
For the shared user guide, see Provider authentication.
Start Qwen with Happier
happier qwenNotes
- Resume availability is session-specific in Happier and depends on valid resume metadata plus the current backend/settings.
- Model, mode, and permission behavior can still vary by installed Qwen runtime.
- Tool calls are normalized to canonical Happier tool renderers.
Troubleshooting
If Qwen is not detected:
- Verify
qwen --versionworks. - Restart Happier.
- Set
HAPPIER_QWEN_PATHif needed.
Related
- Agent capabilities — what this agent supports, generated from the manifest.
- Choosing an agent
- Model and engine selection
- Agent authentication