Problem
The onboarding wizard (Step 4: Create Config) tells new users to run mirrord wizard in their terminal. This only works if they have the mirrord CLI installed.
Many users start with the VS Code or IntelliJ extension and may not have the CLI installed. There's currently no way to launch the config wizard from within the IDE extensions.
Proposal
Add a way to trigger the mirrord wizard web UI from the IDE extensions, so users don't need to install the CLI separately just to generate their first config file.
Possible approaches:
- Bundle the wizard frontend in the IDE extension and serve it locally
- Add a "Generate Config" action in the extension that opens the wizard
- Deep link from the portal to a hosted version of the wizard
Context
This came up while building the onboarding wizard for app.metalbear.com. The final step directs users to run mirrord wizard, but this creates a dependency on CLI installation that not all users will have completed.
Problem
The onboarding wizard (Step 4: Create Config) tells new users to run
mirrord wizardin their terminal. This only works if they have the mirrord CLI installed.Many users start with the VS Code or IntelliJ extension and may not have the CLI installed. There's currently no way to launch the config wizard from within the IDE extensions.
Proposal
Add a way to trigger the
mirrord wizardweb UI from the IDE extensions, so users don't need to install the CLI separately just to generate their first config file.Possible approaches:
Context
This came up while building the onboarding wizard for app.metalbear.com. The final step directs users to run
mirrord wizard, but this creates a dependency on CLI installation that not all users will have completed.