Happier Docs
Providers

Kimi

Configure Kimi in Happier via ACP-backed local runtime integration.

Happier supports Kimi as a local CLI-backed provider.

Requirements

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

Install Kimi

If you use hstack, you can install Kimi with the providers installer:

hstack providers install kimi
kimi --version

Or install manually (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 provider settings → 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:

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

On this page