feat(vscode): add project-scoped Agent Manager settings tab - #13369
Merged
marius-kilocode merged 7 commits intoAug 24, 2026
Conversation
Move Agent Manager worktree settings (project, default base branch, setup script) into the Kilo Settings editor behind a new Agent Manager tab shown only for panels that opt in. The gear action in the Agent Manager sidebar now opens that tab pre-scoped to the owning project. The default base branch picker reuses the existing ProjectBranchDialog and BranchSelect UI instead of a Settings-specific popover. Settings requests are generation-guarded so stale responses from a previously selected project cannot switch the visible repository state.
…scode-multiproject-support # Conflicts: # packages/kilo-vscode/webview-ui/agent-manager/AgentManagerApp.tsx # packages/kilo-vscode/webview-ui/agent-manager/ProjectBranchDialog.tsx
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
Contributor
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (2 files)
Fix these issues in Kilo Cloud Previous Review Summaries (2 snapshots, latest commit 62dda5a)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 62dda5a)Status: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (7 files)
Fix these issues in Kilo Cloud Previous review (commit 6b86526)Status: 3 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (50 files)
Reviewed by grok-4.6 · Input: 82.4K · Output: 5.6K · Cached: 175.1K Review guidance: REVIEW.md from base branch |
Route the settings-panel message through the shared project message handler, build the project settings handler in the project wiring, and drop the duplicate projectId prop that the merge left in SidebarBody.
…oject untouched Only Agent Manager settings messages now bump the settings generation, so unrelated Settings-panel requests carrying a requestId can no longer invalidate an in-flight projects or branches response. The handler also no longer retargets the panel project directory: the settings handler is project-scoped by projectId, and touching the panel directory expired config bindings and blocked unsaved config saves when switching the Agent Manager project.
marius-kilocode
force-pushed
the
migrate-settings-to-vscode-multiproject-support
branch
from
August 24, 2026 13:49
47670a7 to
6f6f2e4
Compare
marius-kilocode
enabled auto-merge
August 24, 2026 14:05
marius-kilocode
force-pushed
the
migrate-settings-to-vscode-multiproject-support
branch
from
August 24, 2026 14:15
62dda5a to
c7889b1
Compare
kirillk
approved these changes
Aug 24, 2026
marius-kilocode
deleted the
migrate-settings-to-vscode-multiproject-support
branch
August 24, 2026 14:24
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
3 participants
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.
Agent Manager worktree settings (project selection, default base branch, setup script) previously lived behind per-project gear menus inside the Agent Manager sidebar. That made them hard to discover and duplicated settings UI that already exists in the Kilo Settings editor, and the old dialogs each opened their own branch requests without project scoping, which raced with project switches.
This adds an Agent Manager tab to the Kilo Settings editor, placed under Auto-Approve and shown only for panels that opt in. The gear action in the Agent Manager sidebar now opens that tab pre-scoped to the owning project, and the tab keeps a project selector so multi-project users can edit each repository's worktree settings from one place.
The default base branch picker reuses the existing
ProjectBranchDialogandBranchSelectUI rather than a Settings-specific popover, so search, keyboard navigation, and the Auto-detect option behave exactly like the picker users already know. Settings requests carry request IDs and a generation counter so a slow response for a previously selected project cannot switch the visible repository state, and a configured branch that no longer exists is cleared automatically when branches load.