Refs: #334518
Complexity: 2
Authors: Martin Aeschlimann (@aeschli)
Create Issue
Customization migrations are controlled by separate settings for prompt files, user data, and configured locations. Deprecated customization location settings use an informational message with links to the relevant migration page.
Test setup
Use a build with an agent-host harness active. Create migration candidates for at least two migration categories. For example:
- Create a
*.prompt.md prompt file.
- Configure a custom agent, instruction, mode, or skill location that is unsupported by the active harness and add a valid customization there.
Ensure the migration enablement settings are not explicitly configured before starting.
Verify the migration settings
- Open Agent Customizations.
- In Settings, verify these three settings exist:
chat.customizations.promptMigration.enabled, enabled by default.
chat.customizations.userDataMigration.enabled, disabled by default.
chat.customizations.locationsMigration.enabled, disabled by default.
- Verify Migrate Prompt Files is offered by default when prompt candidates exist.
- Verify Migrate User Data Customizations and Migrate Location Settings are not offered by default, even when candidates exist.
- Enable
chat.customizations.userDataMigration.enabled and verify only the applicable user-data migration card and sidebar shortcut are added.
- Enable
chat.customizations.locationsMigration.enabled and verify only the applicable configured-location migration card and sidebar shortcut are added.
- Disable
chat.customizations.promptMigration.enabled and verify the prompt migration card and sidebar shortcut disappear without hiding the enabled user-data and configured-location migrations.
- Verify
chat.customizations.migration.enabled is not present in Settings.
Verify location-setting deprecation messages
Open Settings and inspect these settings:
chat.agentFilesLocations
chat.modeFilesLocations
chat.agentSkillsLocations
chat.instructionsFilesLocations
chat.promptFilesLocations
For each setting, verify:
- The deprecation notice is presented as informational guidance with an info icon rather than an error/warning icon.
- The info icon has the accessible label Info.
- The message text uses the normal foreground color, while the info icon and links remain visually distinct.
- There is comfortable spacing between the setting control and the informational notice.
- The notice explains that the setting and Local agent harness will be removed in a future release.
Verify migration links
Enable chat.customizations.locationsMigration.enabled before testing the configured-location links.
- From
chat.agentFilesLocations, chat.modeFilesLocations, chat.agentSkillsLocations, and chat.instructionsFilesLocations, activate Migrate Location Settings and verify the Agent Customizations editor opens the Migrate Location Settings page.
- From
chat.promptFilesLocations, activate Migrate Prompt Files and verify the Agent Customizations editor opens the Migrate Prompt Files page.
- Verify both links work with keyboard activation.
- Verify the links continue to use the normal Settings link styling in Dark, Light, and a High Contrast theme.
Refs: #334518
Complexity: 2
Authors: Martin Aeschlimann (@aeschli)
Create Issue
Customization migrations are controlled by separate settings for prompt files, user data, and configured locations. Deprecated customization location settings use an informational message with links to the relevant migration page.
Test setup
Use a build with an agent-host harness active. Create migration candidates for at least two migration categories. For example:
*.prompt.mdprompt file.Ensure the migration enablement settings are not explicitly configured before starting.
Verify the migration settings
chat.customizations.promptMigration.enabled, enabled by default.chat.customizations.userDataMigration.enabled, disabled by default.chat.customizations.locationsMigration.enabled, disabled by default.chat.customizations.userDataMigration.enabledand verify only the applicable user-data migration card and sidebar shortcut are added.chat.customizations.locationsMigration.enabledand verify only the applicable configured-location migration card and sidebar shortcut are added.chat.customizations.promptMigration.enabledand verify the prompt migration card and sidebar shortcut disappear without hiding the enabled user-data and configured-location migrations.chat.customizations.migration.enabledis not present in Settings.Verify location-setting deprecation messages
Open Settings and inspect these settings:
chat.agentFilesLocationschat.modeFilesLocationschat.agentSkillsLocationschat.instructionsFilesLocationschat.promptFilesLocationsFor each setting, verify:
Verify migration links
Enable
chat.customizations.locationsMigration.enabledbefore testing the configured-location links.chat.agentFilesLocations,chat.modeFilesLocations,chat.agentSkillsLocations, andchat.instructionsFilesLocations, activate Migrate Location Settings and verify the Agent Customizations editor opens the Migrate Location Settings page.chat.promptFilesLocations, activate Migrate Prompt Files and verify the Agent Customizations editor opens the Migrate Prompt Files page.