UX: Permission prompt dialogs (“Yes / Yes for this session”) appear too frequently and break flow

What version of Kimi Code is running?

OS: Windows 10 Kimi Code CLI version: (latest as of 2026-07-18)

Which open platform/subscription were you using?

Windows 10 VSCODE插件

Which model were you using?

No response

What platform is your computer?

No response

What issue are you seeing?

Body:

When running in the default/manual permission mode, almost every tool call (Read, Edit, Bash, etc.) triggers a modal “Yes / Yes for this session” approval dialog. This makes iterative development sessions very disruptive, especially when the agent is doing many small reads or edits in a row.

Steps to reproduce:

Start Kimi Code CLI in a project.
Ask the agent to do anything that involves multiple file reads/edits or command runs.
Observe repeated “Yes / Yes for this session” prompts.
Expected behavior:

There should be a less disruptive way to grant permission for a logical block of work (e.g., a whole goal, a whole plan step, or a configurable timeout).
Alternatively, “Yes for this session” should be easier to select or configurable by default.
Actual behavior: Every tool call requires manual approval, which interrupts the user and makes the agent feel unusable for non-trivial tasks.

Environment:

OS: Windows 11
Kimi Code CLI version: (latest as of 2026-07-18)

What steps can reproduce the bug?

Body:

When running in the default/manual permission mode, almost every tool call (Read, Edit, Bash, etc.) triggers a modal “Yes / Yes for this session” approval dialog. This makes iterative development sessions very disruptive, especially when the agent is doing many small reads or edits in a row.

Steps to reproduce:

Start Kimi Code CLI in a project.
Ask the agent to do anything that involves multiple file reads/edits or command runs.
Observe repeated “Yes / Yes for this session” prompts.
Expected behavior:

There should be a less disruptive way to grant permission for a logical block of work (e.g., a whole goal, a whole plan step, or a configurable timeout).
Alternatively, “Yes for this session” should be easier to select or configurable by default.
Actual behavior: Every tool call requires manual approval, which interrupts the user and makes the agent feel unusable for non-trivial tasks.

Environment:

OS: Windows 11
Kimi Code CLI version: (latest as of 2026-07-18)

What is the expected behavior?

No response

Additional information

No response

Start by reproducing the repeated prompts in Kimi Code CLI using default/manual permission mode with multiple Read, Edit, and Bash calls. Compare the current behavior with the proposed session, logical-block, or timeout-based permission options. Done means non-trivial iterative work no longer requires disruptive approval for every tool call while preserving an explicit permission choice.