MoonshotAI / MoonshotAI/kimi-cli

kimi login fails

Open
#2,556 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
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?

0.29.1

Which open platform/subscription were you using?

OAuth

Which model were you using?

kimi-k3

What platform is your computer?

Linux ARM64

What issue are you seeing?

kimi login fails, which looks bad as I just bought a Vivace (Ultimate) subscription. Any workarounds?

What steps can reproduce the bug?
$ kimi login
Login failed: OAuth request to https://auth.kimi.com/api/oauth/device_authorization failed: fetch failed: Connect Timeout Error (attempted address: auth.kimi.com:443, timeout: 10000ms)
What is the expected behavior?

Authenticate with Kimi Code CLI via the device-code flow.

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running kimi login on Linux ARM64 with the reported OAuth configuration and inspect the device-authorization request to https://auth.kimi.com/api/oauth/device_authorization. Determine whether the timeout is handled in the CLI or caused by connectivity; done means the device-code flow authenticates successfully or reports an actionable failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authentication, cli, networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.