Skip to content

Desktop app: "Auto-approve requests" setting toggle cannot be turned on and does not persist #41069

Closed as duplicate

Description

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the bug

On the OpenCode desktop app (Windows 11, v1.18.15), the "Auto-approve requests" (auto-approve permissions) toggle in Settings cannot be turned on: clicking it does nothing / it stays off or greyed out.

Additionally, the toggle's state does not persist to ~/.config/opencode/opencode.jsonc (no permission-related change is written), so there is no way to enable auto-approval from the desktop UI.

Manually adding "permission": { "*": "allow" } to the global config file also still results in permission prompts for some actions (e.g. external directory access / doom-loop detection are ask by default and the UI has no way to change them).

Expected behavior

  • The Settings toggle should turn on/off and persist (either to opencode.jsonc or app-local settings).
  • Turning it on should behave like --auto mode (auto-approve requests that are not explicitly denied).

Environment

  • OS: Windows 11
  • App: OpenCode Desktop v1.18.15

Activity

  1. github-actions commented on Aug 7, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    If your issue is the same, please add a reaction or comment on the existing issue rather than opening a new one. If it differs (e.g. different root cause or new regression), please clarify what distinguishes it.

  2. liudongyan13701205717-source commented on Aug 8, 2026

    @liudongyan13701205717-source
    Author

    Confirmed duplicate of #37617 / #33788 — same symptom on Desktop 1.18.15 (Windows 11): the Settings → General "Auto-accept permissions" toggle stays disabled (not-allowed), never persists a value.

    Also confirmed the workaround from #37617 works: pressing Ctrl+Shift+A (Mod+Shift+A) inside an active chat toggles auto-accept for the current session — the runtime feature works fine, only the Settings UI entry is broken.

    Please track this under #37617 / #33767. Closing this one is fine; keeping it open just for visibility on 1.18.15.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions