You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maka.apache.org by "1625567290 (via GitHub)" <gi...@apache.org> on 2026/09/02 05:55:31 UTC

[I] proposal(runtime): let the root Agent create a bounded task-specific Sub Agent [maka]

1625567290 opened a new issue, #4538:
URL: https://github.com/apache/maka/issues/4538

   ## Problem
   
   The root Agent can delegate work through `agent_spawn`, but every child must be selected from `agent_list` by `subagent_id` or from a legacy built-in profile. The root Agent can describe the task, but it cannot create a bounded task-specific child role when none of the configured presets fits.
   
   This makes one-off delegation depend on configuration prepared before the task is understood. Users must either anticipate every specialization in Settings, accept an ill-fitting preset, interrupt the workflow to add one, or keep the work in the root Agent.
   
   The missing capability is not unrestricted Agent creation. It is a narrow way for the root Agent to instantiate a temporary child whose task-specific instructions are chosen at delegation time while its authority remains inside a user-approved envelope.
   
   ## Desired outcome
   
   Allow the root Agent to create a temporary, task-specific Sub Agent without requiring a matching named preset in advance.
   
   - The user explicitly enables an ad hoc child policy and selects its maximum authority.
   - The root Agent may provide a bounded display name, purpose, and task-specific instructions.
   - Runtime, not the root Agent, chooses or validates the permitted model, tool profile, permission ceiling, workspace boundary, write-back modes, lifecycle, and nesting depth.
   - The child remains a normal linked child Session/AgentRun with the existing lineage, event, inspection, cancellation, recovery, and artifact semantics.
   - The root Agent cannot grant capabilities it does not have or widen the user's configured envelope.
   - Existing configured presets remain the preferred path for repeatable roles and exact model selection.
   - Disabling ad hoc creation removes the route from `agent_list`/`agent_spawn` rather than relying only on prompt instructions.
   
   One possible model-facing shape is a Host-authorized synthetic catalog entry such as `temporary-bounded`, selected through the existing `subagent_id` flow, with a separate bounded role description. The exact protocol is less important than keeping policy authority out of model-provided fields.
   
   ## Acceptance criteria
   
   1. With ad hoc creation disabled, current `agent_list` and `agent_spawn` behavior is unchanged.
   2. With it enabled, the root Agent can spawn a task-specific child without first creating a named preset in Settings.
   3. The child receives the delegated task and bounded role instructions, but its effective model, tools, permissions, workspace access, write-back policy, lifecycle, and nesting depth cannot exceed the user-approved envelope.
   4. Invalid or over-broad requests fail before a child Session or AgentRun is created and explain which boundary was rejected.
   5. The resulting child is visible and inspectable through the same linked-session and `agent_output` paths as configured children.
   6. Parent cancellation, restart recovery, transcript isolation, and artifact lookup retain their current behavior.
   7. Prompt injection in parent content cannot enable the feature, alter the authority envelope, or create nested children.
   
   ## Non-goals
   
   - Background child execution, steering, or independent cancellation; those belong to #3540
   - Letting the root Agent choose arbitrary credentials, providers, tools, permission modes, or filesystem access
   - Replacing user-configured reusable Sub Agent presets
   - Allowing Side Conversations or child Agents to create further children
   - Adding a second Sub Agent runtime, ledger, or Session type
   
   ## Related
   
   - #49 established child execution on the existing runtime spine and originally discussed an inline Agent specification.
   - #3540 covers background lifecycle, steering, visibility, and stopping; this proposal is limited to how a foreground child role is selected and authorized.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org


Re: [I] proposal(runtime): let the root Agent create a bounded task-specific Sub Agent [maka]

Posted by "Astro-Han (via GitHub)" <gi...@apache.org>.
Astro-Han commented on issue #4538:
URL: https://github.com/apache/maka/issues/4538#issuecomment-5717643279

   The implementation attempt for this was closed in #4701: a policy that still requires the user to pick profile, connection and model in Settings before the route exists is a preset under another name, and one general-purpose preset plus the `task` text `agent_spawn` already takes covers acceptance items 1 through 7. Before any implementation is worth opening again, the open design question needs an answer: what does the root Agent gain that a preset cannot give, without model-authored text entering the child's system prompt and without a second settings shape beside `SubagentPreset`. That is a design conversation rather than a tracked work item, so please open it at https://github.com/apache/maka/discussions and we can reopen or file a scoped issue once it settles.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org


Re: [I] proposal(runtime): let the root Agent create a bounded task-specific Sub Agent [maka]

Posted by "testikun (via GitHub)" <gi...@apache.org>.
testikun commented on issue #4538:
URL: https://github.com/apache/maka/issues/4538#issuecomment-5521417142

   > *This was generated by AI during triage.*
   
   I’d like to take a bounded foreground child-creation slice, subject to maintainer alignment on the protocol shape.
   
   Scope:
   - reuse the existing `agent_list`/`agent_spawn`, linked-session, and Runtime Host authority paths;
   - allow a temporary task-specific role only when the user has explicitly enabled the ad-hoc policy;
   - enforce model, tool, permission, workspace, write-back, lifecycle, and nesting ceilings in Runtime/Host code, never from model-provided fields;
   - reject invalid or over-broad requests before creating a Session or AgentRun;
   - preserve configured presets, lineage, cancellation, recovery, and transcript isolation; do not add background children or nested creation.
   
   I’ll map the current protocol and add boundary tests first, then implement the smallest compatible path.
   
   **中文摘要:** 认领有界的临时 Sub Agent 创建能力,复用现有运行时和权限边界,禁止模型自行扩大能力或创建嵌套子代理。


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org


Re: [I] proposal(runtime): let the root Agent create a bounded task-specific Sub Agent [maka]

Posted by "testikun (via GitHub)" <gi...@apache.org>.
testikun commented on issue #4538:
URL: https://github.com/apache/maka/issues/4538#issuecomment-5521242480

   > *This was generated by AI during triage.*
   
   I’d like to take this proposal and work on the bounded foreground slice described here.
   
   Proposed scope:
   
   - Allow an explicitly enabled, task-specific child to use the existing linked child Session/AgentRun path.
   - Keep model, tool profile, permission ceiling, workspace boundary, write-back mode, lifecycle, and nesting depth selected and enforced by Runtime.
   - Preserve fresh identity, lineage, cancellation, recovery, transcript isolation, and artifact semantics; leave background lifecycle/steering and nested children out of scope.
   - Add protocol and runtime coverage for authority rejection and prompt-injection resistance.
   
   I’ll keep this limited to the bounded policy and creation path in the issue.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org


Re: [I] proposal(runtime): let the root Agent create a bounded task-specific Sub Agent [maka]

Posted by "Astro-Han (via GitHub)" <gi...@apache.org>.
Astro-Han commented on issue #4538:
URL: https://github.com/apache/maka/issues/4538#issuecomment-5549012315

   Closed #4701 with reasoning there. Short version for this issue: a policy that still requires the user to pick profile, connection and model in Settings before the route exists is a preset under another name, so it does not remove the pre-configuration this proposal is about; one general-purpose preset plus `agent_spawn`'s `task` text already covers acceptance 1–7.
   
   If someone wants to pick this up again, the design question to answer first is what the root Agent gets that a preset cannot give, without model-authored text entering the child's system prompt and without a second settings shape next to `SubagentPreset`. Until there is an answer to that, I would not open another implementation.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org


Re: [I] proposal(runtime): let the root Agent create a bounded task-specific Sub Agent [maka]

Posted by "Astro-Han (via GitHub)" <gi...@apache.org>.
Astro-Han closed issue #4538: proposal(runtime): let the root Agent create a bounded task-specific Sub Agent
URL: https://github.com/apache/maka/issues/4538


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org