Repository navigation
feat(vscode): add shared agent board reader and reset - #13782
Merged
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Previous Review Summaries (5 snapshots, latest commit e089f5c)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit e089f5c)Status: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Previous review (commit d7b368b)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (67 files)
Fix these issues in Kilo Cloud Previous review (commit b04dd7f)Status: No Issues Found | Recommendation: Merge Files Reviewed (67 files)
Previous review (commit efa5c6f)Status: No Issues Found | Recommendation: Merge Files Reviewed (67 files)
Previous review (commit 00370f3)Status: No Issues Found | Recommendation: Merge Files Reviewed (65 files)
Reviewed by grok-4.6 · Input: 105.1K · Output: 8.3K · Cached: 218.6K Review guidance: REVIEW.md from base branch |
marius-kilocode
force-pushed
the
add-session-board-view-and-reset
branch
from
September 4, 2026 11:21
00370f3 to
15beb8f
Compare
marius-kilocode
enabled auto-merge
September 4, 2026 11:40
marius-kilocode
disabled auto-merge
September 4, 2026 12:10
marius-kilocode
force-pushed
the
add-session-board-view-and-reset
branch
from
September 7, 2026 13:30
efa5c6f to
b04dd7f
Compare
marius-kilocode
enabled auto-merge
September 7, 2026 13:30
marius-kilocode
force-pushed
the
add-session-board-view-and-reset
branch
from
September 8, 2026 08:37
b04dd7f to
d7b368b
Compare
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
marius-kilocode
force-pushed
the
add-session-board-view-and-reset
branch
from
September 8, 2026 09:10
e089f5c to
f83275f
Compare
eshurakov
approved these changes
Sep 8, 2026
This was referenced Sep 8, 2026
This was referenced Sep 9, 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
Shared-agent board messages are available to agents, but the owning session has no direct way to read the full discussion. Long exchanges are difficult to inspect through individual tool results, and a stale board cannot be cleared without disrupting resumed agents' cursors.
Why This Change Was Made
Add a single Board action to the session header, shown only when
experimental.shared_agent_boardis enabled and the board has messages. It opens a larger chronological reader and loads older history automatically in bounded requests. Sender/recipient rows, task and broadcast icons, tooltips, and Markdown reuse the same components as board tool cards.The observer is read-only: opening the reader does not create a board or mark messages as agent-read. Reset is owner- and directory-scoped, requires confirmation, and rejects a changed revision. It advances the visible-history floor rather than deleting rows, so existing message IDs, cursors, replies, and retried posts remain valid. Conversations and running agents are unchanged. Archived records remain stored; this is not permanent deletion or storage reclamation.
User Impact
Evidence
Validated against the PR base: extension compile/typecheck/lint, 4,846 extension unit tests, 65 board/runtime/API tests, 4 migration tests, and 10 focused browser tests. Strict HTTP API coverage and auth checks cover all 331 scenarios, including both board endpoints. Migration consistency, unused-export, source-link, and annotation checks pass. The browser suite ran on an isolated port to avoid another worktree's Storybook server.
CI also exposed Windows path representation differences and npm audit requests in two local-file test fixtures. Board directory checks now compare canonical paths while still rejecting neighboring worktrees. Only those test fixtures disable audit networking; production npm behavior is unchanged. The full local core suite passes with the unrelated local AWS profile unset (1,319 passed, 26 platform skips).
Manual VS Code checks covered hidden empty boards, directed and broadcast messages, long-history loading, keyboard navigation, and reset. Screenshots use isolated fixture data without real credentials. The standalone
kilo-uistory typecheck has unrelated existing story-typing errors; the extension typecheck covers the shared renderer used here.Board reader
An empty board does not add a header control