You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Revalidate migration candidates against source files, preserve errors and selection state across refreshes, and guard MCP file updates against conflicts and deletion races.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copy file name to clipboardExpand all lines: src/vs/sessions/AI_CUSTOMIZATIONS.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,9 @@ Core workbench registrations may expose Local, Copilot CLI, and Claude harnesses
51
51
52
52
### `ICustomizationMigrationService`
53
53
54
-
This shared workbench service computes customization migrations for an explicit chat session. File migrations include source URIs and migratable-configuration metadata for flows that need source type and storage; MCP migrations report known servers' binary harness compatibility, migratable `.vscode/mcp.json` entries and their root `.mcp.json` targets, together with discovery and policy-coverage state. The service also produces a localized, harness-specific hint summarizing available migrations for UI consumers.
54
+
This shared workbench service computes customization migrations for an explicit chat session. File migrations include source URIs and migratable-configuration metadata for flows that need source type and storage. Its MCP migration domain owns source canonicalization, destination representability, candidate planning, pre-write revalidation, guarded execution, and typed failure reasons. MCP results also retain the full compatibility inventory, discovery state, and policy coverage. The service produces a localized, harness-specific hint summarizing available migrations for UI consumers.
55
+
56
+
`CustomizationMigrationModel` owns the editor's reactive migration lifecycle: active-session and MCP refresh inputs, async sequencing, loading/error state, candidates, and destination folders. The management editor owns only selection, rendering, confirmation, and user notifications.
0 commit comments