Kimi Code

Use the current Kimi Code CLI from Happier through kimi acp in your project directory.

Requirements

• Current Kimi Code 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/kimi-code/install.sh | bash
kimi --version

Windows (PowerShell):

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

On Windows, install Git for Windows first. If Git Bash is outside its default location, set KIMI_SHELL_PATH to its bash.exe, as described in the official installation guide.

Local authentication in Happier

Kimi supports launching its native setup/login flow from:

• Settings → AI & Agents → AI backends → Kimi

Happier opens the native kimi login flow 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

• Kimi advertises list, load, fork, close, delete, and cancellation in its ACP capability reference. Happier consumes supported methods through its shared ACP runtime; advertised vendor methods do not imply a dedicated control in every Happier client.
• When creating a new session, the Resume field can browse session IDs reported by kimi acp through ACP session/list, filtered to the selected directory, and use one as the session to resume. Those entries are resume-only. Listing them does not establish that Kimi's interactive terminal uses the same IDs, and Happier does not provide live takeover, writer safety, transcript following or import, or terminal attachment for them. When the live Kimi ACP connection also advertises session/delete, the resume picker offers a confirmed delete action for the provider-owned candidate. This does not delete a persisted Happier session.
• Models come from the active ACP session. Happier does not translate them into top-level Kimi flags.
• MCP servers use standard ACP descriptors, including stdio, HTTP, and SSE transports supported by Kimi.
• Permission-mode mappings are not advertised until they have authenticated live proof.
• Tool calls are normalized to canonical Happier tool renderers.

Update an existing current installation with:

kimi upgrade

Troubleshooting

If Kimi is not detected:

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

Legacy kimi-cli detected

The retired Python kimi-cli has a different ACP capability shape and is not launched as current Kimi Code. Install the current CLI, then run this migration yourself:

kimi migrate

Happier never runs migration automatically. An explicit HAPPIER_KIMI_PATH is still capability-classified; it does not bypass this check.

Related

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