Add agent autonomy presets - #9750
Merged
Merged
Conversation
![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)SUGGESTION
Resolved Issues
Incremental Updates (since 740155a)Two new commits:
Other Observations (not in diff)
Files Reviewed (60 files)
Fix these issues in Kilo Cloud Reviewed by claude-4.6-sonnet-20260217 · 938,152 tokens Review guidance: REVIEW.md from base branch |
Contributor
|
OK I got it to work, the problem was that it was also only showing if you did not have any existing sessions in your history. A few thoughts:
|
…tence and add skipped state Replace globalState-based `onboardingShown` flag with a new `skipped` enum value in the `agentWorkStyle` VS Code setting. This makes the onboarding flow re-triggerable by setting the config back to `unset` and removes the need for extension context in work-style handlers. - Add `skipped` to WorkStyleState enum for dismissing without choosing - Remove `onboardingShown` from messages and context provider - Add `watchWorkStyleConfig` to reactively push changes to webview - Extract `SidebarEmptyState` and `WelcomeEmptyState` components from MessageList for cleaner separation of concerns - Pass `emptyState` prop through ChatView to allow sidebar-specific onboarding UI without coupling MessageList to WorkStyleProvider
…oading Add a listener for the extensionDataReady message so that the WorkStyleProvider retries data fetching when the extension signals readiness, preventing a stale loading state caused by race conditions during webview initialization.
imanolmzd-svg
force-pushed
the
feat-hitl-onboarding-preferences
branch
from
June 11, 2026 10:20
947aef2 to
ec7a5ff
Compare
…e resolver Decouple onboarding visibility from the persisted WorkStyleState by introducing a dedicated `display` signal driven by resolveWorkStyleOnboarding(). The onboarding panel now auto-persists "skipped" on first render (one-off semantics) and dismisses itself on newTaskRequest events. Unit tests cover the three resolution branches.
Contributor
Visual Changes
Other Implementation details
Testing
Screen.Recording.2026-06-11.at.12.06.15.mov |
marius-kilocode
commented
Jun 11, 2026
Collaborator
Author
|
As an existing user, how can I use this? Is this only part of the onboarding now? |
marius-kilocode
commented
Jun 11, 2026
marius-kilocode
commented
Jun 11, 2026
Contributor
Yes, it's only part of the onboarding |
Persist skipped state only after onboarding is bypassed, apply presets through one rollback-aware extension operation, and use the human-in-the-loop identifier consistently.
The apply handler already posts the updated work-style payload internally, so the additional post here caused a redundant message to be sent to the webview after each style application.
Contributor
Benchmark resultsI benchmarked this PR at The scenario measured a cold Kilo sidebar open on a new profile. The PR rendered the new first-run work-style picker, while the base rendered the standard empty state.
The functional behavior matched the intended design:
Overall, the PR adds a modest amount of cold initialization work, consistent with rendering the additional onboarding UI. The absolute style and layout increases were small, warm-idle behavior was effectively unchanged, and there was no observable responsiveness regression. With only three runs and some baseline DOM variability, these results do not demonstrate a meaningful user-visible performance regression. |
Contributor
|
Current UI 
|
lambertjosh
approved these changes
Jun 12, 2026
… card Move the "Go to Settings" call-to-action out of the post-save toast and into a persistent inline link at the bottom of the WorkStylePicker. Simplify the success toast to a short 2-second confirmation, tighten choice descriptions for conciseness, drop the bash detail row, and remove the small-viewport rule that hid mode details.
imanolmzd-svg
enabled auto-merge (squash)
June 12, 2026 16:09
imanolmzd-svg
approved these changes
Jun 12, 2026
t7tran
pushed a commit
to t7tran/kilocode
that referenced
this pull request
Aug 14, 2026
* feat(vscode): add agent autonomy presets * feat(work-style): simplify onboarding state to use config-only persistence and add skipped state Replace globalState-based `onboardingShown` flag with a new `skipped` enum value in the `agentWorkStyle` VS Code setting. This makes the onboarding flow re-triggerable by setting the config back to `unset` and removes the need for extension context in work-style handlers. - Add `skipped` to WorkStyleState enum for dismissing without choosing - Remove `onboardingShown` from messages and context provider - Add `watchWorkStyleConfig` to reactively push changes to webview - Extract `SidebarEmptyState` and `WelcomeEmptyState` components from MessageList for cleaner separation of concerns - Pass `emptyState` prop through ChatView to allow sidebar-specific onboarding UI without coupling MessageList to WorkStyleProvider * chore: update kilo-vscode visual regression baselines * feat(work-style): refine onboarding preferences * feat(webview): re-request work style on extensionDataReady if still loading Add a listener for the extensionDataReady message so that the WorkStyleProvider retries data fetching when the extension signals readiness, preventing a stale loading state caused by race conditions during webview initialization. * chore: update kilo-vscode visual regression baselines * feat(work-style): improve onboarding flow * chore: update kilo-vscode visual regression baselines * refactor(onboarding): extract work style display logic into pure state resolver Decouple onboarding visibility from the persisted WorkStyleState by introducing a dedicated `display` signal driven by resolveWorkStyleOnboarding(). The onboarding panel now auto-persists "skipped" on first render (one-off semantics) and dismisses itself on newTaskRequest events. Unit tests cover the three resolution branches. * style(welcome): widen responsive breakpoint for work-style empty state * fix(vscode): make work style onboarding updates reliable Persist skipped state only after onboarding is bypassed, apply presets through one rollback-aware extension operation, and use the human-in-the-loop identifier consistently. * fix(work-style): remove duplicate payload post after apply handler The apply handler already posts the updated work-style payload internally, so the additional post here caused a redundant message to be sent to the webview after each style application. * refactor(onboarding): relocate settings access from toast into picker card Move the "Go to Settings" call-to-action out of the post-save toast and into a persistent inline link at the bottom of the WorkStylePicker. Simplify the success toast to a short 2-second confirmation, tighten choice descriptions for conciseness, drop the bash detail row, and remove the small-viewport rule that hid mode details. * chore: update kilo-vscode visual regression baselines --------- Co-authored-by: Imanol Maiztegui <imanol.mzd@gmail.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
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.
Summary
Closes #8419