Repository navigation
Default the init full-permission consent to Yes, with a sharper warning - #11
Merged
Merged
Conversation
The consent question defaulted to No, but No is the choice that breaks the product: the harness's skills cannot run unattended without full permission, so every run and flow fails closed on the first permission request. New users hit the wizard first and had no signal that No means "most workflows will not complete." The confirm now highlights Yes as the recommended default, and its description warns explicitly that runs and flows (audit → triage → patch → verify) will not complete without it. Doctor's scoped-mode message carries the same warning. Headless `init --yes` still defaults to No — silent consent without a human reading the warning is the one path that stays opt-in via --full-permission. 💘 Generated with Crush Assisted-by: Crush:rits/zai-org/glm-5-3
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
The init wizard's full-permission consent defaulted to No — but No is the choice that breaks the product: the harness's skills cannot run unattended without full permission, so every run and flow fails closed on the first permission request. New users hit the wizard first and had no signal that No means "most workflows will not complete."
(recommended).init --yesstill defaults to No — silent consent without a human reading the warning stays opt-in via--full-permission.Verification
💘 Generated with Crush