Replies: 2 comments 1 reply
-
|
Hey dev The kimi-code/kimi-for-coding model may be causing issues. Switch to the default model. Edit ~/.kimi/config.json: { Or remove the "model" line entirely to use the default configuration. I was able to resolve it this way. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
This issue is with the kimi-code.json file it got extra closing curly bracket at the end of json which is invalid you can remove that extra curly bracked and save it and then try again. File is under this path. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
What version of Kimi Code CLI is running?
kimi, version 1.6
Which open platform/subscription were you using?
Visual Studio Code
Which model were you using?
kimi-code/kimi-for-coding
What platform is your computer?
No response
What issue are you seeing?
Using Kimi Code within VS Code.
Service temporarily unavailable.
{"jsonrpc":"2.0","id":"2_1770754790728","error":{"code":-32003,"message":"Error code: 401 - {'error': {'message': 'The API Key appears to be invalid or may have expired. Please verify your credentials and try again.', 'type': 'invalid_authentication_error'}}","data":null}}
What steps can reproduce the bug?
/init
/version
no matter what i do, this comes up.
What is the expected behavior?
Not getting this error.
You need better Error handling. How is a user supposed to know how to resolve?
I understand this is due to insufficient tokens. I have checked my dashboard, and it says I have enough.
You need independent testers to QA all features and enhancements prior to a production deployment.
Additional information
No response
Beta Was this translation helpful? Give feedback.
All reactions