Repository navigation
docs(swarm): board lives with background agents, not Experimental settings - #15106
Conversation
The Kilo Swarm board control moved out of the VS Code task header into the session dock at the bottom of the background agent sessions, and Kilo Swarm is no longer configured under Experimental settings. Update the settings and Agent Manager docs to describe the new entry point and correct the removed Experimental reference.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
| #### Viewing the board | ||
|
|
||
| When Kilo Swarm is enabled and the main session has board messages, a **Board** icon appears in its task header. Select the icon to open the board dialog and read the stored messages. Each message shows the sender and recipient avatars. Select an avatar to open that agent's transcript. | ||
| The board is only shown with the session's background agents. When Kilo Swarm is enabled and the main session has background agents, a **Board** control appears at the bottom of the background agent sessions, in the session dock next to the background-agent row above the prompt. It is no longer in the task header, and the feature is no longer configured under Experimental settings. Select the control to open a panel with the latest posts, then open the full board dialog to read the stored messages. Each message shows the sender and recipient avatars. Select an avatar to open that agent's transcript. |
There was a problem hiding this comment.
WARNING: The board is not tied to background agents. SwarmBoardButton renders whenever the session is allowed and has board messages (shown: () => allowed() && present(), present() is !!board()?.messages.length, in packages/kilo-vscode/webview-ui/src/components/chat/SwarmBoard.tsx:432). The dock keeps the button in the same place after the background agents are cleared or the view reloads (see the SwarmBoard.tsx header comment and SessionDock.tsx:21-23), and the board also works with foreground task agents (see line 53 above: "It works with both foreground and background task agents"). So "only shown with the session's background agents" misstates the behavior; consider describing the control as appearing whenever the session has board messages, next to the background-agent row when those agents exist.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| All participants can read the board history, including messages addressed to others. Recipient selection is not a privacy boundary. Peer messages do not grant user approval or change permissions; `HOLD` and `VETO` are advisory, not controls that pause or cancel work. | ||
|
|
||
| When a main session has board messages, open the **Board** icon in its task header (VS Code) or session header (JetBrains, which also offers a **View Kilo Swarm** session menu action) to read them, refresh them, or reset the board. Only the owning top-level session can view or reset its board; child sessions and cloud sessions cannot. Reset clears visible messages only and does not stop agents or clear conversations. See [Kilo Swarm communication](/docs/automate/agent-manager#kilo-swarm-communication) for the board dialog, ownership rules, and recipient-state warnings. | ||
| Kilo Swarm's board is only shown with the session's background agents, and its control lives there. In VS Code, the **Board** control appears at the bottom of the background agent sessions, in the session dock next to the background-agent row above the prompt. It is no longer in the task header, and Kilo Swarm is no longer configured under Experimental settings. In JetBrains, open the **Board** icon in the session header, which also offers a **View Kilo Swarm** session menu action. Use the control to read the board messages, refresh them, or reset the board. Only the owning top-level session can view or reset its board; child sessions and cloud sessions cannot. Reset clears visible messages only and does not stop agents or clear conversations. See [Kilo Swarm communication](/docs/automate/agent-manager#kilo-swarm-communication) for the board dialog, ownership rules, and recipient-state warnings. |
There was a problem hiding this comment.
WARNING: "Kilo Swarm's board is only shown with the session's background agents" does not match the extension. The dock button renders whenever the session is allowed and has board messages, independently of background agents (shown: () => allowed() && present() in packages/kilo-vscode/webview-ui/src/components/chat/SwarmBoard.tsx:432), and it stays in place after those agents are cleared or the view reloads. The board also works with foreground task agents, as the same page notes elsewhere. Consider rephrasing to say the control lives in the session dock and appears when the session has board messages.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Previous Review Summary (commit df64554)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit df64554)Status: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (2 files)
Reviewed by deepseek-v4.1-flash · Input: 64.4K · Output: 5.1K · Cached: 340.1K Review guidance: REVIEW.md from base branch |
|
@kilocode-bot verify fix all comments! |
|
I pushed a fix for both review comments to this PR's branch (
I checked the visibility logic in Please review the pushed commit. Marius, please also confirm the wording matches what you wanted. The PR description still says the board is "only shown with the session's background agents". You may want to update it to match the docs. |
What changed
Updated the Kilo Swarm documentation to match the current VS Code board UI:
packages/kilo-docs/pages/getting-started/settings/index.md(Kilo Swarm section)packages/kilo-docs/pages/automate/agent-manager.md(Viewing the board)The docs now state that:
Why
The board button previously lived in the session header (
TaskHeader.tsx). It was moved into the session dock next to the background agent stack, so the old "Board icon appears in its task header" text no longer matched the UI. The opt-out setting also moved out of the Experimental tab to Agent Behaviour (shared_agent_board), so the docs must not point at Experimental. Both doc pages still described the removed task-header location.No changeset: docs-only.
Built for Marius Wichtner by Kilo for Slack