fix(vscode): remove unsupported legacy migration - #13605
Merged
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (53 files)
Previous Review Summaries (2 snapshots, latest commit df75333)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit df75333)Status: No Issues Found | Recommendation: Merge Files Reviewed (21 files)
Previous review (commit 91d2be3)Status: No Issues Found | Recommendation: Merge Files Reviewed (33 files)
Reviewed by grok-4.6 · Input: 151.2K · Output: 17.5K · Cached: 1.3M Review guidance: REVIEW.md from base branch |
marius-kilocode
force-pushed
the
investigate-code-keychain-storage-error
branch
from
August 31, 2026 11:17
91d2be3 to
fc62b89
Compare
marius-kilocode
enabled auto-merge
August 31, 2026 11:31
kirillk
approved these changes
Aug 31, 2026
marius-kilocode
force-pushed
the
investigate-code-keychain-storage-error
branch
from
August 31, 2026 14:01
df75333 to
49af575
Compare
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
2 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.
What Problem This Solves
A fresh VS Code profile still ran the unsupported Kilo v5 migration scan during startup and webview synchronization. The scan read VS Code SecretStorage before it knew whether legacy data existed. That can initialize macOS keychain-backed encryption and produce a keychain dialog without a login or credential-save action.
The retired migration also remained available through Settings and the command palette.
Why This Change Was Made
Remove the obsolete migration instead of disabling native credential storage for normal VS Code use. The extension no longer needs to discover, import, or delete legacy Kilo credentials and settings.
Keep the explicit Roo Code session import and its shared session discovery, conversion, and batch-import code. The shared session helpers retain their existing paths to avoid an unrelated file move.
User Impact
This does not add Zoo-specific storage discovery. The existing Roo discovery list does not include
ZooCodeOrganization.zoo-code; Zoo compatibility remains unverified and is outside this cleanup.Evidence
Live VS Code testing was not run to avoid accessing the system keychain. The native macOS dialog's disappearance has not been visually verified. No keychain contents were inspected or changed.