Answer: Background delegation lets the main agent launch a single custom agent in the background via run_workflow(agent://), which behaves like ordinary isolated delegation but is backgrounded so the parent chat stays available, the run is inspectable, and progress can return while it works. Sub-agents can be used by an agent running inside a Workflow when its configuration permits, and nested sub-agents help a workflow step divide its own task but are not nodes in the parent workflow and cannot signal, pause, complete, or revise that step on its behalf. Status: Confirmed Entry: tool/kiro/agents-and-automation/background-delegation-sub-agents Revision: 1 Digest: sha256:0b39b78f5ca62c8a (changes whenever the content changes) Timeline: Created: 2026-11-13T03:46:52Z Last changed: 2026-11-13T03:46:52Z Last verified: 2026-11-20T13:34:26Z Next check: 2026-11-21T13:34:26Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of background delegation command | run_workflow(agent://) | [1] | 2026-11-20 backgrounded behavior | the parent chat stays available, the run is inspectable, and progress can return while it works | [1] | 2026-11-20 version for Workflow use controls | 2.34 | [1] | 2026-11-20 sub-agents inside Workflow | That agent can still use sub-agents when its configuration permits it | [1] | 2026-11-20 nested sub-agents limitation | They are not nodes in the parent workflow and cannot signal, pause, complete, or revise that step on its behalf. | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Workflows - Features - Docs - Kiro". https://kiro.dev/docs/workflows/ Role: primary. Accessed: 2026-11-20T13:34:26Z Quote: "the main agent can launch run_workflow(agent://)" (Supports: background delegation command) Quote: "the parent chat stays available, the run is inspectable, and progress can return while it works" (Supports: backgrounded behavior) Quote: "In Kiro CLI 2.34 or later, Workflow use controls when the main chat starts Workflows." (Supports: version for Workflow use controls) Quote: "That agent can still use sub-agents when its configuration permits it" (Supports: sub-agents inside Workflow) Quote: "They are not nodes in the parent workflow and cannot signal, pause, complete, or revise that step on its behalf." (Supports: nested sub-agents limitation) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 77be89bfe81108ae40b4370341767cbf9ce6cf2bd51c2d76190e42b3fb8d135a (captured 2026-11-20T13:34:25Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:34:26Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:34:26Z Last attempt: 2026-11-20T13:34:26Z Notes and limitations: Extracted automatically from a single official source (section "Background delegation and sub-agents"). Related: https://latestn.com/tool/kiro/agents-and-automation/before-creating-task What should I do before creating a task when chatting with the Kiro agent? https://latestn.com/tool/kiro/agents-and-automation/bot-own-context How does a Kiro bot keep its own context? https://latestn.com/tool/kiro/agents-and-automation/bounded-exploration-workflow How do I set up a bounded exploration workflow in Kiro? https://latestn.com/tool/kiro/agents-and-automation/assign-tasks-from-github-issues How do I assign tasks to Kiro from GitHub issues? https://latestn.com/tool/kiro/agents-and-automation/automatic-agent-upgrade-on-start Does Kiro CLI V3 automatically upgrade agent configs when it starts, and is that safe? https://latestn.com/tool/kiro/agents-and-automation/available-agent-backends Which agent backends are available in Kiro Crew? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:46:52Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/agents-and-automation/background-delegation-sub-agents/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/agents-and-automation/background-delegation-sub-agents POST: https://latestn.com/dispute/tool/kiro/agents-and-automation/background-delegation-sub-agents with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/agents-and-automation/background-delegation-sub-agents?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do background delegation and sub-agents work in Kiro workflows? Revision 1, last verified 2026-11-20T13:34:26Z. https://latestn.com/tool/kiro/agents-and-automation/background-delegation-sub-agents (accessed 2026-11-21T10:08:19Z). @misc{LatestN_tool_kiro_agents_and_automation_background_delegation_sub_agents_r1, title = {How do background delegation and sub-agents work in Kiro workflows?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/agents-and-automation/background-delegation-sub-agents}}, note = {Revision 1; digest sha256:0b39b78f5ca62c8a; last verified 2026-11-20T13:34:26Z; accessed 2026-11-21T10:08:19Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/agents-and-automation/background-delegation-sub-agents