You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
'yolo' aka --dangerously-skip-permissions mode not sticking in happy app #206
'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!
Reacted by Filipe Guerreiro, dinoworld75, Mike Staub, Stefan Otte, Zoee and clawssified
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.
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.
Reacted by Ryan Newton, Andrew Hundt and Filipe Guerreiro
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
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.
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".
I got claude to self-host and then setup server-side always running in yolo
From: jojonas ***@***.***>
Date: Tuesday, January 20, 2026 at 8:00 PM
To: slopus/happy ***@***.***>
Cc: Benjamin Thomas ***@***.***>, Comment ***@***.***>
Subject: Re: [slopus/happy] 'yolo' aka --dangerously-skip-permissions mode not sticking in happy app (Issue #206)
[Image removed by sender.]jonasqin left a comment (slopus/happy#206)<#206 (comment)>
I came with the same problem while it keep asking me for permissions. I dont know how to open dangerous mode in happy. I just want to act like a advisor to review my project in some time but not keep chosing "yes". I can't leave this baby though > <
—
Reply to this email directly, view it on GitHub<#206 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BVGUL7ASO2MZQ73REWKVSGL4H3FQ3AVCNFSM6AAAAACKLURNTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONZVGYZTONJRHE>.
You are receiving this because you commented.Message ID: ***@***.***>
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?
Activity
rrnewton commentedon Oct 28, 2025
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.
RapidAlexander commentedon Oct 28, 2025
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.
ex3ndr commentedon Nov 1, 2025
Yes you need to pick the mode in the app itself, it is changed when the next message processed
kmizzi commentedon Nov 1, 2025
I'm on yolo mode on both desktop and app and it still asks for permission for everything
RapidAlexander commentedon Nov 1, 2025
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
kmizzi commentedon Nov 3, 2025
Yes, basically the sync between mobile and desktop is finicky/unreliable in many ways
fix(settings): resolve YOLO mode persistence and add profile management
fix: persist permission mode across server sync updates
BTForIT commentedon Dec 27, 2025
Adding a default seems like a no brainer here...this defaulting to not continue such a loss of productivity
ahundt commentedon Dec 28, 2025
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.
ahundt commentedon Jan 11, 2026
Unfortunately the fixes I tried don't solve the problem so this issue remains outstanding
RapidAlexander commentedon Jan 11, 2026
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".
fix: set permissionMode when --yolo flag is used
fix: preserve CLI permission mode when mobile sends "default"
fix: set permissionMode when --yolo flag is used
fix: set permissionMode when --yolo flag is used
BTForIT commentedon Jan 21, 2026
bra1nDump commentedon Apr 13, 2026
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 happyto update, can you verify it's sticky on your setup?