Kimi

Happier supports Kimi as a local CLI-backed provider.

Kimi 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

Kimi CLI installed locally.
Binary available on PATH (or set HAPPIER_KIMI_PATH).

Install Kimi

Happier can run the vendor installer for you:

happier install provider kimi

Or install it yourself (macOS / Linux):

curl -LsSf https://code.kimi.com/install.sh | bash
kimi --version

Windows (PowerShell):

Invoke-RestMethod https://code.kimi.com/install.ps1 | Invoke-Expression
kimi --version

Local authentication in Happier

Kimi supports launching its native setup/login flow from:

Settings → AI & Agents → AI backends → Kimi

Happier opens Kimi and sends /setup for you.

Auth-status detection for Kimi 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 Kimi with Happier

happier kimi

Notes

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 Kimi runtime.
Tool calls are normalized to canonical Happier tool renderers.

Troubleshooting

If Kimi is not detected:

Verify kimi --version works.
Restart Happier.
Set HAPPIER_KIMI_PATH if needed.

Agent capabilities — what this agent supports, generated from the manifest.
Choosing an agent
Model and engine selection
Agent authentication