feat(remote-sender): forward messageID and drop queued prompts - #13496
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Reviewed by grok-4.6 · Input: 311.2K · Output: 19.1K · Cached: 801.4K Review guidance: REVIEW.md from base branch |
This was referenced Aug 28, 2026
Merged
RSO
approved these changes
Aug 28, 2026
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
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.
Implementation
The new
drop_queued_messagecommand usesDropQueuedMessageDatato require amsg-prefixedmessageIDand validatessessionIdbefore targeting one queued prompt.KiloSessionPromptQueue.dropemitssession.queue.changed; success returns{}, while unknown or active messages return an error without stopping the active prompt.send_messageretains optionalmessageIDforwarding; new comments document the command-line interface (CLI) fallback for older clients that omit it.Files
packages/opencode/src/kilo-sessions/remote-sender.ts— Source; modified (M), 34 changed lines: adds validated queued-message removal and documents the existing message identity fallback.Tests: 1 test file modified —
packages/opencode/test/kilocode/sessions/remote-sender.test.ts(M; 175 changed lines).Generated: 0 files changed.
Issue
No separate issue was supplied; this pull request accompanies the Cloud Agent contract implementation.
Context
This pull request supplies the Kilo CLI handler for targeted cancellation from Cloud Agent clients.
/Users/igor/Projects/.worktrees/agent-composers-c07a-kilocode; branchagent-composers-c07a, baseorigin/main, immutable headb9537ae089./Users/igor/Projects/.worktrees/agent-composers-c07a; branchagent-composers-c07a-s6, cloud reference only.Screenshots / Video
Visual Changes: N/A
How to Test
Verification
E2E report: none attached; the cumulative report belongs to cloud tip PR 5617.
Manual/local verification
The handoff supplies these results:
This agent did not run product checks. The handoff does not identify whether an agent or a human ran the runtime checks.
Reviewer test steps
Run the
remote-senderunit tests in the opencode package. The added cases cover dropping a waiting prompt, leaving an active run untouched, andmessageIDpass-through.Run
bun test ./test/kilocode/sessions/remote-sender.test.tsfrompackages/opencode/.Blocked checks and substitute verification
The handoff names no blocked command. Automated coverage substitutes for live verification of deterministic queued-message cancellation.
Human steps
drop_queued_messagebefore clients use it.No new environment value, secret, migration, or flag change is required.
Checklist
Get in Touch
No Discord handle provided.
Notes
Cumulative runtime verification and its limits are recorded in Kilo-Org/cloud#5617.