Requirements
| Requirement | |
|---|---|
| Computer | A Mac with Apple silicon (arm64) or an Intel processor (x64), or a PC running 64-bit Windows 10 or 11. There's no Linux build. |
| Agent CLI | At least one supported agent CLI, installed and signed in. |
| Node.js | Not needed. It's bundled with the app. |
| Task tools | If your agents' work uses git, npm, or other tools, install those too. |
| Whyve | Not a separate install. It's bundled with the app. |
Supported agent CLIs
| CLI | Minimum version | Execution modes |
|---|---|---|
| Codex CLI | 0.154.0 | automatic, protected |
| Claude Code CLI | 2.1.260 | automatic, protected |
| Gemini CLI | 0.60.0 | automatic |
| OpenCode | 1.18.31 | automatic |
| GitHub Copilot CLI | 1.0.85 | automatic |
| Kimi Code | 2.1.1 | automatic |
| Qwen Code | 0.24.6 | automatic |
| Cursor CLI | 2026.9.26 | automatic |
| Antigravity CLI | 1.1.25 | automatic |
For CLIs other than Codex and Claude Code, Howse can't list models, so type the model name yourself.
How Howse finds your CLI
Howse checks a fixed list of locations that desktop apps can see. On Windows, it looks for claude.exe, codex.exe, or npm's .cmd launchers in three places: your PATH, %USERPROFILE%\.local\bin, and %APPDATA%\npm. To use a specific binary, set its environment variable, such as HOWSE_CODEX_BIN or HOWSE_CLAUDE_BIN. If that path doesn't work, Howse won't fall back to a different binary.