MoonshotAI / MoonshotAI/kimi-code

Suggestions on Auto Mode + Plan Mode Interaction and Plan Preview Feature

Open
#906 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
7.5k
Forks
1.2k
Avg merge
11h 53m
Merged PRs (30d)
350

Description

What feature would you like to see?

Suggestion 1: Do Not Auto-Approve Plans in Auto Mode with Plan Mode Enabled

Problem Description
When Auto Mode is enabled alongside Plan Mode, the system automatically approves the generated plan and proceeds to execution without user intervention. This removes the manual review step that Plan Mode is intended to provide.

Proposed Solution

  • In Auto Mode + Plan Mode, the system should pause and wait for manual user confirmation after the plan is generated.
  • Execution should only proceed after the user explicitly clicks "Approve Plan" or "Confirm Execution".
  • Auto Mode automation should apply to code execution, terminal commands, etc., but not override plan-level decisions.

Suggestion 2: Add Full Plan Preview in Plan Mode on Kimi Web

Problem Description
On the Kimi Web interface, when Plan Mode is enabled, users currently seem unable to view the complete plan content—only fragments or summaries are visible. This makes it difficult to fully assess the plan and completeness before approval.

Proposed Solution

  • Provide a full plan preview after the plan generation is complete.
  • Display the complete plan in the sidebar (or a dedicated panel), including all steps, affected files, and intended operations.
  • The preview should be automatically presented upon plan completion, ensuring users can thoroughly review before confirming.

Summary
It would be ideal to integrate these two improvements: after Plan Mode completes, show the full plan for preview first, then require manual user confirmation before adoption—even when Auto Mode is active. This preserves the efficiency of Auto Mode while ensuring the controllability and transparency of Plan Mode.

Additional information

No response

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 by tracing the Auto Mode and Plan Mode interaction, then inspect the Kimi Web plan display entry points. Compare the current approval flow with the requested full-plan preview and identify how affected files and operations are represented. Done means plans pause for explicit approval in Auto Mode and the complete plan is visible before confirmation.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.