-
Notifications
You must be signed in to change notification settings - Fork 11.7k
Description
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
I have an primary agent which orchestrates the tasks for a session by delegating to subagents. The subagents edit and bash permissions are set to ask to that it's clear what they are doing without me having to view/check in on each session. It's more of a safety measure and a means to make sure they're staying on-task.
It does limit workflow throughput.
I think being able to set a permission for specific primary agents to be able to approve/grant subagent permissions would be a good way to keep things safe while also keeping things progressing.
The orchestrating agent has the 'big picture' context of what is going on. It uses a high-intelligence model like Opus 4.5 Thinking Max. It likely would be able to stop a less-intelligent subagent from doing something it shouldn't. It creates a check and balance, a middle ground between the permissions 'allow' and 'ask'. It also helps people develop agentic systems in which one agent is 'overseen' by another, which is a critical aspect of developing working long-horizon agentic systems.
A primary agent with the permission to grant subagents permission to edit or bash would be very useful for non-coding workflows where document drafting and creation differs from a codebase and artifacts can accumulate and create 'noise' and conflicting context. Limiting what gets written, and being aware of what gets edited and why, it a critical part of working non-coding projects.
This permission to grant permission also aids coding workflows. A not-so-smart coding subagent can be 'managed' by a smart orchestrating agent without being 'let loose'. Rather than using rules and restrictions to 'force' subagents to specific behaviors (which can often causes conflicts, inefficiencies, and more problems), the workflow can rely upon smart models managing less smart models where each agent is given discretion and can maximize autonomy.
The end-point to which this feature serves is eventually, an agent asks for a tool and the orchestrator can decide to grant it or persist the session with the subagent to ask for more details about why the agent wants to edit or bash.
Related to:
[Improvement] The ability to guide subagents on the right path (#2378)