Feature Request: Yolo and non-Yolo mode (auto-accept)

[nordrune]

Hi :)

Background:

Like in Claude-Code there are permissions in opencode:
"permission": {
"edit": "ask",
"bash": "ask",
"webfetch": "ask"
},

I use auto-accept/yolo/allow-permissions mode about 15% of the time.

Ask:
I would like to be able to switch between my default 'ask' permissions to yolo 'allow' all permissions. As easily as with something like tab.

Context:
In claude code there are 3 modes that can be cycled through using SHIFT+TAB:
Plan
Normal/Build with ask permissions
Normal/Build with auto-accept permissions (allow)

That difference between the two Normal/Build modes is what I'm looking for.

[adamcik]

I would actually much prefer this to pressing a and then being stuck in auto-accept mode without a way to go back to ask-mode. I was considering filling a seperate issue for supporting always-ask, but I think this feature might solve my underlying issue of not being able to switch back to ask mode just as well.

[rekram1-node]

In the next release plan mode is going to have more tool access and all of them (bash, edit) are going to be ask by default, I think this will address what OP brought up, would this work for u too?

[tobias-walle]

I helped myself, by creating a custom autoaccept agent for this functionality.

Here is my config (I omitted unrelated details):

{
  "$schema": "https://opencode.ai/config.json",
  "permission": {
    "edit": "ask",
    "bash": {
      "ls": "allow",
      "pwd": "allow",
      "git status": "allow",
      "git diff*": "allow",
      "git add*": "allow",
      "git log*": "allow"
    }
  },
  "agent": {
    "plan": {
      "mode": "primary",
      "tools": {
        "write": false,
        "edit": false,
        "bash": true
      }
    },
    "build": {
      "mode": "primary",
      "tools": {
        "write": true,
        "edit": true,
        "bash": true
      }
    },
    "autoaccept": {
      "mode": "primary",
      "tools": {
        "write": true,
        "edit": true,
        "bash": true
      },
      "permission": {
        "edit": "allow"
      }
    }
  }
}

But if I understand it correctly, this way the build agent "reminder" won't be added. It would be nice if there would be an option to configure custom reminders for agents.

[nordrune]

In the next release plan mode is going to have more tool access and all of them (bash, edit) are going to be ask by default, I think this will address what OP brought up, would this work for u too?

Hi,
No, not fully.
I use all modes in Claude-Code, and they are all useful. I don't feel like anything is missing.

Modes and use cases:

Plan:
I never want edit suggestions, just explore and plan. I use the better Opus 4.1 model for complex problems that I have mostly figured out.
Usage: ~30% of the time

Normal:
Chatting, like on the Claude website.
I explore, ask questions, and make small changes. The key difference is that I don't have anything figured out yet. I just want quick feedback to figure things out. That's why I prefer a cheaper model (sonnet-4) with less intensive thinking. Once I have things figured out and know what I want to do, I validate it with Plan mode and create a plan for making the changes.
Usage: ~50% of the time

Auto-accept/Yolo:
For prototyping scripts or tasks I don't want or need to fully understand.
I use it to make straightforward, low-risk changes without confirmation and to create debug-scripts for debugging application parts.
Usage: ~20% of the time

[rekram1-node]

claude code plan behaves basically same to what I outlined above, you can always edit the build/plan modes to be more aligned with your specific workflow, you can also add custom agents that you can also tab through if you prefer something more custom

[art-shen]

What's really cool about Claude Code is that it distinguishes not on the binary but on the secondary level. Like, doesn't propose you to always accept git:* commands, but proposes to always accept git log:* instead. It makes much more sense and allows quick teaching the agent to properly and effectively behave.

Because of that, even with no yolo mode enabled, Claude Code almost never bothers me with acceptance requests, which I find very nice in comparison with opencode.

Could this also be done for opencode?

[rekram1-node]

I think I get what you are saying, yeah we probably can do that

sounds like better ux

[rekram1-node]

@amal this should be fixed on latest ex:

 "permission": {
    "bash": {
      "git *": "ask"
    }
  }

if llm runs "git log -n 10" and I allow always, then it tries to run "git diff", it will still prompt for "git diff"

Permissions should behave as expected now and when you do an accept always for bash commands it tries to find the nearest subcommand rather than approving "git *"

(works for other commands besides git ones but just using it as example)

[art-shen]

@rekram1-node thank you so much! ❤️

Can we please also get this type of step-by-step learning, when the opencode could propose to always allow e.g., git fetch * instead of git * by default?

Upd: it seems like it already should behave like that! I will give it a try!