Web UI启动时的afk选项和--no-restrict-sensitive-apis互斥 || The afk option when starting the Web UI and --no-restrict-sensitive-apis are mutually exclusive

What version of Kimi Code CLI is running?

1.41.0

Which open platform/subscription were you using?

kimi code

Which model were you using?

kimi-for-coding

What platform is your computer?

Linux 6.8.0-107-generic x86_64 x86_64

What issue are you seeing?

Web UI启动时的afk选项和--no-restrict-sensitive-apis互斥。
情况1：如果两个选项同时开启，kimi配置default_yolo = true，在网页会话中退出plan模式时会报错：

ExitPlanMode
[...
Client unsupported
error:
The connected client does not support plan mode. Do NOT call this tool again.
message:
The connected client does not support plan mode. Do NOT call this tool again.

情况2:如果两个选项同时开启，kimi配置default_yolo = fasle,所有命令都会要求approve

What steps can reproduce the bug?

kimi --afk web --no-restrict-sensitive-apis --public

What is the expected behavior?

No response

Additional information

No response

---

What version of Kimi Code CLI is running?

1.41.0

Which open platform/subscription were you using?

kimi code

Which model were you using?

kimi-for-coding

What platform is your computer?

Linux 6.8.0-107-generic x86_64 x86_64

What issue are you seeing?

The afk option when starting the Web UI and --no-restrict-sensitive-apis are mutually exclusive.
Case 1: If both options are enabled at the same time and kimi configures default_yolo = true, an error will be reported when exiting plan mode in a web session:

ExitPlanMode
[…
Client unsupported
error:
The connected client does not support plan mode. Do NOT call this tool again.
message:
The connected client does not support plan mode. Do NOT call this tool again.

Case 2: If both options are enabled at the same time, kimi configures default_yolo = fasle, and all commands will require approve

What steps can reproduce the bug?

kimi --afk web --no-restrict-sensitive-apis --public

What is the expected behavior?

No response

Additional information

No response

Reproduce the issue with kimi --afk web --no-restrict-sensitive-apis --public, testing both default_yolo = true and default_yolo = false. Trace the handling of the afk Web UI option and sensitive-API restriction to determine why plan-mode exit fails or every command requires approval; done means both configurations behave consistently without the reported error.