Add setting to auto-approve external ACP agent tool permissions

[beardfaceguy]

Check for existing issues

• Completed

What problem is this solving?

When using external ACP agents (Cursor, Claude Code, Gemini CLI), permission prompts are surfaced via session/request_permission. Zed's existing agent.tool_permissions rules only apply to the native Zed agent path, so there is no global opt-in to trust an external agent's tool decisions.

In practice, users can still get repeated permission cards for external tools (for example, web search), even in workflows where they intentionally want an always-allow posture for that external agent.

Proposed behavior

Add an opt-in setting under agent, e.g.:

{
  "agent": {
    "always_allow_external_agent_tools": true
  }
}

When enabled, Zed should auto-approve external ACP tool permission requests by selecting AllowAlways when available, otherwise AllowOnce.

Expected impact

• Improves parity with external agent "yolo/always allow" workflows.
• Reduces repetitive permission friction for users who explicitly opt in.
• Keeps current behavior unchanged by default (false).

Additional context

There is prior implementation work for this behavior in closed PR #56722; this issue tracks reopening that work with clean formatting and issue linkage.

[dandv]

For development in isolated or throwaway sandboxes, the ability to allow ALL tools (including ACP) is essential for unattended workflows.

[code3z]

Yes! Is there any workaround? It's getting very annoying to approve everything even when I say "always approve" it still has to ask again for the same tool

[danielrdotcom]

ditto, this is making me use oh-my-pi in a terminal window instead of using via ACP in zed

[achneerov]

This is quite annoying, any workaround?