Skip to content

'yolo' aka --dangerously-skip-permissions mode not sticking in happy app #206

Closed

Description

@ahundt

'yolo' mode is not sticking and there are still constant prompts for permission, especially on new sessions created via the happy app + icon for creating new sessions. Changes from whatever the previous setting is to 'yolo' also sometimes gets forgotten by the app.

If it could be fixed properly that would be amazing, and also another workaround might be to simulate and send 'yes' answers automatically to allow the system to proceed when the proper yolo does not take for one reason or another.

Thanks again for the cool app!

Activity

  1. rrnewton commented on Oct 28, 2025

    @rrnewton

    I have the same problem. I switch to YOLO and it keeps asking me. The UI is also really hard for switching to yolo because if the iphone keyboard is up, there's very little screen space OUTSIDE of the PERMISSION MODE dialogue to click on in order to change it. For mobile, maybe that dialogue should be more of a "full screen" affair instead of this pop-up.

  2. RapidAlexander commented on Oct 28, 2025

    @RapidAlexander

    I'm also seeing this issue. But I'm finding if I resume from a different device with YOLO preselected before any interaction, it respects the dangerous mode.

    As a work-around when it presents, open the session from another device but before instructing it to "continue" or selection/prompting an action, be sure to use the gear to change to Yolo mode.

  3. ex3ndr commented on Nov 1, 2025

    @ex3ndr
    Contributor

    Yes you need to pick the mode in the app itself, it is changed when the next message processed

  4. kmizzi commented on Nov 1, 2025

    @kmizzi
    Contributor

    I'm on yolo mode on both desktop and app and it still asks for permission for everything

  5. RapidAlexander commented on Nov 1, 2025

    @RapidAlexander

    Yes you need to pick the mode in the app itself, it is changed when the next message processed

    But if you accidentally continue a thread and do not select Yolo mode before your first message and then try to do so for your second message, it doesn't respect it

  6. kmizzi commented on Nov 3, 2025

    @kmizzi
    Contributor

    Yes, basically the sync between mobile and desktop is finicky/unreliable in many ways

  7. added a commit that references this issue on Nov 26, 2025
    54881e2
  8. BTForIT commented on Dec 27, 2025

    @BTForIT

    Adding a default seems like a no brainer here...this defaulting to not continue such a loss of productivity

  9. ahundt commented on Dec 28, 2025

    @ahundt
    ContributorAuthor

    I've done a lot to fix that issue and a bunch of others in #272 and its corresponding happy-cli pr slopus/happy-cli#86, but the maintainers haven't had a chance to look at it yet.

  10. ahundt commented on Jan 11, 2026

    @ahundt
    ContributorAuthor

    Unfortunately the fixes I tried don't solve the problem so this issue remains outstanding

  11. RapidAlexander commented on Jan 11, 2026

    @RapidAlexander

    I've found another good workaround is to us the info/stop button to stop the interaction and then change the toggle (on your mobile device) to Yolo and make the request again or instruct to "continue".

  12. added 4 commits that reference this issue on Jan 17, 2026
    5dd79b8
    1e3d492
    ad9192d
    40ff9ce
  13. BTForIT commented on Jan 21, 2026

    @BTForIT
  14. bra1nDump commented on Apr 13, 2026

    @bra1nDump
    Contributor

    hey @ahundt, thanks for the detailed writeup - this is tracked in #521. YOLO propagation is fixed, it now sticks across new sessions and between the app and CLI. npm i -g happy to update, can you verify it's sticky on your setup?

  15. moved this from In progress to Done in roadmapon Apr 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    • Status
      Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions