fix(vscode): show consistent session activity indicators - #13504
Merged
Conversation
This comment has been minimized.
This comment has been minimized.
marius-kilocode
force-pushed
the
improve-vscode-tab-session-status
branch
from
August 27, 2026 11:17
7a23321 to
cdcf69e
Compare
marius-kilocode
force-pushed
the
improve-vscode-tab-session-status
branch
from
August 27, 2026 11:28
4cfe71d to
ec20f8f
Compare
marius-kilocode
enabled auto-merge
August 27, 2026 11:44
marius-kilocode
force-pushed
the
improve-vscode-tab-session-status
branch
from
August 27, 2026 11:58
be85dc2 to
9a287dc
Compare
marius-kilocode
force-pushed
the
improve-vscode-tab-session-status
branch
from
August 27, 2026 13:00
c2b5fc6 to
f6ff101
Compare
marius-kilocode
force-pushed
the
improve-vscode-tab-session-status
branch
from
August 28, 2026 06:02
aeccb9b to
84a0b4b
Compare
WebReflection
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.
What Problem This Solves
When several sessions are open, a loading indicator alone does not show which session needs an answer or permission. Stopped, completed, and failed sessions also look too similar across the sidebar, native editor tabs, and Agent Manager.
Why This Change Was Made
Use one cached session-activity calculation for every presentation surface. Native editor tabs receive the derived state instead of maintaining a second backend-event state machine. Session ancestry comes from session metadata and task metadata, so a child request remains visible even when its originating task is outside the loaded transcript page.
The existing prompt-recovery path is preserved. There are no new polling loops or notification settings.
User Impact
◔⚠✓⚠Evidence
Automated checks
bun run compile: passed, including extension/webview typechecks, lint, and bundles.bun run test:unit: 4,319 passed, 0 failed after resolving conflicts with currentmain.bun run knip,bun run check-kilocode-change, package formatting, and diff whitespace checks passed.SessionProviderand renders actual Agent Manager tabs. It covers nested requests without loaded transcript pages, resolution, stale permissions, retry/offline states, completion/error ownership, next-turn and revert resets, reconnection, deletion, and disposal.Screenshot tests
Added seven stories to the existing automatically discovered Playwright screenshot suite:
The existing switcher story now uses a real portal and includes waiting and error states.
The original five stories and the three focused review-regression scenarios were rendered locally in dark and light themes. Repeated captures were byte-identical, and warning, success, and error colors were distinct. Spinner animation is frozen only in the screenshot fixtures. Linux baseline generation and pixel comparison run in CI; the repository intentionally skips baseline comparison on macOS.
VS Code self-test
Verified the sidebar's multiple-session tabs, native editor tabs, Agent Manager tabs, and worktree cards in isolated VS Code. Checked input-required priority, stale-permission recovery, completion, new-turn reset, failure, revert, reconnect, and removal/history scoping. These checks used controlled session events, not a live model round trip.
Native editor tabs
Multiple sessions in the sidebar
All tab states, dark and light themes
Worktree cards
Manual test
Run two sessions in the sidebar or Agent Manager. Trigger a question or permission in one while the other runs, answer the request, then complete a session and start its next turn. Confirm that both the session tab and its native/context indicator update and that old attention or completion states clear.
Review regression checks in VS Code
Verified that the selected worktree retains its warning color and that the real portalled sidebar switcher retains warning, completion, and error colors.