Refactor agent selection logic in InstallCommand #394
Merged
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.
Problem
When running
boost:install, users are prompted twice to select code environments:Since most of the option support both MCP (editors) and AI guidelines (agents), users end up selecting the same environments twice creating a frustrating UX.
Scenario 1: First-Time User (No Saved Config)
Command:
php artisan boost:installAgent prompt: Auto-detected from system
Agent prompt: ✨ Auto-derived from selected editors
Scenario 2: Returning User (Has Saved Config)
Command:
php artisan boost:installAgent prompt: Previously saved agents
Agent prompt: ✨ Synced with current editor selection
Impact: Agent selection stays in sync with current editor choices, not stale saved config.
Scenario 3: With
--ignore-guidelinesCommand:
php artisan boost:install --ignore-guidelinesAgent prompt: Skipped
Agent prompt: Skipped
Scenario 4: With
--ignore-mcpCommand:
php artisan boost:install --ignore-mcpAgent prompt: Saved config or auto-detected
Agent prompt: Falls back to saved config