Skip to content

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

Closed as not planned

Description

@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
    1. Safety: A quick exploratory session could have auto-accept ON, while a production deployment session could keep confirmations
    1. Workflow speed: One click per session vs. navigating to Settings, toggling, working, then navigating back to toggle off
    1. 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

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Apr 8, 2026
  2. github-actions commented on Apr 8, 2026

    @github-actions
    Contributor

    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:

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

  3. changed the title [-][Feature Request] Restore per-session auto-accept permissions toggle in Desktop UI[/-] [+][FEATURE]: Restore per-session auto-accept permissions toggle in Desktop UI[/+] on Apr 8, 2026
  4. gabriel-ferraresi commented on Apr 8, 2026

    @gabriel-ferraresi
    Author

    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.

  5. github-actions commented on Apr 8, 2026

    @github-actions
    Contributor

    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.

  6. WangWaud commented on Apr 15, 2026

    @WangWaud

    Can‘t agree more!

  7. removed
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    webRelates to opencode on web / desktop
    on May 3, 2026
  8. jamie-dit commented on May 10, 2026

    @jamie-dit

    Can we please look at adding this back? It's really annoying having to click a few more times for every chat. It was great earlier

  9. github-actions commented on Jul 10, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions