Skip to content
Nested Sub-Agents in OrchestKit
On Trove · from Yonatan Gross

Nested Sub-Agents in OrchestKit

Adopting CC 2.1.172–2.1.173

Load when adding or debugging nested sub-agent chains in OrchestKit, depth limits, delegation docs, or CI guards for declared tools.

Read a preview

You can read the contents and the first 2,000 characters.
Free accounts get the whole book.

  • By Yonatan Gross
  • 7 chapters
  • Updated Nov 8, 2026
  • 43 readers

What’s inside

  • 1. Context & Timeline
  • 2. PR #2368 — Making Nesting Observable
  • 3. PR #2370 — Making Nesting Usable
  • 4. Design Decisions & Trade-offs
  • 5. Verification
  • 6. Reusable Patterns

What is Nested Sub-Agents in OrchestKit?

Load when adding or debugging nested sub-agent chains in OrchestKit, depth limits, delegation docs, or CI guards for declared tools. How OrchestKit 8.33.0 adopted Claude Code nested sub-agents (5-level chains) and /release-notes across PRs #2368 and #2370 — Pattern 9, depth registry, delegation docs, and CI guards.

Read more

Yonatan Gross · markdown · Listed Jun 11, 2026

  • agents
  • best-practices
  • anthropic
  • books-for-agents
  • general-agents

From the first page

How OrchestKit adopted Claude Code's nested sub-agent capability (CC 2.1.172) and the /release-notes command (CC 2.1.173), shipped in OrchestKit 8.33.0 on 2026-06-11 across two PRs. This book documents what changed, why each design call was made, how it was verified, and the reusable patterns that fell out.

1. Context & Timeline 2. PR #2368 — Making Nesting Observable 3. PR #2370 — Making Nesting Usable 4. Design Decisions & Trade-offs 5. Verification 6. Reusable Patterns

Two adjacent Claude Code releases unlocked capability that OrchestKit had previously only declared:

OrchestKit adopted both in two passes, both merged 2026-06-11 and released together as OrchestKit 8.33.0:

The sequencing is deliberate: the first pass instrumented and documented the capability so that nesting could be seen; the second pass wired the capability into agent prompts and runtime so it could actually be used. (See Section 6 — the adopt-in-two-passes pattern.)

The first pass focused on documentation, telemetry, and a nudge — establishing the conceptual model and the observability surface before

Preview · 2,000 of 11,544 characters

Web Application Security for AI Agents
Building Your Agent Team: A Practitioner's Guide to Multi-Agent AI Systems
Inside Claude Code: The Architecture
Show, Don't Sell

Contents

  1. 01Nested Sub-Agents in OrchestKit: Adopting CC 2.1.172–2.1.173p.1
  2. 021. Context & Timelinep.2
  3. 032. PR #2368 — Making Nesting Observablep.3
    1. 2.1 chain-patterns Pattern 9 — Nested Delegationp.3
    2. 2.2 Per-skill compatibility note, not a floor bumpp.3
    3. 2.3 subagent-validator telemetryp.3
    4. 2.4 cc-version-check nudges /release-notesp.3
    5. 2.5 Two drive-by hook bugfixesp.3
  4. 043. PR #2370 — Making Nesting Usablep.4
    1. 3.1 Layer 1 — Agent prompts (the delegation sweep)p.4
    2. 3.2 Layer 2 — Runtime depth injectionp.4
    3. 3.3 Layer 3 — Orchestration skillsp.4
    4. 3.4 CI guard — declarations can't drift from docsp.4
  5. 054. Design Decisions & Trade-offsp.5
    1. Known debtp.5
  6. 065. Verificationp.6
  7. 076. Reusable Patternsp.7
    1. Adopt in two passes — observable first, usable secondp.7
    2. Document-declared-tools-or-they're-deadp.7
    3. Spawn-time self-limiting beats post-hoc warningsp.7