kimi-code upgrade

Open

#500 opened on Jun 6, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug

Dominant language: TypeScript
Stars: 7.5k
Forks: 1.2k
Avg merge: 11h 53m
Merged PRs (30d): 350

Description

What version of Kimi Code is running?

0.11.0

Which open platform/subscription were you using?

Logged in to managed:kimi-code.

Which model were you using?

kimi-k2.6

What platform is your computer?

Linux 6.18.34-1-lts x86_64

What issue are you seeing?

Hello! Thank you for the agent! It's great! I see unexpected behavior when updating.

What steps can reproduce the bug?

Run: kimi upgrade

What is the expected behavior?

.bashrc does not changed
~/.kimi-code in $KIMI_CODE_HOME not at home

Additional information

My .bashrc:

# kimi-code
export KIMI_CODE_HOME="$XDG_CONFIG_HOME/kimi-code"
export PATH="$KIMI_CODE_HOME/bin/:$PATH"

Contributor guide

Open the contributing 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 issue with kimi upgrade using the .bashrc configuration shown, then trace the upgrade entry point's handling of KIMI_CODE_HOME. Done means the command leaves .bashrc unchanged and does not create ~/.kimi-code when KIMI_CODE_HOME points to $XDG_CONFIG_HOME/kimi-code.

Written by the indexing model from the issue text.

Assessment

Tech stack: bash, typescript
Domain: cli, developer-experience
Issue type: Bug
Difficulty: 3/5
Estimated time: 1-2 days
Activity status: Quiet
Clarity: Mostly clear
Newbie friendliness: 55/100