Repository navigation
fix(extension): preserve browser chat runs - #5113
Conversation
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryIncremental re-review of the new commit ( Files Reviewed (14 files)This pass re-reviewed the incremental change in
Previous Review Summaries (2 snapshots, latest commit ad7b639)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit ad7b639)Status: 1 Issue Found | Recommendation: Address before merge Executive SummaryThe queued-message drain effect in Overview
Issue Details (click to expand)WARNING
Files Reviewed (14 files)
Fix these issues in Kilo Cloud Previous review (commit b0f210a)Status: 1 Issue Found | Recommendation: Address before merge Executive SummaryThe queued-message drain effect in Overview
Issue Details (click to expand)WARNING
Files Reviewed (14 files)
Reviewed by kimi-k3 · Input: 56.8K · Output: 10.1K · Cached: 591.5K Review guidance: REVIEW.md from base branch |
Users can keep a browser chat run active while they open the Agents tab, queue the next message, and see the conversation model while the catalog loads.
Product behavior now preserves streaming output across the mode switch, sends queued text after the active turn, drops queued text on Stop, and locks model controls during a run.
The panel remains mounted while hidden, queue state lives per conversation, and the gateway paths validate the stored model against the loaded catalog. Focused Vitest and Chrome and Firefox extension checks cover the new behavior.
Human steps: none.
Visual Changes: N/A.
E2E: bot-e2e. Chrome continuity and model-loading scenarios passed 8/8, Firefox Selenium passed 35/35, and the repaired queue/model re-verification passed.