[FEATURE]: Restore per-session auto-accept permissions toggle in Desktop UI

[gabriel-ferraresi]

Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Description

In v1.4.0, the auto-accept permissions button was moved from the session-level UI to global Settings. This removed the ability to toggle auto-accept per session, which was a highly practical workflow feature.

Previous Behavior (v1.3.x)

• A toggle/icon was available directly in the session UI
• • Users could enable auto-accept for a specific session without affecting other sessions
• • • This allowed a quick "trust this session" workflow - one click and the session flowed without interruptions
• • • • When starting a new session, permissions defaulted back to the configured behavior

Current Behavior (v1.4.0)

• Auto-accept is now only available as a global setting in Settings
• • Enabling it affects all sessions across all projects
• • • There is no way to scope auto-accept to a single session anymore

Why Per-Session Was Better

1. Granular control: Users could decide trust level based on the specific task at hand
2. 2. Safety: A quick exploratory session could have auto-accept ON, while a production deployment session could keep confirmations
3. 3. Workflow speed: One click per session vs. navigating to Settings, toggling, working, then navigating back to toggle off
4. 4. Principle of least privilege: Global auto-accept is an all-or-nothing approach that goes against security best practices

Proposal

Restore the per-session auto-accept toggle in the Desktop session UI, while keeping the global setting in Settings as a default/override. This gives users both options:

• Global setting: Sets the default behavior for new sessions
• • Per-session toggle: Allows overriding for specific sessions

Environment

• OpenCode v1.4.0 Desktop (Windows 11)
• • Previously working in v1.3.17 and earlier

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• The title should start with [FEATURE]: (note the colon) to match the Feature Request template format. Currently it uses [Feature Request] which doesn't match.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

This issue might be a duplicate of existing issues. Please check:

• Why Moved auto-accept permissions into Settings? #21423: Directly discusses the same change of moving auto-accept permissions to Settings
• [FEATURE]:Add "Accept for Session" Option for Permission Prompts #3419: Requests "Accept for Session" option for permission prompts (same concept)
• [Feature]: Runtime Permission Mode Toggle (like Claude Code's Shift+Tab) #7928: Requests a runtime permission mode toggle per-session (same concept)
• [Desktop/Web] Auto-accept permissions gets turned on for every conversation #15589: Auto-accept permissions getting applied across all conversations (related)
• [FEATURE]: Enabling dynamically changing agents and permissions while running prompt #5963: Enabling dynamically changing permissions while running a prompt (related)

If you believe this was flagged incorrectly, please let a maintainer know.

[gabriel-ferraresi]

Thanks for flagging the related issues. This is indeed related to #3419 and #7928 - the core ask is the same: restore per-session granularity for auto-accept permissions, which was removed in v1.4.0 when it was moved to global Settings only. Adding my voice and specific use case details to support this request.

[github-actions]

Thanks for updating the issue! It now follows the contributing guidelines and feature request template. We appreciate you providing the version details and a clear description of the regression. Your request has been noted.

[WangWaud]

Can‘t agree more!