Skip to content

[FEATURE]: Subagent view - permission requests #15332

Closed as not planned
Closed as not planned

Description

@seggcsont

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

Currently, when a subagent requests permission, the prompt appears under the main agent. As a result, when multiple agents are running in parallel, it is not clear which specific agent is requesting approval. Additionally, if I am monitoring the subagent’s messages, I cannot see that it is waiting for permission or understand the reason for the delay. I have to navigate back to the parent agent to verify whether a permission request is pending.

Proposal

When a subagent requests permission, the approval dialog should open directly within the subagent’s view. This would make it immediately visible that the specific agent is waiting for approval.

In the parent agent view, the system should clearly indicate which subagent requires manual intervention — for example, by highlighting it, flashing a visual indicator, or providing a direct link that navigates to the relevant subagent.

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Feb 27, 2026
  2. changed the title [-][FEATURE]: Subagent level UI permission requests[/-] [+][FEATURE]: Subagent view - permission requests[/+] on Feb 27, 2026
  3. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on Feb 27, 2026
  4. ck3mp3r commented on Mar 1, 2026

    @ck3mp3r

    It would indeed be great if the sub-agent permission request actually shows more context than: I want to run "command" but not "command some argument some other argument". In the case of MCP tool calls, the context is completely lost and you have to switch to the agent view just to be able to follow...

  5. assigned and unassigned on Apr 26, 2026
  6. removed
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on May 3, 2026
  7. github-actions commented on Jul 3, 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