[ENHANCEMENT] Allow import settings in the initial screen

[emeraldcheshire]

Problem (one or two sentences)

Initial setup screen forces you to set up a Provider before allowing you to access Settings->About->Import.

Context (who is affected and when)

Affects existing users migrating to a fresh install.

Affects enterprises who wish to standardize user setup using an imported settings file during initial setup.

Desired behavior (conceptual, not technical)

Initial setup screen for fresh Roo Code installation should allow Import of settings file.

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote]

I've analyzed this issue and here's my proposed implementation plan:

Problem Analysis

Currently, the Welcome screen (WelcomeViewProvider.tsx) requires users to set up an API provider before they can access Settings -> About -> Import. This blocks existing users migrating to a fresh install and enterprises wanting to standardize setup via imported settings files.

Proposed Solution

Add an "Import Settings" link to the Landing screen of the Welcome flow. This allows users to import their settings file immediately upon fresh installation, before any provider configuration is required.

Implementation Details:

1. Modify webview-ui/src/components/welcome/WelcomeViewProvider.tsx:

   • Add an "Import Settings" link (using VSCodeLink) to the Landing screen section (where selectedProvider === null)
   • The link will trigger the existing import functionality: vscode.postMessage({ type: "importSettings" })
   • Place it near the "Get Started" and "No Account" options as a secondary action

2. Translation key already exists:

   • welcome:importSettings = "Import Settings" (found in webview-ui/src/i18n/locales/en/welcome.json)

3. Visual consistency:

   • Use the same styling pattern as the existing "or use without an account" link
   • Optionally add the Download icon from lucide-react for visual consistency with the Settings -> About import button

Benefits:

• Minimal code change (approximately 3-5 lines added)
• Reuses existing import infrastructure and translation
• Doesn't disrupt the existing welcome flow for new users
• Addresses both use cases: individual migrations and enterprise standardization

This approach ensures the import functionality is accessible during initial setup while maintaining the current UX flow for users who don't need to import settings.

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[emeraldcheshire]

@roomote I approve the plan.

[roomote]

I've seen your approval and will proceed with the implementation. I'll open a draft PR to share progress shortly.

[roomote]

Opened a draft PR with my attempt at addressing this: #10994

The implementation adds an "Import Settings" link to the welcome landing screen, allowing users to import settings before configuring a provider. Feedback welcome!