MoonshotAI / MoonshotAI/kimi-code
different Issues using the cli
Nobody has claimed this yet.
- 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.6.0
Which open platform/subscription were you using?
Kimi code $20 tier
Which model were you using?
kimi k2.6 thinking
What platform is your computer?
macOS
What issue are you seeing?
-
based on the docs https://www.kimi.com/code/docs/en/kimi-code-cli/core-operations.html#agent-and-shell-mode I am hitting cntrl + X and I can't enter in shell mode
-
everytime I turn on the plan mode I see this message
Plan mode: ON
Plan will be created here:
/Users/franciscorubial/.kimi-code/sessions/wd_carptra-crm-monolith_d32fe2a23615/session_4fcd6b1d-89b5-46e4-9466-ce6080647960/agents/main/plans/icon-gho
st-rider-cloak.md
- the agent itself doesn't come with skills or sub agents with context of the CLI as such, so if I ask something like, how do I set an mcp ? it doesn't know or it is not capable to search in his official web docs
What steps can reproduce the bug?
self described above
What is the expected behavior?
No response
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 with the Kimi Code CLI core operations documentation linked in the report and reproduce the Ctrl+X shell-mode issue on macOS. Then separately inspect the plan-mode output and the agent's ability to answer MCP questions or search the official documentation. Done means the reported CLI behaviors are reproduced, their causes are identified, and each expected behavior is confirmed with the reporter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100