docs: align cli option behavior - #2668
Conversation
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 426a3650ff
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - In non-prompt mode, `--yolo` and `--plan` cannot be combined with `--continue` or `--session` | ||
| - `--yolo` and `--auto` cannot be used together | ||
|
|
||
| When resuming a session, `--auto`, `--yolo`, or `--plan` can temporarily override its saved permission or plan mode. |
There was a problem hiding this comment.
Document resumed mode overrides as persistent
For interactive resumes, these flags are not just temporary: applyStartupModesToResumedSession calls session.setPermission('auto'/'yolo') and session.setPlanMode(true) with no exit-time restore, and those session APIs write persisted permission/plan records. A user following this sentence could run kimi --continue --auto, exit, and later resume the same session still in auto mode despite expecting the override to disappear; the zh mirror has the same wording, so update both copies together.
AGENTS.md reference: docs/AGENTS.md:L19-L21
Useful? React with 👍 / 👎.
Summary
Aligns the CLI option documentation with the current validation and prompt-mode behavior.
The configuration guide currently contains outdated conflict rules and recommends combining
--yolowith-p, although prompt mode already uses auto permission and rejects that combination.Changes
kimi --yolo -pexampleKIMI_MODEL_OUTPUT_FORMATand its precedenceValidation
apps/kimi-code/src/cli/options.tsapps/kimi-code/test/cli/options.test.ts