Skip to main content

Guides

Kimi K3 Took #1 — How to Run It With Power Claude (Not Locked to One Lab)

Kimi K3 Took #1 — How to Run It With Power Claude (Not Locked to One Lab)

Kimi K3 (Moonshot AI) took top spots on public frontend coding arenas ahead of Claude Fable 5 — and ships as open weights. Power Claude is host-agnostic: discover Kimi, pin the Model tab you use, hide noise.

TL;DR: Wire KIMI_API_KEY / MOONSHOT_API_KEY, let Power Claude auto-discover the Kimi Model tab, hide unused hosts, keep Claude/Grok/Codex under the same pool contracts.

Why Kimi K3 matters

Public 2026 reports put Kimi K3 at #1 on community Frontend Code Arena leaderboards (Elo ~1679 class), ahead of Claude Fable 5 in many frontend matchups, with open weights in the multi-trillion parameter class. Leaderboards move weekly — the operational truth is multi-model agentic coding.

Power Claude contracts (not hard-coded favorites)

SurfaceMeaning
ClaudeDefault public host + brain
Grok / Codex / Gemini / KimiPure families when discovered or pinned
Mixtures / AllCross-host / gateway — pin when needed; hidden by default
Auto-discovery: env keys, home paths (~/.kimi), host-store seats, session tokens (kimi, moonshot, k3). Hide beats discovery.

How to run K3

export KIMI_API_KEY="…"   # or MOONSHOT_API_KEY
pc host-account import-live kimi
pc host-account rotate kimi

Gateway mixtures: Claude Code UI → hurc-gateway → Kimi brain; pin Mixtures tab.

FAQ

Is K3 better than Fable 5?

No single winner — K3 leads some frontend arenas; Fable 5 still wins multiple SWE/visual harnesses.

Will unused models clutter UI?

No — defaults are Claude + discovered/pinned only.

Can I hide Kimi after trying?

Yes — add pure-kimi to hidden in ~/.power-claude/state/ui/model-tab-visibility.json.