feat(vscode): show scheduled wakeup status in Agent Manager - #14292
Conversation
Code Review SummaryStatus: No Issues Found | Recommendation: Merge The only change since the prior reviewed commit Files Reviewed (1 file)
Reviewed at commit Previous Review Summaries (2 snapshots, latest commit 10b4789)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 10b4789)Status: No Issues Found | Recommendation: Merge The previous WARNING is resolved at HEAD: Files Reviewed (2 files)
Reviewed at commit Previous review (commit 3ef8473)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (37 files)
Fix these issues in Kilo Cloud Reviewed at commit Reviewed by deepseek-v4.1-flash · Input: 0 · Output: 0 · Cached: 0 Review guidance: REVIEW.md from base branch |
Context
Sessions can schedule a wakeup that resumes them later (
schedule_wakeup). While the timer is pending the session is idle, so the Agent Manager showed a plain idle indicator with no signal that a resume was scheduled. There was no way to tell a session that is truly done from one that will wake itself up.Implementation
session.wakeupSSE event and seed pending counts fromGET /kilocode/wakeupsinto the webview, next to the existing session status seeding.scheduledactivity. It ranks aboveidleand belowdone,busy,retry,error, andwaiting. It does not roll up from child sessions and does not count as active, so it never starts the busy spinner or blocks worktree deletion.Screenshots / Video
How to Test
Manual/local verification
aria-label="Scheduled"and the same computed color as the idle icon.pending: 0and confirmed the row returned to the branch icon.bun run typecheck,bun run lint, and the focused unit tests pass.Reviewer test steps
schedule_wakeupwith a short delay, for example "schedule a wakeup in 2 minutes to check the build".cancel_wakeup, or wait for the wakeup to fire, and confirm the icon returns to the branch and then to the busy spinner.Blocked checks and substitute verification
tests/unit/worktree-manager.test.tscases that fail only under parallel full-suite load. That file passes in isolation (134 tests, 0 fail) and does not touch this change, so these are unrelated flakes.