fix(vscode): remember initial prompts in history - #12201
Merged
chrarnoldus merged 1 commit intoJul 14, 2026
Merged
Conversation
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
marius-kilocode
approved these changes
Jul 14, 2026
Collaborator
|
Never noticed that |
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (3 files)
Reviewed by gpt-5.6-sol · Input: 73.2K · Output: 4.8K · Cached: 469.2K Review guidance: REVIEW.md from base branch |
chrarnoldus
deleted the
session/agent_180c8fe9-118d-4933-9d07-179e1dd84116
branch
July 14, 2026 08:12
This was referenced Jul 14, 2026
t7tran
pushed a commit
to t7tran/kilocode
that referenced
this pull request
Aug 14, 2026
…9-118d-4933-9d07-179e1dd84116 fix(vscode): remember initial prompts in history
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Record a dispatched prompt in chat history before the pending draft is promoted to a real session key.
Why
The initial prompt could be sent successfully while session creation changed the active draft key. The cleanup guard then returned before recording that prompt, so ArrowUp only recalled later prompts from the established session.
The existing guard remains around visible draft cleanup, preventing an asynchronous send from clearing another tab's input.