MoonshotAI / MoonshotAI/kimi-code

-r option to resume a session is missing in --help

Open Beginner friendly
#3,285 1 comment 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.38.0

Which open platform/subscription were you using?

deepseek

Which model were you using?

DeepSeek V4 Flash Vision

What platform is your computer?

Linux 6.6.87.2-microsoft-standard-WSL2 x86_64 x86_64

What issue are you seeing?

when exiting kimi, it says 'To resume this session: kimi -r xxx', but type kimi --help, you don't see -r option. what is available is -S, --session.

 Bye!

 To resume this session: kimi -r session_fbec356c-4be5-4d23-ac71-89fa032c65e5
(base) peter@berilla-bajie:~/repo/website$ kimi --help
Usage: kimi [options] [command]

The Starting Point for Next-Gen Agents

Options:
  -V, --version                 output the version number
  -S, --session [id]            Resume a session. With ID: resume that session. Without ID:
                                interactively pick.
  -c, --continue                Continue the previous session for the working directory. (default:
                                false)
  -y, --yolo                    Auto-approve regular tool calls; the agent may still ask questions.
                                (default: false)
  --auto                        Start in auto permission mode: fully autonomous, the agent will not
                                ask questions. (default: false)
  -m, --model <model>           LLM model alias to use for this invocation. Defaults to
                                default_model in config.toml.
  -p, --prompt <prompt>         Run one prompt non-interactively and print the response.
  --output-format <format>      Output format for prompt mode. Defaults to text. (choices: "text",
                                "stream-json")
  --skills-dir <dir>            Load skills from this directory instead of auto-discovered user and
                                project directories. Can be repeated. (default: [])
  --agent <name>                Agent profile to start the new session with. Custom profiles are
                                discovered from agent directories or loaded via --agent-file. Cannot
                                be combined with --session/--continue.
  --agent-file <path>           Load an agent definition from a Markdown file and select it for the
                                new session. Cannot be combined with --session/--continue. (default:
                                [])
  --add-dir <dir>               Add an additional workspace directory for this session. Can be
                                repeated. (default: [])
  --plan                        Start in plan mode. (default: false)
  -h, --help                    Show help.

Commands:
  export [options] [sessionId]  Export a session as a ZIP archive.
  provider                      Manage LLM providers non-interactively.
  acp [options]                 Run kimi-code as an Agent Client Protocol (ACP) server over stdio.
  web [options]                 Run the local Kimi server and open the web UI.
  server                        Deprecated — use `kimi web` instead.
  login [options]               Authenticate with Kimi Code CLI via the device-code flow.
  doctor                        Validate Kimi Code configuration files.
  vis [options] [sessionId]     Launch the session visualizer in your browser.
  migrate                       Migrate data from a legacy kimi-cli installation into kimi-code.
  upgrade|update                Upgrade Kimi Code to the latest version.

Documentation:        https://moonshotai.github.io/kimi-code/

What steps can reproduce the bug?

kimi
/exit
kimi --help

What is the expected behavior?

Update help message to use -r instead of -S or update the bye reminder message to use -S.

Additional information

No response

Contribution
  • I am willing to submit a PR for this bug fix myself (please wait for maintainer approval in this issue first)

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 at the CLI entry point that defines the --help options and the exit message shown after /exit; reproduce the mismatch with kimi, /exit, and kimi --help. Align the documented resume option and the reminder, then verify that both paths present the same usable command.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.