MoonshotAI / MoonshotAI/kimi-cli
`kimi acp` does not accept the Moonshot Open Platform authentication
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.4k
- Forks
- 1.3k
- Avg merge
- 9h 47m
- Merged PRs (30d)
- 2
Description
What version of Kimi Code CLI is running?
kimi, version 1.26.0
Which open platform/subscription were you using?
Moonshot AI Open Platform
Which model were you using?
kimi-k2.5
What platform is your computer?
Linux 6.17.0-19-generic x86_64 unknown
What issue are you seeing?
When opening Kimi in ACP model (kimi term, or using kimi via Zed editor), it does not reuse the authentication info I made with Moonshot Open Platform. It insists on requiring "Kimi Code Plans".
What steps can reproduce the bug?
Two ways:
- Run
kimi term. Toad said "failed to connect". - Launch Kimi ACP from Zed: It opens browser requiring for authentication, but points to kimi.com
What is the expected behavior?
It should accept Moonshot Open Platform authentication that I already set from Kimi CLI.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with kimi term, then compare it with launching Kimi ACP from Zed as described in the issue. Trace how ACP authentication differs from the existing Kimi CLI authentication; done means Moonshot Open Platform credentials are reused in both paths without requiring Kimi Code Plans or redirecting to kimi.com.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100