fix(init): hide ambient plugin from multiselect#150
Merged
Conversation
…nt prompt The init wizard showed devflow-ambient in the plugin multiselect (pre-selected) AND had a separate "Enable ambient mode?" prompt, which was redundant. Since the /ambient command was removed (ambient is hook-only now), the plugin's only purpose is distributing skills/agents the hook needs. Now follows the devflow-core-skills precedent: filtered from multiselect, auto- included when the ambient prompt answer is yes.
dean0x
pushed a commit
that referenced
this pull request
Mar 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
devflow-ambientfrom the plugin multiselect and preSelected defaults (followsdevflow-core-skillsprecedent)devflow-ambientwhen the "Enable ambient mode?" prompt is answered yesContext
The init wizard previously showed
devflow-ambientin the plugin multiselect (pre-selected) AND had a separate "Enable ambient mode?" prompt. Since/ambientwas removed and ambient is hook-only, the plugin's sole purpose is distributing skills/agents the hook needs — it shouldn't be a user-facing selection.Test plan
npm run buildpassesnpm test— all 250 tests passnode dist/cli.js initin TTY — confirmambientNOT in plugin list, ambient prompt still appearsnode dist/cli.js init --no-ambient— confirm ambient plugin NOT installednode dist/cli.js init --ambient— confirm ambient plugin IS installed (auto-included)