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
[Desktop/Web] Auto-accept permissions gets turned on for every conversation #15589
It's worse than that: Apparently, auto-accept is turned on by default for every new and existing session unless it has been explicitly turned off for that session.
It's even worse: The button is disabled (unclickable) until you submit the first prompt. And then it defaults on. So there is no way to begin a session without auto-accepting permissions. Except I guess to submit the prompt and then very quickly click the toggle before the agent tries to do any commands.
We're fixing this. Was a bit of a miscommunication around some core changes that are coming in, and I rushed this change to the frontend. Fix coming shortly.
Reacted by Achim Herwig, Franz Thoma, Lucas, Andy Pfister and Stefan Kunkel
Activity
fmthoma commentedon Mar 2, 2026
It's worse than that: Apparently, auto-accept is turned on by default for every new and existing session unless it has been explicitly turned off for that session.
Here's the problem in the source code:
opencode/packages/app/src/context/permission-auto-respond.ts
Line 40 in bf2cc3a
This should be
return value ?? false, or there should be a global/fallback auto-accept setting that acts as fallback.kentonv commentedon Mar 2, 2026
It's even worse: The button is disabled (unclickable) until you submit the first prompt. And then it defaults on. So there is no way to begin a session without auto-accepting permissions. Except I guess to submit the prompt and then very quickly click the toggle before the agent tries to do any commands.
adamdotdevin commentedon Mar 2, 2026
We're fixing this. Was a bit of a miscommunication around some core changes that are coming in, and I rushed this change to the frontend. Fix coming shortly.
kentonv commentedon Mar 4, 2026
Seems to be fixed in 1.2.16, thanks.
adamdotdevin commentedon Mar 4, 2026
Fixed in latest