Auto mode causes repeated false permission notifications in terminals

Description

When using OpenCode Auto mode, permission notifications keep firing even though the permissions are automatically approved and the agent never needs user input.

The underlying issue is that Auto approval currently happens client-side, after the server has already emitted permission.asked. Integrations such as Warp and Orca therefore interpret these requests as requiring user attention.

Expected

Auto-approved permissions should not emit a user-attention event.

Downstream impact

This currently affects at least:

• Orca: stablyai/orca#18950
• Warp: warpdotdev/opencode-warp#26

The Warp PR works around the race downstream by delaying notifications briefly. Fixing the distinction upstream would avoid integrations needing their own suppression logic.

Proposed direction

#47754 moves the Auto decision server-side so covered requests can be resolved before permission.asked is emitted.

The remaining design question is whether TUI Auto should continue affecting all sessions on the connected server, as it effectively does today, or only the current session.

Plugins

No response

OpenCode version

1.18.29

Steps to reproduce

1. Run OpenCode in Warp or Orca.
2. Enable Auto mode.
3. Start a task with permission-gated tool calls.
4. Observe repeated permission / blocked notifications.
5. The agent continues without requiring input.

Screenshot and/or share link

No response

Operating System

macOS 27.0 Beta (26A5421a)

Terminal

Warp.dev & Orca

Related

#47675 restores the permission.ask plugin hook, allowing a plugin verdict to resolve a request before permission.asked is emitted. It is related because both changes aim to resolve permission requests before they become user-attention events.