{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreieglebxoalz4ylvxb7ad6f3ppll4cv6qw6ekewyfyvc2a6a5i75nm",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mmfgwkiytsj2"
  },
  "path": "/t/how-are-you-managing-the-use-of-explicitly-spawned-subagents/1381187#post_3",
  "publishedAt": "2026-05-21T20:23:31.000Z",
  "site": "https://community.openai.com",
  "textContent": "The failure mode I keep seeing with explicit subagents is not just context loss, it is missing lifecycle proof. Once a child is spawned, the parent needs a small receipt for requested role, resolved model or tools, task boundary, spend or time budget, and why the child stopped. Otherwise teams either duplicate work because silence looks like failure, or trust output they cannot audit later. The orchestration layer gets calmer once child admission and child completion are both visible artifacts instead of hidden runtime state.",
  "title": "How are you managing the use of explicitly spawned subagents?"
}