Skip to content

Desktop ignores permission rules in ~/.config/opencode/opencode.jsonc #36416

Closed as not planned

Description

@ayakabot

OpenCode Desktop ignores permission rules from ~/.config/opencode/opencode.jsonc (bash patterns always prompt)

Description

OpenCode Desktop does not honor permission rules defined in the user-level config ~/.config/opencode/opencode.jsonc. For example, with the following in the config:

{
  "permission": {
    "bash": {
      "git log*": "allow"
    }
  }
}

Desktop still pops up the "Allow / Deny" confirmation dialog when the agent tries to run git log. The same config works as expected in the TUI (opencode CLI), so the rule is being written correctly and parsed somewhere — Desktop just doesn't apply it.

Plugins

none

OpenCode version

1.17.18 (1.17.18)

Steps to reproduce

  1. Make sure ~/.config/opencode/opencode.jsonc (or the OS equivalent) contains a permission rule such as "bash": { "git log*": "allow" }.
  2. Launch OpenCode Desktop and start a session in any git repo.
  3. Ask the agent to run git log (or any command matching the pattern).
  4. Observe the permission prompt asking to confirm, instead of auto-allowing.
  5. (For comparison) Run the same prompt in the TUI opencode CLI with the same config — the command runs without prompting.

Screenshot and/or share link

No response

Operating System

macOS 26

Terminal

N/A (Desktop app)

Activity

  1. changed the title [-]OpenCode Desktop ignores permission rules from ~/.config/opencode/opencode.jsonc (bash patterns always prompt)[/-] [+]Desktop ignores permission rules in ~/.config/opencode/opencode.jsonc[/+] on Jul 11, 2026
  2. github-actions commented on Jul 11, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues reporting that permission rules are not honored. Please check:

    If your issue is specifically about the Desktop app ignoring the global config while the TUI works correctly (i.e., the Desktop sidecar not loading ~/.config/opencode/opencode.jsonc at all), that would be a distinct bug from the above — please add a note confirming whether this is the case so maintainers can triage accordingly.

  3. github-actions commented on Sep 10, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

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