fix(plan): Show implementation suggestions only when LLM has all the information by alex-alecu · Pull Request #6240 · Kilo-Org/kilocode

alex-alecu · 2026-02-24T13:51:13Z

Context

This PR #6007 introduced suggestions after planning (similar to what Claude Code does), but sometimes the LLM expects some answers from the user and instead of showing just the input text, we display the implement suggestions.

We need to show the implement suggestions only when we are 100% sure we have all the info necessary.

Implementation

Move out of experimental the tool call plan_exit. We can add another tool call, but since we already have this in place, we might just as well use it.

When plan_exit is called, the LLM is sure the plan is ready in its opinion. We add the suggestions to start the implementation only when plan_exit is invoked.

Screenshots

Users are choosing ~equally all options at the moment. After this change we should show less custom/dismiss in posthog

How to Test

Ask the CLI to add a greetings prompt when Kilo is opened while in PLAN mode. Look for the implement suggestions at the end.

Get in Touch

We'd love to have a way to chat with you about your changes if necessary. If you're in the Kilo Code Discord, please share your handle here.

…information

…lo-Org/kilocode into fix/fix-plan-mode-suggestions

kilo-code-bot · 2026-02-25T07:51:11Z

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Overview

This PR refactors the plan_exit flow from a tool-driven user prompt into a clean signal-based architecture:

PlanExitTool simplified — No longer prompts the user or injects synthetic messages. It now returns a simple completion signal with plan metadata.
shouldAskPlanFollowup extracted — A shared predicate in SessionPrompt that checks for a completed plan_exit tool part in messages after the last user message. This replaces the previous lastUser.agent === "plan" check with explicit tool detection.
resolvePlan added — Multi-strategy plan text resolution with a well-ordered fallback chain: last assistant text → all assistant texts after last user → plan file on disk.
Prompt sync improved — The TUI prompt component now syncs on [sessionID, msg.id] instead of just sessionID, correctly re-syncing when a new synthetic user message appears (e.g., "Implement the plan above").
PlanExitTool always registered — Removed feature flag gating from the registry; access is properly controlled via agent permissions (deny by default, allow only for plan agent).
TUI session handler cleaned up — plan_exit no longer triggers agent switching in the session route; PlanFollowup handles the transition.
Comprehensive test coverage — New plan-exit-detection.test.ts covers trigger detection, continue/reject flows, non-completed status, multi-message scenarios, and plan file fallback. Registry test confirms plan_exit is always available.

The permission model is sound: plan_exit is deny by default in agent config, allow only for the plan agent, and shouldAskPlanFollowup additionally gates on ["cli", "vscode"].includes(Flag.KILO_CLIENT). The resolvePlan fallback chain handles edge cases well (empty last assistant, tool-only turns, missing plan text).

Files Reviewed (8 files)

packages/opencode/src/cli/cmd/tui/component/prompt/index.tsx — Prompt sync key change
packages/opencode/src/cli/cmd/tui/routes/session/index.tsx — Removed plan_exit agent switch
packages/opencode/src/kilocode/plan-followup.ts — Added resolvePlan, updated ask() to use it
packages/opencode/src/session/prompt.ts — Extracted shouldAskPlanFollowup, updated loop
packages/opencode/src/session/prompt/plan.txt — Added plan_exit instruction
packages/opencode/src/tool/plan-exit.txt — Updated description
packages/opencode/src/tool/plan.ts — Simplified PlanExitTool
packages/opencode/src/tool/registry.ts — Always register PlanExitTool
packages/opencode/test/kilocode/plan-exit-detection.test.ts — New comprehensive test file
packages/opencode/test/tool/registry.test.ts — New plan_exit registry test

marius-kilocode · 2026-02-25T09:22:37Z

packages/opencode/src/tool/registry.ts

      ...(config.experimental?.batch_tool === true ? [BatchTool] : []),
-      ...(Flag.KILO_EXPERIMENTAL_PLAN_MODE && Flag.KILO_CLIENT === "cli" ? [PlanExitTool, PlanEnterTool] : []),
+      PlanExitTool, // kilocode_change - always registered; gated by agent permission instead
+      ...(Flag.KILO_EXPERIMENTAL_PLAN_MODE && Flag.KILO_CLIENT === "cli" ? [PlanEnterTool] : []),


What about desktop and other clients, or is that irrelevant? What about extension next?

I will handle them manually in a feature PR, I have not tested them yet

marius-kilocode · 2026-02-25T09:23:47Z

packages/opencode/src/kilocode/plan-followup.ts

+
+    // Fall back to plan file on disk
+    const session = await Session.get(input.sessionID)
+    const file = Bun.file(Session.plan(session))


Do we read the complete plan always? Also if it's really large? Could that be the case?

The plan will rarely be large, it can still happen

marius-kilocode · 2026-02-25T09:25:51Z

packages/opencode/src/tool/registry.ts

+      PlanExitTool, // kilocode_change - always registered; gated by agent permission instead
+      ...(Flag.KILO_EXPERIMENTAL_PLAN_MODE && Flag.KILO_CLIENT === "cli" ? [PlanEnterTool] : []),


Why is PlanEnterTool experimental and PlanExitTool not? Wondering what happens if the flag is triggered by the users

@marius-kilocode PlanExitTool was experimental too before this PR - I am not sure why, but I though it's a good candidate for this issue.

So what if the flag is enabled or disabled, will planning be broken?

PlanExitTool was promoted from experimental to to standard, so the flag KILO_EXPERIMENTAL_PLAN_MODE will do nothing for it.

A merge conflict resolution incorrectly gated PlanExitTool behind KILO_EXPERIMENTAL_PLAN_MODE && KILO_CLIENT === "cli", preventing the plan agent from signaling completion. This broke the "looks good, implement" flow — the follow-up prompt never appeared and no new code-mode session was created. Regression of #6240.

fix(plan): Show implementation suggestions only when LLM has all the …

0886ef8

…information

github-actions bot added the contributor label Feb 24, 2026

alex-alecu added 3 commits February 25, 2026 09:45

Merge branch 'main' into fix/fix-plan-mode-suggestions

3653c79

fix: Fix plan_exit call

7143683

Merge branch 'fix/fix-plan-mode-suggestions' of https://github.com/Ki…

67e0694

…lo-Org/kilocode into fix/fix-plan-mode-suggestions

alex-alecu marked this pull request as ready for review February 25, 2026 07:47

alex-alecu self-assigned this Feb 25, 2026

alex-alecu requested a review from marius-kilocode February 25, 2026 07:47

alex-alecu mentioned this pull request Feb 25, 2026

fix(plan): prevent repeated "Ready to implement?" prompt in plan mode #6218

Closed

jeanduplessis approved these changes Feb 25, 2026

View reviewed changes

marius-kilocode reviewed Feb 25, 2026

View reviewed changes

marius-kilocode approved these changes Feb 25, 2026

View reviewed changes

alex-alecu merged commit d8ce43f into main Feb 25, 2026
10 checks passed

alex-alecu deleted the fix/fix-plan-mode-suggestions branch February 25, 2026 10:18

kilo-code-bot bot mentioned this pull request Feb 25, 2026

Improve mode switching UX: nicer prompts and auto-switch capability #6347

Open

alex-alecu mentioned this pull request Mar 6, 2026

fix(plan): restore unconditional plan_exit tool registration #6699

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(plan): Show implementation suggestions only when LLM has all the information#6240

fix(plan): Show implementation suggestions only when LLM has all the information#6240
alex-alecu merged 4 commits intomainfrom
fix/fix-plan-mode-suggestions

alex-alecu commented Feb 24, 2026 •

edited

Loading

Uh oh!

kilo-code-bot bot commented Feb 25, 2026

Uh oh!

marius-kilocode Feb 25, 2026

Uh oh!

alex-alecu Feb 25, 2026

Uh oh!

marius-kilocode Feb 25, 2026

Uh oh!

alex-alecu Feb 25, 2026

Uh oh!

marius-kilocode Feb 25, 2026

Uh oh!

alex-alecu Feb 25, 2026

Uh oh!

marius-kilocode Feb 25, 2026

Uh oh!

alex-alecu Feb 25, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

		PlanExitTool, // kilocode_change - always registered; gated by agent permission instead
		...(Flag.KILO_EXPERIMENTAL_PLAN_MODE && Flag.KILO_CLIENT === "cli" ? [PlanEnterTool] : []),

Conversation

alex-alecu commented Feb 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Context

Implementation

Screenshots

How to Test

Get in Touch

Uh oh!

kilo-code-bot bot commented Feb 25, 2026

Code Review Summary

Overview

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

alex-alecu commented Feb 24, 2026 •

edited

Loading