[ENHANCEMENT] Auto-Approve (run) isn't confidence inspiring.

[opensourcefan]

Problem (one or two sentences)

A couple things regarding (run):

1. When I add a prefix under Allowed Auto-Execute Commands, I actually don't know what I should add or what the format should be because I can't seem to get it to be reliable functional. For example if I place git in there, I still get prompt for all kinds of git commands, If I place git add in there, I still get prompted. It's a bit hit and miss really.
2. If I do have a prefix that works for whatever reason, I still see the run prompt, if I ignore it, it might go away after a bit or I might need to click it due to the reasons in feat: support OAuth 2.1 for streamable-http MCP servers #1 above. It's all just a bit flaky.

Context (who is affected and when)

Users during normal use.

Desired behavior (conceptual, not technical)

Add a prefix, ie git and git (along with anything else) is auto-approved, If git * is required then advise, as I can't get that to work either.

I've searched around, and used examples but nothing seems like a confident approach. I don't know if it's a bug or not.

I'm using VScode on Ubuntu, with this extension.

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Zoo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[opensourcefan]

For a command that has been auto approved, the "Run" button shows and stays until there is output from that command, then it disappears. That is bad when you're testing or building as the process takes a while to get an output. Couple that with not being 100% sure it will auto approve, turns into a "is it gonna work" game. It's painful.

[chengmoya]

要是像codex一样有个单独模型用来自动审批就好了，目前增加:* 并不能让我放心qaq