@chankov/agent-fleet 2.0.3 → 2.0.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (452) hide show
  1. package/.pi/agents/model-profiles.yaml +64 -13
  2. package/.pi/agents/peers.yaml +11 -8
  3. package/.pi/harnesses/agent-hub/README.md +4 -2
  4. package/.pi/harnesses/agent-hub/config/agents.ts +13 -14
  5. package/.pi/harnesses/agent-hub/config/model-profiles.ts +216 -0
  6. package/.pi/harnesses/agent-hub/dispatch-coms.ts +6 -4
  7. package/.pi/harnesses/agent-hub/dispatch-native-prepare.ts +6 -3
  8. package/.pi/harnesses/agent-hub/dispatch-native.ts +4 -1
  9. package/.pi/harnesses/agent-hub/index.ts +61 -9
  10. package/.pi/harnesses/agent-hub/lifecycle/session-orchestration.ts +7 -7
  11. package/.pi/harnesses/agent-hub/package.json +1 -1
  12. package/.pi/harnesses/agent-hub/policy/models.ts +35 -8
  13. package/.pi/harnesses/agent-hub/policy/profile-activation.ts +62 -0
  14. package/.pi/harnesses/agent-hub/policy/profile-runtime.ts +64 -0
  15. package/.pi/harnesses/agent-hub/provider-semaphore.js +1 -1
  16. package/.pi/harnesses/agent-hub/research/spawn-run.ts +2 -1
  17. package/.pi/harnesses/agent-hub/spawn.ts +17 -1
  18. package/.pi/harnesses/agent-hub/tools/action-executors.ts +2 -0
  19. package/.pi/harnesses/agent-hub/tools/herdr-executors.ts +2 -0
  20. package/.pi/harnesses/agent-hub/ui/detail-panel.ts +4 -1
  21. package/.pi/harnesses/coms/package.json +1 -1
  22. package/.pi/harnesses/damage-control-continue/package.json +1 -1
  23. package/.versions/2.0.4/.pi/agents/dispatch-policy.yaml +32 -0
  24. package/.versions/2.0.4/.pi/agents/model-profiles.yaml +78 -0
  25. package/.versions/2.0.4/.pi/agents/peers.yaml +145 -0
  26. package/.versions/2.0.4/.pi/agents/teams.yaml +41 -0
  27. package/.versions/2.0.4/.pi/agents/voices.yaml +13 -0
  28. package/.versions/2.0.4/.pi/damage-control-rules.yaml +297 -0
  29. package/.versions/2.0.4/.pi/extensions/agent-fleet-update-check/README.md +57 -0
  30. package/.versions/2.0.4/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
  31. package/.versions/2.0.4/.pi/extensions/agent-fleet-update-check/package.json +6 -0
  32. package/.versions/2.0.4/.pi/extensions/btw/README.md +120 -0
  33. package/.versions/2.0.4/.pi/extensions/btw/index.ts +914 -0
  34. package/.versions/2.0.4/.pi/extensions/btw/package.json +6 -0
  35. package/.versions/2.0.4/.pi/extensions/btw/state.js +179 -0
  36. package/.versions/2.0.4/.pi/extensions/chrome-devtools-mcp/README.md +55 -0
  37. package/.versions/2.0.4/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
  38. package/.versions/2.0.4/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  39. package/.versions/2.0.4/.pi/extensions/compact-and-continue/README.md +42 -0
  40. package/.versions/2.0.4/.pi/extensions/compact-and-continue/index.ts +120 -0
  41. package/.versions/2.0.4/.pi/extensions/compact-and-continue/package.json +6 -0
  42. package/.versions/2.0.4/.pi/extensions/mcp-bridge/README.md +46 -0
  43. package/.versions/2.0.4/.pi/extensions/mcp-bridge/index.ts +206 -0
  44. package/.versions/2.0.4/.pi/extensions/mcp-bridge/package.json +6 -0
  45. package/.versions/2.0.4/.pi/extensions/package-lock.json +1175 -0
  46. package/.versions/2.0.4/.pi/extensions/package.json +9 -0
  47. package/.versions/2.0.4/.pi/extensions/pi-voice-stt/README.md +205 -0
  48. package/.versions/2.0.4/.pi/extensions/pi-voice-stt/config.ts +198 -0
  49. package/.versions/2.0.4/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  50. package/.versions/2.0.4/.pi/extensions/pi-voice-stt/index.ts +248 -0
  51. package/.versions/2.0.4/.pi/extensions/pi-voice-stt/package.json +6 -0
  52. package/.versions/2.0.4/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  53. package/.versions/2.0.4/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  54. package/.versions/2.0.4/.pi/harnesses/agent-hub/README.md +1160 -0
  55. package/.versions/2.0.4/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  56. package/.versions/2.0.4/.pi/harnesses/agent-hub/artifacts.js +146 -0
  57. package/.versions/2.0.4/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
  58. package/.versions/2.0.4/.pi/harnesses/agent-hub/backend-policy.js +174 -0
  59. package/.versions/2.0.4/.pi/harnesses/agent-hub/budget-continuation.ts +73 -0
  60. package/.versions/2.0.4/.pi/harnesses/agent-hub/capability-confirmation.ts +47 -0
  61. package/.versions/2.0.4/.pi/harnesses/agent-hub/capability-packs.ts +180 -0
  62. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/agent-model-thinking.ts +10 -0
  63. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/agent-model.ts +10 -0
  64. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/agent-models-substitute.ts +10 -0
  65. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/agents-add.ts +9 -0
  66. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/agents-drop.ts +9 -0
  67. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/agents-history.ts +9 -0
  68. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/agents-kill.ts +10 -0
  69. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/agents-list.ts +9 -0
  70. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/agents-restart.ts +10 -0
  71. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/agents-save.ts +9 -0
  72. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/agents-team.ts +9 -0
  73. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/compound.ts +9 -0
  74. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/coms.ts +9 -0
  75. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/context-command.ts +9 -0
  76. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/context.ts +41 -0
  77. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/debate.ts +9 -0
  78. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/dispatch-policy.ts +9 -0
  79. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/handoff.ts +10 -0
  80. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/hub-report.ts +9 -0
  81. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/models.ts +10 -0
  82. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/poll.ts +9 -0
  83. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/watchdog.ts +9 -0
  84. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/work-mode.ts +29 -0
  85. package/.versions/2.0.4/.pi/harnesses/agent-hub/commands/zoom.ts +10 -0
  86. package/.versions/2.0.4/.pi/harnesses/agent-hub/config/agents.ts +179 -0
  87. package/.versions/2.0.4/.pi/harnesses/agent-hub/config/model-profiles.ts +216 -0
  88. package/.versions/2.0.4/.pi/harnesses/agent-hub/config/overrides.ts +153 -0
  89. package/.versions/2.0.4/.pi/harnesses/agent-hub/context/agent-state.ts +30 -0
  90. package/.versions/2.0.4/.pi/harnesses/agent-hub/context/assertions-artifacts.ts +211 -0
  91. package/.versions/2.0.4/.pi/harnesses/agent-hub/context/budgets.ts +208 -0
  92. package/.versions/2.0.4/.pi/harnesses/agent-hub/context/hub-state.ts +40 -0
  93. package/.versions/2.0.4/.pi/harnesses/agent-hub/context-budget-snapshot.ts +105 -0
  94. package/.versions/2.0.4/.pi/harnesses/agent-hub/context-pressure.ts +191 -0
  95. package/.versions/2.0.4/.pi/harnesses/agent-hub/context-window.js +106 -0
  96. package/.versions/2.0.4/.pi/harnesses/agent-hub/debate-command.ts +176 -0
  97. package/.versions/2.0.4/.pi/harnesses/agent-hub/delegate.ts +446 -0
  98. package/.versions/2.0.4/.pi/harnesses/agent-hub/dispatch-coms.ts +234 -0
  99. package/.versions/2.0.4/.pi/harnesses/agent-hub/dispatch-core.ts +27 -0
  100. package/.versions/2.0.4/.pi/harnesses/agent-hub/dispatch-native-complete.ts +135 -0
  101. package/.versions/2.0.4/.pi/harnesses/agent-hub/dispatch-native-prepare.ts +156 -0
  102. package/.versions/2.0.4/.pi/harnesses/agent-hub/dispatch-native-spawn.ts +191 -0
  103. package/.versions/2.0.4/.pi/harnesses/agent-hub/dispatch-native-types.ts +207 -0
  104. package/.versions/2.0.4/.pi/harnesses/agent-hub/dispatch-native.ts +187 -0
  105. package/.versions/2.0.4/.pi/harnesses/agent-hub/dispatch-observability.ts +220 -0
  106. package/.versions/2.0.4/.pi/harnesses/agent-hub/docs-lane.js +122 -0
  107. package/.versions/2.0.4/.pi/harnesses/agent-hub/drift-watchdog.js +218 -0
  108. package/.versions/2.0.4/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  109. package/.versions/2.0.4/.pi/harnesses/agent-hub/external-blocker.js +85 -0
  110. package/.versions/2.0.4/.pi/harnesses/agent-hub/fixtures/registration-surface.json +55 -0
  111. package/.versions/2.0.4/.pi/harnesses/agent-hub/footer.ts +30 -0
  112. package/.versions/2.0.4/.pi/harnesses/agent-hub/helpers.ts +266 -0
  113. package/.versions/2.0.4/.pi/harnesses/agent-hub/hub-state-audit.js +59 -0
  114. package/.versions/2.0.4/.pi/harnesses/agent-hub/index.ts +2088 -0
  115. package/.versions/2.0.4/.pi/harnesses/agent-hub/input/completions.ts +76 -0
  116. package/.versions/2.0.4/.pi/harnesses/agent-hub/input/shortcuts.ts +47 -0
  117. package/.versions/2.0.4/.pi/harnesses/agent-hub/lifecycle/context-pressure.ts +123 -0
  118. package/.versions/2.0.4/.pi/harnesses/agent-hub/lifecycle/monitor-session.ts +104 -0
  119. package/.versions/2.0.4/.pi/harnesses/agent-hub/lifecycle/session-orchestration.ts +141 -0
  120. package/.versions/2.0.4/.pi/harnesses/agent-hub/lifecycle/turn-handlers.ts +95 -0
  121. package/.versions/2.0.4/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  122. package/.versions/2.0.4/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
  123. package/.versions/2.0.4/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
  124. package/.versions/2.0.4/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  125. package/.versions/2.0.4/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  126. package/.versions/2.0.4/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  127. package/.versions/2.0.4/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  128. package/.versions/2.0.4/.pi/harnesses/agent-hub/monitor-session-bridge.ts +266 -0
  129. package/.versions/2.0.4/.pi/harnesses/agent-hub/package.json +7 -0
  130. package/.versions/2.0.4/.pi/harnesses/agent-hub/peer-spawn-plan.ts +116 -0
  131. package/.versions/2.0.4/.pi/harnesses/agent-hub/policy/models.ts +153 -0
  132. package/.versions/2.0.4/.pi/harnesses/agent-hub/policy/profile-activation.ts +62 -0
  133. package/.versions/2.0.4/.pi/harnesses/agent-hub/policy/profile-runtime.ts +64 -0
  134. package/.versions/2.0.4/.pi/harnesses/agent-hub/policy/roster.ts +79 -0
  135. package/.versions/2.0.4/.pi/harnesses/agent-hub/policy/work-mode.ts +118 -0
  136. package/.versions/2.0.4/.pi/harnesses/agent-hub/poll-command.ts +176 -0
  137. package/.versions/2.0.4/.pi/harnesses/agent-hub/presentation.ts +48 -0
  138. package/.versions/2.0.4/.pi/harnesses/agent-hub/prompts/context.ts +46 -0
  139. package/.versions/2.0.4/.pi/harnesses/agent-hub/prompts/fragments.ts +115 -0
  140. package/.versions/2.0.4/.pi/harnesses/agent-hub/prompts/session-start.ts +90 -0
  141. package/.versions/2.0.4/.pi/harnesses/agent-hub/prompts/system-prompt.ts +110 -0
  142. package/.versions/2.0.4/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
  143. package/.versions/2.0.4/.pi/harnesses/agent-hub/research/controls.ts +74 -0
  144. package/.versions/2.0.4/.pi/harnesses/agent-hub/research/runtime.ts +175 -0
  145. package/.versions/2.0.4/.pi/harnesses/agent-hub/research/spawn-run.ts +144 -0
  146. package/.versions/2.0.4/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  147. package/.versions/2.0.4/.pi/harnesses/agent-hub/return-contract.js +293 -0
  148. package/.versions/2.0.4/.pi/harnesses/agent-hub/return-extract.js +75 -0
  149. package/.versions/2.0.4/.pi/harnesses/agent-hub/review-findings.js +102 -0
  150. package/.versions/2.0.4/.pi/harnesses/agent-hub/run-budget.js +537 -0
  151. package/.versions/2.0.4/.pi/harnesses/agent-hub/run-namespace.js +87 -0
  152. package/.versions/2.0.4/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  153. package/.versions/2.0.4/.pi/harnesses/agent-hub/scope-gate.js +103 -0
  154. package/.versions/2.0.4/.pi/harnesses/agent-hub/session-health.js +110 -0
  155. package/.versions/2.0.4/.pi/harnesses/agent-hub/session-start.ts +42 -0
  156. package/.versions/2.0.4/.pi/harnesses/agent-hub/spawn.ts +404 -0
  157. package/.versions/2.0.4/.pi/harnesses/agent-hub/timeline.ts +54 -0
  158. package/.versions/2.0.4/.pi/harnesses/agent-hub/tools/action-executors.ts +148 -0
  159. package/.versions/2.0.4/.pi/harnesses/agent-hub/tools/coms-tools.ts +139 -0
  160. package/.versions/2.0.4/.pi/harnesses/agent-hub/tools/context.ts +132 -0
  161. package/.versions/2.0.4/.pi/harnesses/agent-hub/tools/dispatch-agent.ts +79 -0
  162. package/.versions/2.0.4/.pi/harnesses/agent-hub/tools/dispatch-execution.ts +199 -0
  163. package/.versions/2.0.4/.pi/harnesses/agent-hub/tools/execution-orchestration.ts +22 -0
  164. package/.versions/2.0.4/.pi/harnesses/agent-hub/tools/fleet-tools.ts +202 -0
  165. package/.versions/2.0.4/.pi/harnesses/agent-hub/tools/herdr-executors.ts +84 -0
  166. package/.versions/2.0.4/.pi/harnesses/agent-hub/tools/set-task-tier.ts +29 -0
  167. package/.versions/2.0.4/.pi/harnesses/agent-hub/tools/spawn-research.ts +62 -0
  168. package/.versions/2.0.4/.pi/harnesses/agent-hub/tools/team-adjust.ts +29 -0
  169. package/.versions/2.0.4/.pi/harnesses/agent-hub/tools/verification-contract.ts +77 -0
  170. package/.versions/2.0.4/.pi/harnesses/agent-hub/types.ts +61 -0
  171. package/.versions/2.0.4/.pi/harnesses/agent-hub/ui/context-budget.ts +86 -0
  172. package/.versions/2.0.4/.pi/harnesses/agent-hub/ui/detail-panel.ts +178 -0
  173. package/.versions/2.0.4/.pi/harnesses/agent-hub/ui/fleet-dashboard.ts +123 -0
  174. package/.versions/2.0.4/.pi/harnesses/agent-hub/ui/grid.ts +144 -0
  175. package/.versions/2.0.4/.pi/harnesses/agent-hub/ui/history-store.ts +137 -0
  176. package/.versions/2.0.4/.pi/harnesses/agent-hub/ui/history.ts +234 -0
  177. package/.versions/2.0.4/.pi/harnesses/agent-hub/ui/pool.ts +103 -0
  178. package/.versions/2.0.4/.pi/harnesses/agent-hub/ui/zoom.ts +204 -0
  179. package/.versions/2.0.4/.pi/harnesses/agent-hub/version.ts +42 -0
  180. package/.versions/2.0.4/.pi/harnesses/agent-hub/work-mode-controls.ts +56 -0
  181. package/.versions/2.0.4/.pi/harnesses/agent-hub/work-mode.ts +167 -0
  182. package/.versions/2.0.4/.pi/harnesses/ask-user-remote/README.md +53 -0
  183. package/.versions/2.0.4/.pi/harnesses/ask-user-remote/index.ts +532 -0
  184. package/.versions/2.0.4/.pi/harnesses/ask-user-remote/race-core.js +106 -0
  185. package/.versions/2.0.4/.pi/harnesses/coms/README.md +100 -0
  186. package/.versions/2.0.4/.pi/harnesses/coms/index.ts +276 -0
  187. package/.versions/2.0.4/.pi/harnesses/coms/package.json +7 -0
  188. package/.versions/2.0.4/.pi/harnesses/coms/version.ts +42 -0
  189. package/.versions/2.0.4/.pi/harnesses/damage-control-continue/README.md +124 -0
  190. package/.versions/2.0.4/.pi/harnesses/damage-control-continue/index.ts +536 -0
  191. package/.versions/2.0.4/.pi/harnesses/damage-control-continue/package.json +7 -0
  192. package/.versions/2.0.4/.pi/harnesses/damage-control-continue/version.ts +42 -0
  193. package/.versions/2.0.4/.pi/harnesses/lib/coms-core-io.ts +385 -0
  194. package/.versions/2.0.4/.pi/harnesses/lib/coms-core.ts +577 -0
  195. package/.versions/2.0.4/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
  196. package/.versions/2.0.4/.pi/harnesses/lib/context-budget-child-prompt.ts +179 -0
  197. package/.versions/2.0.4/.pi/harnesses/lib/context-budget-hub-prompt.ts +114 -0
  198. package/.versions/2.0.4/.pi/harnesses/lib/context-budget-view.ts +107 -0
  199. package/.versions/2.0.4/.pi/harnesses/lib/context-budget.ts +114 -0
  200. package/.versions/2.0.4/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  201. package/.versions/2.0.4/.pi/harnesses/lib/fixtures/context-budget-profiles.json +11 -0
  202. package/.versions/2.0.4/.pi/harnesses/lib/fixtures/hub-prompt-operator.legacy.txt +73 -0
  203. package/.versions/2.0.4/.pi/harnesses/lib/fixtures/hub-prompt-orchestrator.legacy.txt +73 -0
  204. package/.versions/2.0.4/.pi/harnesses/lib/fleet-dashboard-ops.ts +166 -0
  205. package/.versions/2.0.4/.pi/harnesses/lib/fleet-dashboard-view.ts +142 -0
  206. package/.versions/2.0.4/.pi/harnesses/lib/fleet-detail-view.ts +247 -0
  207. package/.versions/2.0.4/.pi/harnesses/lib/fleet-overlay.ts +26 -0
  208. package/.versions/2.0.4/.pi/harnesses/lib/fleet-panel.ts +34 -0
  209. package/.versions/2.0.4/.pi/harnesses/lib/fleet-read-model.ts +131 -0
  210. package/.versions/2.0.4/.pi/harnesses/lib/fleet-selection.ts +24 -0
  211. package/.versions/2.0.4/.pi/harnesses/lib/fleet-transcript-store.ts +244 -0
  212. package/.versions/2.0.4/.pi/harnesses/lib/herdr-client.ts +472 -0
  213. package/.versions/2.0.4/.pi/harnesses/lib/herdr-presence.ts +399 -0
  214. package/.versions/2.0.4/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
  215. package/.versions/2.0.4/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  216. package/.versions/2.0.4/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
  217. package/.versions/2.0.4/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  218. package/.versions/2.0.4/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
  219. package/.versions/2.0.4/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  220. package/.versions/2.0.4/.pi/harnesses/lib/spawned-peers.js +190 -0
  221. package/.versions/2.0.4/.pi/harnesses/package-lock.json +2039 -0
  222. package/.versions/2.0.4/.pi/harnesses/package.json +10 -0
  223. package/.versions/2.0.4/.pi/prompts/af-build.md +24 -0
  224. package/.versions/2.0.4/.pi/prompts/af-code-simplify.md +22 -0
  225. package/.versions/2.0.4/.pi/prompts/af-plan.md +17 -0
  226. package/.versions/2.0.4/.pi/prompts/af-review.md +16 -0
  227. package/.versions/2.0.4/.pi/prompts/af-set-hermes-telegram.md +15 -0
  228. package/.versions/2.0.4/.pi/prompts/af-set-hermes-watchdog.md +6 -0
  229. package/.versions/2.0.4/.pi/prompts/af-ship.md +17 -0
  230. package/.versions/2.0.4/.pi/prompts/af-spec.md +15 -0
  231. package/.versions/2.0.4/.pi/prompts/af-test.md +19 -0
  232. package/.versions/2.0.4/.pi/skills/bowser/SKILL.md +145 -0
  233. package/.versions/2.0.4/.version +1 -0
  234. package/.versions/2.0.4/agents/architect.md +25 -0
  235. package/.versions/2.0.4/agents/bowser.md +28 -0
  236. package/.versions/2.0.4/agents/builder.md +56 -0
  237. package/.versions/2.0.4/agents/code-reviewer.md +210 -0
  238. package/.versions/2.0.4/agents/deep-researcher.md +33 -0
  239. package/.versions/2.0.4/agents/documenter.md +22 -0
  240. package/.versions/2.0.4/agents/orchestrator.md +23 -0
  241. package/.versions/2.0.4/agents/plan-reviewer.md +84 -0
  242. package/.versions/2.0.4/agents/planner.md +105 -0
  243. package/.versions/2.0.4/agents/releaser.md +25 -0
  244. package/.versions/2.0.4/agents/researcher.md +31 -0
  245. package/.versions/2.0.4/agents/security-auditor.md +168 -0
  246. package/.versions/2.0.4/agents/test-engineer.md +154 -0
  247. package/.versions/2.0.4/agents/web-debugger.md +44 -0
  248. package/.versions/2.0.4/agents/web-performance-auditor.md +194 -0
  249. package/.versions/2.0.4/bin/catalog/harness-runtime-closure.json +36 -0
  250. package/.versions/2.0.4/codex/CONDUCTOR.md +148 -0
  251. package/.versions/2.0.4/docs/ARCHITECTURE.md +407 -0
  252. package/.versions/2.0.4/docs/agent-fleet-setup.md +547 -0
  253. package/.versions/2.0.4/docs/claude-code-coms-bridge.md +133 -0
  254. package/.versions/2.0.4/docs/codex-remote-conductor.md +170 -0
  255. package/.versions/2.0.4/docs/coms-hermes-bridge.md +189 -0
  256. package/.versions/2.0.4/docs/getting-started.md +124 -0
  257. package/.versions/2.0.4/docs/npm-install.md +299 -0
  258. package/.versions/2.0.4/docs/pi-extensions.md +447 -0
  259. package/.versions/2.0.4/docs/pi-setup.md +74 -0
  260. package/.versions/2.0.4/docs/skill-anatomy.md +150 -0
  261. package/.versions/2.0.4/hermes/README.md +347 -0
  262. package/.versions/2.0.4/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
  263. package/.versions/2.0.4/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
  264. package/.versions/2.0.4/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  265. package/.versions/2.0.4/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  266. package/.versions/2.0.4/hermes/gates/gate-o-capability.md +8 -0
  267. package/.versions/2.0.4/hermes/gates/gate-o-validator-fixtures.json +1 -0
  268. package/.versions/2.0.4/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
  269. package/.versions/2.0.4/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
  270. package/.versions/2.0.4/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
  271. package/.versions/2.0.4/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
  272. package/.versions/2.0.4/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
  273. package/.versions/2.0.4/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
  274. package/.versions/2.0.4/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
  275. package/.versions/2.0.4/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
  276. package/.versions/2.0.4/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
  277. package/.versions/2.0.4/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
  278. package/.versions/2.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
  279. package/.versions/2.0.4/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  280. package/.versions/2.0.4/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  281. package/.versions/2.0.4/hermes/skills/hub-conductor/SKILL.md +84 -0
  282. package/.versions/2.0.4/hermes/skills/hub-liaison/SKILL.md +84 -0
  283. package/.versions/2.0.4/hermes/skills/hub-watchdog/SKILL.md +76 -0
  284. package/.versions/2.0.4/hermes/skills/hub-watchdog/manifest.json +1 -0
  285. package/.versions/2.0.4/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
  286. package/.versions/2.0.4/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
  287. package/.versions/2.0.4/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
  288. package/.versions/2.0.4/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
  289. package/.versions/2.0.4/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
  290. package/.versions/2.0.4/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
  291. package/.versions/2.0.4/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
  292. package/.versions/2.0.4/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
  293. package/.versions/2.0.4/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
  294. package/.versions/2.0.4/hermes/watchdog-tests/__init__.py +0 -0
  295. package/.versions/2.0.4/hooks/coms-stop-hook.mjs +84 -0
  296. package/.versions/2.0.4/install-manifest.json +2942 -0
  297. package/.versions/2.0.4/justfile +289 -0
  298. package/.versions/2.0.4/manifest-meta.json +969 -0
  299. package/.versions/2.0.4/references/accessibility-checklist.md +160 -0
  300. package/.versions/2.0.4/references/communication-contract.md +26 -0
  301. package/.versions/2.0.4/references/definition-of-done.md +67 -0
  302. package/.versions/2.0.4/references/fleet-coordination-patterns.md +171 -0
  303. package/.versions/2.0.4/references/observability-checklist.md +91 -0
  304. package/.versions/2.0.4/references/orchestration-patterns.md +370 -0
  305. package/.versions/2.0.4/references/performance-checklist.md +153 -0
  306. package/.versions/2.0.4/references/prompting-patterns.md +380 -0
  307. package/.versions/2.0.4/references/security-checklist.md +179 -0
  308. package/.versions/2.0.4/references/testing-patterns.md +236 -0
  309. package/.versions/2.0.4/references/workflow-authoring.md +304 -0
  310. package/.versions/2.0.4/scripts/claude-code-preflight.ts +70 -0
  311. package/.versions/2.0.4/scripts/codex-conductor.ts +41 -0
  312. package/.versions/2.0.4/scripts/codex-remote-control.ts +167 -0
  313. package/.versions/2.0.4/scripts/coms-claude-bridge.ts +411 -0
  314. package/.versions/2.0.4/scripts/coms-cli.ts +484 -0
  315. package/.versions/2.0.4/scripts/coms-hermes-bridge.ts +413 -0
  316. package/.versions/2.0.4/scripts/fleet.ts +222 -0
  317. package/.versions/2.0.4/scripts/flow.ts +137 -0
  318. package/.versions/2.0.4/scripts/hermes-monitor-capability-runner.ts +25 -0
  319. package/.versions/2.0.4/scripts/hermes-monitor-scenario.ts +474 -0
  320. package/.versions/2.0.4/scripts/hermes-watchdog-capability-probe.ts +45 -0
  321. package/.versions/2.0.4/scripts/install-hermes-plugin.sh +180 -0
  322. package/.versions/2.0.4/scripts/lib/claude-bridge-core.ts +210 -0
  323. package/.versions/2.0.4/scripts/lib/codex-conductor.ts +88 -0
  324. package/.versions/2.0.4/scripts/lib/codex-remote-control.ts +482 -0
  325. package/.versions/2.0.4/scripts/lib/coms-envelope.ts +582 -0
  326. package/.versions/2.0.4/scripts/lib/fake-herdr-server.ts +88 -0
  327. package/.versions/2.0.4/scripts/lib/fleet-command.ts +270 -0
  328. package/.versions/2.0.4/scripts/lib/flow-command.ts +93 -0
  329. package/.versions/2.0.4/scripts/lib/flow-maintenance.ts +230 -0
  330. package/.versions/2.0.4/scripts/lib/herdr-layout.ts +281 -0
  331. package/.versions/2.0.4/scripts/lib/hermes-bridge-core.ts +241 -0
  332. package/.versions/2.0.4/scripts/lib/hermes-monitor-events.ts +1 -0
  333. package/.versions/2.0.4/scripts/lib/hermes-monitor-herdr.ts +2 -0
  334. package/.versions/2.0.4/scripts/lib/hermes-monitor-model.ts +3 -0
  335. package/.versions/2.0.4/scripts/lib/hermes-monitor-registry.ts +2 -0
  336. package/.versions/2.0.4/scripts/lib/hermes-monitor-socket.ts +2 -0
  337. package/.versions/2.0.4/scripts/lib/hermes-monitor-store.ts +2 -0
  338. package/.versions/2.0.4/scripts/lib/monitor-env.ts +146 -0
  339. package/.versions/2.0.4/scripts/lib/peer-launch.ts +318 -0
  340. package/.versions/2.0.4/scripts/lib/persona-banner.ts +62 -0
  341. package/.versions/2.0.4/scripts/lib/runtime-dependencies.js +124 -0
  342. package/.versions/2.0.4/scripts/lib/spawn-stagger.ts +101 -0
  343. package/.versions/2.0.4/scripts/lib/team-project.ts +213 -0
  344. package/.versions/2.0.4/scripts/lib/team-snapshot.ts +147 -0
  345. package/.versions/2.0.4/scripts/package-lock.json +35 -0
  346. package/.versions/2.0.4/scripts/package.json +9 -0
  347. package/.versions/2.0.4/scripts/peer-banner.ts +40 -0
  348. package/.versions/2.0.4/scripts/peer-launch.ts +285 -0
  349. package/.versions/2.0.4/scripts/team-snapshot.ts +237 -0
  350. package/.versions/2.0.4/scripts/team-up.ts +406 -0
  351. package/.versions/2.0.4/scripts/workflows/lib/agent-phase.ts +133 -0
  352. package/.versions/2.0.4/scripts/workflows/lib/changes.ts +61 -0
  353. package/.versions/2.0.4/scripts/workflows/lib/debate.ts +149 -0
  354. package/.versions/2.0.4/scripts/workflows/lib/env.ts +34 -0
  355. package/.versions/2.0.4/scripts/workflows/lib/envelopes.ts +169 -0
  356. package/.versions/2.0.4/scripts/workflows/lib/gates.ts +81 -0
  357. package/.versions/2.0.4/scripts/workflows/lib/git.ts +96 -0
  358. package/.versions/2.0.4/scripts/workflows/lib/merge.ts +95 -0
  359. package/.versions/2.0.4/scripts/workflows/lib/model-profile.ts +22 -0
  360. package/.versions/2.0.4/scripts/workflows/lib/model-visibility.ts +92 -0
  361. package/.versions/2.0.4/scripts/workflows/lib/permissions.ts +130 -0
  362. package/.versions/2.0.4/scripts/workflows/lib/personas.ts +57 -0
  363. package/.versions/2.0.4/scripts/workflows/lib/poll.ts +86 -0
  364. package/.versions/2.0.4/scripts/workflows/lib/quality.ts +64 -0
  365. package/.versions/2.0.4/scripts/workflows/lib/run.ts +108 -0
  366. package/.versions/2.0.4/scripts/workflows/lib/trace.ts +34 -0
  367. package/.versions/2.0.4/scripts/workflows/lib/voices.ts +128 -0
  368. package/.versions/2.0.4/scripts/workflows/lib/writer-lease.ts +112 -0
  369. package/.versions/2.0.4/scripts/workflows/tsconfig.json +22 -0
  370. package/.versions/2.0.4/scripts/workflows/wf-build-test.ts +61 -0
  371. package/.versions/2.0.4/scripts/workflows/wf-debate.ts +87 -0
  372. package/.versions/2.0.4/scripts/workflows/wf-document.ts +50 -0
  373. package/.versions/2.0.4/scripts/workflows/wf-poll.ts +95 -0
  374. package/.versions/2.0.4/scripts/workflows/wf-quality.ts +20 -0
  375. package/.versions/2.0.4/scripts/workflows/wf-scout.ts +38 -0
  376. package/.versions/2.0.4/skills/_internal/grilling.md +59 -0
  377. package/.versions/2.0.4/skills/browser-testing-with-devtools/SKILL.md +351 -0
  378. package/.versions/2.0.4/skills/code-review-and-quality/SKILL.md +381 -0
  379. package/.versions/2.0.4/skills/compound-learning/SKILL.md +137 -0
  380. package/.versions/2.0.4/skills/context-engineering/SKILL.md +291 -0
  381. package/.versions/2.0.4/skills/deprecation-and-migration/SKILL.md +206 -0
  382. package/.versions/2.0.4/skills/designing-agents/SKILL.md +394 -0
  383. package/.versions/2.0.4/skills/designing-agents/pi-harness-authoring.md +222 -0
  384. package/.versions/2.0.4/skills/drafting-workflows/SKILL.md +143 -0
  385. package/.versions/2.0.4/skills/drafting-workflows/scripts/make-workflow.ts +177 -0
  386. package/.versions/2.0.4/skills/frontend-ui-engineering/SKILL.md +328 -0
  387. package/.versions/2.0.4/skills/git-workflow-and-versioning/SKILL.md +316 -0
  388. package/.versions/2.0.4/skills/idea-refine/SKILL.md +182 -0
  389. package/.versions/2.0.4/skills/idea-refine/examples.md +238 -0
  390. package/.versions/2.0.4/skills/idea-refine/frameworks.md +99 -0
  391. package/.versions/2.0.4/skills/idea-refine/refinement-criteria.md +113 -0
  392. package/.versions/2.0.4/skills/idea-refine/scripts/idea-refine.sh +15 -0
  393. package/.versions/2.0.4/skills/incremental-implementation/SKILL.md +298 -0
  394. package/.versions/2.0.4/skills/interview-me/SKILL.md +226 -0
  395. package/.versions/2.0.4/skills/orchestration-verification/SKILL.md +181 -0
  396. package/.versions/2.0.4/skills/peer-coms/SKILL.md +90 -0
  397. package/.versions/2.0.4/skills/performance-optimization/SKILL.md +350 -0
  398. package/.versions/2.0.4/skills/planning-and-task-breakdown/SKILL.md +265 -0
  399. package/.versions/2.0.4/skills/security-and-hardening/SKILL.md +461 -0
  400. package/.versions/2.0.4/skills/spec-driven-development/SKILL.md +256 -0
  401. package/.versions/2.0.4/skills/using-agent-skills/SKILL.md +197 -0
  402. package/.versions/2.0.4/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
  403. package/.versions/2.0.4/vendor/agent-skills-upstream/LICENSE +21 -0
  404. package/.versions/2.0.4/vendor/agent-skills-upstream/README.md +11 -0
  405. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
  406. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  407. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  408. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  409. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  410. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
  411. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  412. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  413. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
  414. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  415. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  416. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  417. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  418. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  419. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  420. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  421. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  422. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  423. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  424. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
  425. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
  426. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
  427. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
  428. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
  429. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
  430. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
  431. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
  432. package/.versions/2.0.4/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
  433. package/CHANGELOG.md +7 -0
  434. package/bin/catalog/harness-runtime-closure.json +2 -0
  435. package/bin/cli.js +47 -9
  436. package/bin/lib/doctor.js +35 -2
  437. package/bin/lib/reconcile.js +3 -2
  438. package/docs/agent-fleet-setup.md +74 -0
  439. package/docs/claude-code-coms-bridge.md +5 -0
  440. package/docs/getting-started.md +5 -0
  441. package/docs/npm-install.md +12 -5
  442. package/install-manifest.json +3 -1
  443. package/justfile +1 -1
  444. package/package.json +5 -3
  445. package/scripts/claude-code-preflight.ts +70 -0
  446. package/scripts/fleet.ts +23 -0
  447. package/scripts/lib/runtime-dependencies.js +124 -0
  448. package/scripts/peer-launch.ts +27 -1
  449. package/scripts/workflows/lib/agent-phase.ts +2 -1
  450. package/scripts/workflows/lib/model-profile.ts +22 -0
  451. package/scripts/workflows/lib/personas.ts +6 -3
  452. package/scripts/workflows/lib/voices.ts +3 -0
@@ -0,0 +1,1160 @@
1
+ # agent-hub
2
+
3
+ The unified Agent Fleet runtime for pi, with [`coms`](../coms/README.md) **embedded**. Bare
4
+ `just fleet` loads Fleet Core and starts `agent-hub` in **operator** work mode with direct coding
5
+ and orchestration tools, but no standing native roster. The same live session can switch to
6
+ **orchestrator** work mode, which removes direct coding tools and drives native specialists under
7
+ the Verification Contract. Fleet Core loads first: [`damage-control-continue`](../damage-control-continue/README.md),
8
+ [`ask-user-remote`](../ask-user-remote/README.md), STT, Compact & Continue, BTW, and the update
9
+ checker. Both work modes can adjust the native roster, run research, collaborate with Pi/Claude
10
+ peers, and hand the session to a visible coms peer.
11
+
12
+ > Consolidates the retired `agent-team` dispatcher into this harness and embeds the ported `coms`
13
+ > P2P layer from [`pi-vs-claude-code`](https://github.com/disler/pi-vs-claude-code) by
14
+ > [disler](https://github.com/disler) (MIT). See the
15
+ > [extension catalog](../../../docs/pi-extensions.md) and the
16
+ > [design plan](../../../docs/plans/agent-hub/).
17
+
18
+ **Optional phone control:** `just fleet --agents <roster> --peers <preset> --project <name>` can supply the live peers for the experimental [Codex Android conductor](https://github.com/chankov/agent-fleet/blob/main/docs/codex-remote-conductor.md). Configure Codex for the same project; do not also launch `just fleet conductor codex <team>` for the same peers. Hermes remains the inbound `ask_user` route, while Codex performs only human-confirmed, approval-gated outbound delegation.
19
+
20
+ ## Work Mode, roster, and topology
21
+
22
+ These are independent runtime axes:
23
+
24
+ - **Work Mode** — `/af-work-mode operator|orchestrator` switches prompt and active tools without
25
+ restarting or losing session state; `/af-work-mode` without an argument and **Alt+M** open the
26
+ two-option picker. Operator keeps `read`, `bash`, `edit`, `write`, approved extension tools, and
27
+ orchestration. Orchestrator withholds direct coding tools but keeps dispatch, research, assertions,
28
+ roster controls, `ask_user`, ready coms, and ready Herdr tools. In orchestrator work mode, raw
29
+ Herdr panes are auxiliary-process orchestration—not a route around delegation for reading,
30
+ editing, testing, or implementing code.
31
+ - **Native roster** — local headless Pi specialists from `.pi/agents/teams.yaml`. Bare Fleet starts
32
+ empty; select one with `--agents frontend` or add one live with `/af-agents-add code-reviewer`.
33
+ - **Peer topology** — separate long-lived Pi or Claude Code processes from `peers.yaml`, connected
34
+ by coms and optionally placed in sibling Herdr panes. `--peers frontend` selects a standing
35
+ preset; `--herdr` creates a Hub-only workspace through the empty `base` preset.
36
+ Orchestrator still requires a native roster. Budgets, nested delegation, and Verification Contract
37
+ rigor follow the **task tier**, not Work Mode.
38
+
39
+ All Hub slash commands, including `/af-handoff`, are registered in both work modes. A command whose
40
+ runtime capability is unavailable refuses with remediation rather than disappearing. `--no-coms`
41
+ disables only embedded coms; direct operator work and native dispatch remain available.
42
+
43
+ ### Automatic capability surfaces
44
+
45
+ Capability packs load **automatically** from the current request, work mode, task tier, pending work,
46
+ and runtime state; there is no activation command. `core` is always present. Orchestrator work mode
47
+ always includes `fleet`; explicit delegation/research, acceptance work, an existing coms peer, a
48
+ Herdr pane/watcher request, and explicit or imminent compaction respectively add `fleet`,
49
+ `verification`, `peer`, `workspace`, and `compaction`. A ready coms or Herdr runtime is only
50
+ **readiness**, not intent: its tools and policy remain model-inactive until requested.
51
+
52
+ Ambiguous delegation, peer, or workspace intent provisionally exposes the smallest relevant pack
53
+ and records its reason in the state capsule and `/af-context`. Before that pack's first side effect,
54
+ the Hub asks one focused `ask_user` confirmation. Confirming promotes it for the task; reject or
55
+ cancel removes it and leaves no message, child, or pane behind. Active task packs persist through
56
+ follow-up turns so a workflow does not lose tools. They shrink only through
57
+ `set_task_tier(new_task: true)` (apart from mandatory work mode and pending-operation leases), never
58
+ merely because the next message sounds different.
59
+
60
+ `/af-context` separates stable replacement-prompt cost from the volatile state capsule and active
61
+ schemas. Inactive and ready-but-inactive packs cost zero model-visible characters. Provider totals,
62
+ including cache read/write when Pi supplies them, remain authoritative; deterministic character
63
+ figures are regression diagnostics and never invent provider usage.
64
+
65
+ ### Context-pressure and resume recovery
66
+
67
+ Pre-turn surface cost and live conversation pressure are different budgets. `/af-context` separates
68
+ the stable replacement prompt, volatile state capsule, and active tool schemas; user and assistant
69
+ messages plus tool results then accumulate during a turn. A long tool loop can therefore reach the
70
+ model window even while every standing prompt ceiling remains green.
71
+
72
+ The Hub samples live provider usage and projects each finalized tool result before another model
73
+ request:
74
+
75
+ - Below **80%**, pressure is `normal`.
76
+ - At **80%**, pressure becomes `warning`; the compact recovery surface is exposed transiently and
77
+ ordinary work may continue.
78
+ - At **90%**, the Hub aborts the next same-turn provider request, waits until the tool result and
79
+ aborted turn are persisted, and starts one automatic Pi compaction. Only one recovery may run at
80
+ a time. Input received while startup or same-turn recovery is active is retained in memory,
81
+ including images, then replayed once after compaction succeeds.
82
+
83
+ The status line and `/af-context` show the pressure phase, measured usage, both thresholds, episode,
84
+ and last recovery outcome. Persisted pressure diagnostics contain numeric/enumerated metadata only;
85
+ they never include prompts, tool output, credentials, error bodies, or compaction summaries.
86
+
87
+ If automatic recovery reports `failed`, the queued input remains retained. Use Pi's built-in manual
88
+ fallback, or switch to a model with a larger context window:
89
+
90
+ ```text
91
+ /compact Preserve the current goal, decisions, assertions, pending operations, blockers, and next step.
92
+ ```
93
+
94
+ A resumed orchestrator session can also require roster recovery. The Hub persists only the selected
95
+ team name and resolves it again against the current `.pi/agents/teams.yaml` and persona files. If the
96
+ team is missing, renamed, empty, or stale, the Hub preserves orchestrator work mode, keeps direct coding
97
+ tools unavailable, and blocks model input rather than inventing a roster or silently downgrading.
98
+ Recover with one of these explicit choices:
99
+
100
+ ```text
101
+ /af-agents-team # select a currently valid team in the live session
102
+ /af-work-mode operator # explicitly leave delegate-only work mode and restore direct tools
103
+ just fleet --agents <name> # restart through the public Fleet CLI
104
+ just fleet --work-mode operator # restart explicitly as an operator
105
+ ```
106
+
107
+ For a direct Pi launch, the roster flag is `--agent-team <name>` and the work mode flag is
108
+ `--work-mode operator`; explicit startup flags take precedence over persisted selections. Fix stale
109
+ team/persona declarations before selecting them.
110
+
111
+ The Pi session JSONL under `~/.pi/agent/sessions/` is the authoritative append-only conversation and
112
+ recovery record. Context overflow or a stale roster does **not** by itself mean that file is corrupt.
113
+ Inspect it through `/session`, resume it through `/resume` or Pi's session flags, and recover through
114
+ compaction or the commands above. Never edit, truncate, reorder, or synthesize JSONL entries to
115
+ recover a session.
116
+
117
+ ## What it does
118
+
119
+ The whole dispatch loop, end to end:
120
+
121
+ ```mermaid
122
+ sequenceDiagram
123
+ autonumber
124
+ actor U as You
125
+ participant H as Hub (dispatcher)
126
+ participant S as Specialist (e.g. builder)
127
+ participant R as Research helper
128
+ participant D as Disk (.pi/agent-sessions/)
129
+
130
+ U->>H: task
131
+ H->>D: set_assertions — Verification Contract persisted
132
+ H->>S: dispatch_agent (task + advisory scope)
133
+ S-->>H: NEEDS_RESEARCH: how does X work?
134
+ H->>R: spawn_research (researcher / deep-researcher)
135
+ R->>D: write findings file
136
+ R-->>H: one-line notice + path
137
+ H->>S: resume with file paths — never raw findings
138
+ S-->>H: structured return + named evidence
139
+ H->>D: update_assertion
140
+ H-->>U: Assertions: 2✓ 1○ 1✗ · open: A4
141
+ ```
142
+
143
+ Every borrowed idea from another harness passes one test before it lands: *does this persistently enter the dispatcher context?* If yes, it goes to disk or a one-line status instead.
144
+
145
+ `agent-hub` is the supported home for the former standalone dispatcher features:
146
+
147
+ - **Dispatcher grid** — a live dashboard of the active, dynamically adjustable native roster from `.pi/agents/teams.yaml`.
148
+ - **Context budget** — `/af-context` opens a separate read-only full-screen diagnostic in either work mode. It shows provider totals and cache fields beside named, metadata-only estimates; `loaded-excluded` Pi inputs are discovered but contribute zero to the replacement Hub prompt. Each specialist, research helper, delegate, and peer remains a separate context plane with its own model window. Component token estimates are heuristic/provider-scaled, never exact claims; unavailable peer/provider detail is labelled explicitly and raw prompts, schemas, and conversation text are never retained or displayed.
149
+ - **Specialist delegation** — `dispatch_agent` sends writable tasks to configured specialists.
150
+ - **Research helpers** — the dispatcher invokes `spawn_research` automatically for read-only
151
+ investigation; specialists can trigger the separate automatic `NEEDS_RESEARCH:` pipe described
152
+ below. Managed research children use a replacement read-only prompt with `--no-skills` and
153
+ `--no-context-files`; managed specialists receive a selected context manifest (persona, applicable
154
+ policy paths, and named skill paths) rather than inherited global skill/context loading. Two
155
+ `kind: research` personas ship by default: `researcher` (`gpt-5.6-luna`, low thinking) for simple
156
+ reads and `deep-researcher` (`grok-4.6`, medium thinking) for hard, cross-cutting investigation.
157
+ The dispatcher routes by persona; each persona's model + thinking level is shown in its catalog.
158
+ Live helpers appear **only in the Fleet Dashboard (`Alt+A`)** while they are running — never as
159
+ cards or compact rows in the main dispatcher view. On every terminal outcome (success, error,
160
+ timeout, spawn/preflight failure, or operator kill) the live `rN` handle is removed immediately.
161
+ Session, transcript, and `findings/*.md` files remain on disk for the requester, and
162
+ `/af-agents-history` keeps the audit/timing record. Finished helpers cannot be restarted; a new
163
+ request always creates a fresh helper. `rN` handles are never reused during a Hub session.
164
+ - **Human handoff path** — `ask_user` is exposed by the `ask-user-remote` wrapper (capturing stock
165
+ `pi-ask-user` and optionally racing a `user-remote` bridge), so specialists can bubble decisions
166
+ back through the dispatcher.
167
+ - **Auto-research pipe (`NEEDS_RESEARCH:`)** — a specialist that lacks information pauses by ending
168
+ its turn with `NEEDS_RESEARCH: <question>` lines (mirror of the `ASK_USER:` protocol). The hub
169
+ intercepts them **in code**: it fans out read-only research helpers (max 4 questions per pause,
170
+ 2 pauses per dispatch), writes each helper's findings to `.pi/agent-sessions/findings/*.md`, and
171
+ resumes the specialist's session with the file paths. The dispatcher LLM sees only a one-line
172
+ notice — raw findings never enter its context. Findings files are wiped at session start.
173
+ - **Verification Contract (assertion ledger)** — the dispatcher owns a ledger of checkable
174
+ acceptance assertions built from the request *before* any builder runs, so a clearly stated
175
+ requirement is never silently dropped. `set_assertions` records the numbered, tagged assertions
176
+ (`test` | `runtime-ui` | `code-grep` | `manual`, one pass condition each, plus a required
177
+ `source` naming where the requirement comes from) and rebuilds the whole
178
+ ledger on a "wrong again" regression reset; `update_assertion` marks each one proven (named
179
+ evidence required), unproven, or failed after a verification gate; `get_assertions` reads the
180
+ full ledger (ids, tags, pass conditions, evidence) back. The hub persists the ledger to
181
+ `.pi/agent-sessions/assertions.json` (wiped at session start like `findings/`) and renders a
182
+ one-line status (`Assertions: 2✓ 1○ 1✗ · open: A4`) so the contract survives compaction without
183
+ re-flooding the dispatcher LLM context — after a compaction the dispatcher calls `get_assertions`
184
+ to recover the full text the status line omits. The `orchestrator` persona drives it — a deep-researcher
185
+ parity inventory for "behave like" requests, runtime proof for UI/visibility assertions, the
186
+ regression reset on a re-ask — per
187
+ [`orchestration-verification`](../../../skills/orchestration-verification/SKILL.md). The hub also
188
+ machine-parses each assertion-carrying specialist's structured return, writes the full raw output
189
+ to `.pi/agent-sessions/artifacts/returns/<agentKey>-run<N>.md`, surfaces only a compact
190
+ `details.structuredReturn` digest plus `details.returnPath`, and marks contract notices such as
191
+ missing assertion ids or evidence-less `assertions_proven` entries (demoted to unproven in the
192
+ tool text). `details.fullOutput` remains for `/af-zoom`/compatibility, but dispatcher-visible text is
193
+ digest + path oriented. `update_assertion(status: "proven")` validates evidence by assertion tag:
194
+ test evidence needs a command/test and outcome, `code-grep` needs pattern plus result sample,
195
+ manual needs user/`ask_user` confirmation, and `runtime-ui` needs an existing artifact path under
196
+ `.pi/agent-sessions/artifacts/evidence/`. **Advisory by design** (PRD open question 2): status is
197
+ surfaced and "proven" requires named evidence, but a dispatch is never hard-refused on an unproven
198
+ assertion — code-enforcement is the Checkpoint A decision. Two contract rules ARE enforced at the
199
+ tool: a batch with any sourceless assertion is refused with the offending ids named (a specialist
200
+ told to prove `A9` must be able to read its origin instead of spending a dispatch and an ASK_USER
201
+ cycle asking where `A9` was defined), and a batch over **8** open assertions is accepted with a
202
+ warning suggesting the split — declare the batch the next dispatches actually prove, and
203
+ `set_assertions` the next one when it starts.
204
+ - **Artifact bus** — session handoffs live under `.pi/agent-sessions/artifacts/` with conventional
205
+ `returns/`, `failures/`, `plans/`, `reviews/`, `inventories/`, and `evidence/` subdirectories, all
206
+ **archived** into an immutable `runs/<runId>/` namespace at session start rather than wiped (see
207
+ [Immutable per-run artifact namespaces](#immutable-per-run-artifact-namespaces-run-namespacejs)),
208
+ so a later session can never overwrite an earlier one's returns. `failures/` is separate on purpose: a run
209
+ that errored or timed out produced no specialist result, so its output goes there and the dispatch
210
+ result names it a **delivery failure** carrying no assertion evidence. Filing a 142-byte coms error
211
+ stub as `returns/code-reviewer-run4.md` once cost a 103-second dispatch investigating a review that
212
+ had in fact succeeded — only its reply was lost. `dispatch_agent` and `spawn_research` accept optional
213
+ `artifacts: string[]` paths (repo-relative or session-artifact-relative); the hub validates that
214
+ they stay inside the repo/session roots and injects only the path plus first heading/one-line
215
+ preview, never file bodies. Document-producing specialists are instructed to write plans, reviews,
216
+ inventories, and reports to the real session path
217
+ `.pi/agent-sessions/artifacts/<kind>/<agentKey>-run<N>.md` when their tools allow it, then report/pass
218
+ the artifact-relative handoff path `artifacts/<kind>/<agentKey>-run<N>.md`, finish with that path plus
219
+ a ≤10-line digest, and still include structured returns when assertions are carried. Repo-root
220
+ `./artifacts/...` files are not session artifacts. Planner's existing PLAN_FILE behavior is preserved;
221
+ the artifact path is an additional handoff channel.
222
+ - **Dispatch scope advisory** — `dispatch_agent` accepts optional `scope: string[]` for writable
223
+ builder-style runs. The orchestrator should derive these globs from the plan task's file list,
224
+ and skip scope for exploratory/reconnaissance work where the right files are not known yet. The
225
+ hub snapshots git status before the writable dispatch, diffs after the whole tool call (including
226
+ auto-research resumes), and reports out-of-scope paths in `details.scopeViolations` plus a ⚠ text
227
+ notice. This is advisory only: the hub never blocks completion, reverts files, or escalates
228
+ automatically. Known limitation: concurrent writable dispatches can only be attributed
229
+ approximately, so overlapping runs are flagged in the notice.
230
+ - **Agent controls** — `/af-zoom` inspects a live agent timeline; `/af-agents-history` replays the run as a
231
+ timeline (orchestrator turns, dispatches, research helpers) with per-agent durations, parallel-run
232
+ markers, and a grand total; kill/restart controls manage running child agents; per-agent `model:`
233
+ fields select models from team config. `/af-agents-kill <name|rN|all>` SIGTERMs a specialist (keeping
234
+ its standing card) or kills a currently running research helper (`all` clears every live helper).
235
+ `/af-agents-restart <name>` re-runs a specialist's last task fresh; research helpers cannot be
236
+ restarted. `/af-zoom <name|rN>` opens a running helper through the Fleet data model. Research spawning
237
+ and follow-up reconnaissance are automated through `spawn_research` and `NEEDS_RESEARCH:`; there are
238
+ no dedicated research lifecycle slash commands.
239
+ Restartable team specialists at or above 70% context render
240
+ their context percentage with a warning marker/color in dashboard and compact views, and their next
241
+ `dispatch_agent` result adds a `/af-agents-restart <persona>` hint. Research helpers are not warned,
242
+ and the hub never restarts specialists automatically.
243
+ - **Model switching** — a persona's frontmatter `models:` list declares the models it may switch to
244
+ (the default `model:` is implicitly a candidate). `/af-agent-model <persona>` picks from that list;
245
+ the choice lasts for the session and takes effect on the persona's next dispatch
246
+ (`/af-agents-restart <persona>` applies it immediately). The dot form
247
+ `/af-agent-model <persona>.<role>` switches a delegate sub-role's model instead — its candidates are
248
+ the role's declared default plus the parent persona's own candidate list; the switch is applied
249
+ when the parent is next dispatched (it lands in the serialized delegate config, so nested
250
+ children inherit it). `/af-models [profile]` applies a named profile
251
+ from `.pi/agents/model-profiles.yaml` — a macro over the same declared candidates, validated at
252
+ session start (a profile with any entry outside a persona's candidates is dropped whole, with an
253
+ error). This is the legacy flat format. Version 2 profiles also set all child roles, thinking,
254
+ dispatcher, watchdog/extraction, poll/debate and routing from one selection; they declare their
255
+ own models without project candidate overrides. See [complete model profiles](../../../docs/agent-fleet-setup.md#complete-model-profiles). Those
256
+ declared-candidate commands stay within their lists; Fleet Detail and the session-wide
257
+ substitution target picker intentionally use Pi's currently available registry. When an effective project or session override
258
+ fails with a model/provider error or aborted request before work begins (including local-model
259
+ memory-limit failures), the hub retries once with the model originally declared in the persona
260
+ frontmatter. For **write-capable** runs this is pre-work only: no fallback occurs after text
261
+ output, a tool call, cancellation, timeout, drift stop, or a Pi process-spawn failure, avoiding
262
+ duplicate writes. **Read-only children and research helpers** (tools limited to
263
+ `read,grep,find,ls`) also retry once when the provider fails *mid-run* — re-running a reader
264
+ repeats nothing, and those are exactly the children that exist to protect their parent's context,
265
+ so losing one to a local-endpoint OOM halfway through discards work for no safety gain. A
266
+ terminated run (watchdog, deadline, cancellation) never retries either way: that is a verdict on
267
+ the work, not a provider outage. The failed attempt is removed from the child session before retry. Per project,
268
+ `model.<persona>:` / `models.<persona>:` keys under `## agent-hub` in
269
+ `.ai/agent-fleet-overrides.md` replace a persona's default model / candidate list.
270
+ Research personas (`researcher` / `deep-researcher`, `kind: research`) are switchable the same
271
+ way — `/af-agent-model <persona>` and `/af-agent-model-thinking <persona>` accept them alongside team
272
+ members. Since research helpers are spawned fresh through `spawn_research`, the switch lands on
273
+ their next spawn (there is no running instance to `/af-agents-restart`).
274
+ `/af-agent-models-substitute [<source> <target>]` saves a runtime source → target mapping for
275
+ the current session. With no arguments it opens the same two-step visual picker as `m` in Fleet
276
+ Dashboard: first choose a source from every model configured across persona defaults, candidates,
277
+ fallbacks, and delegate sub-roles; then choose a target from Pi's currently available models. The
278
+ two-argument form performs the same operation directly. The mapping is resolved when work is
279
+ spawned rather than eagerly copied into today's roster, so team members, research personas, and
280
+ delegate sub-roles activated or created later in the session inherit it automatically. Existing
281
+ runs are not interrupted, and all mappings reset at the next `session_start`.
282
+ - **Thinking levels** — each persona's frontmatter `thinking:` sets its pi `--thinking`
283
+ reasoning effort (`off` · `minimal` · `low` · `medium` · `high` · `xhigh`). `/af-agent-model-thinking
284
+ <persona>` switches it among those six levels for the session; like a model switch it takes effect
285
+ on the persona's next dispatch (`/af-agents-restart <persona>` applies it now), and selecting the
286
+ frontmatter default clears the override. The level shows as a short badge after the model
287
+ everywhere a model is rendered — `gpt-5.5 (xh)` in the dashboard cards and the compact below-editor
288
+ view (`min`/`low`/`med`/`hi`/`xh`; `off` shows no badge). Per project, a `thinking.<persona>:` key
289
+ under `## agent-hub` in `.ai/agent-fleet-overrides.md` replaces a persona's default level.
290
+ - **Mid-turn delegation (`delegate` tool)** — a persona that declares a `subagents:` map in its
291
+ frontmatter (`role: { model, tools? }` entries, or an indented `model:`/`tools:` block per role)
292
+ gets a real mid-turn `delegate(role, instruction, context?, allow_write?)` tool, injected as an
293
+ extra `-e delegate.ts` extension into its spawned process (the `delegate` tool name is appended to
294
+ its `--tools` allowlist — pi filters extension tools too). Only declared roles are spawnable, on
295
+ their declared models — model choice is configuration, never the child LLM's. Budgets are readable
296
+ refusals: at most 4 delegate children per dispatch, tree-wide, and a per-persona `delegate_depth:`
297
+ budget capped at 1 (the default). Children spawned with remaining depth 0 do not receive the
298
+ `delegate` extension/tool. Write safety: children run read-only (`read,grep,find,ls`) unless a
299
+ SINGLE live child gets `allow_write: true`, which inherits the parent's tools intersected with the
300
+ role's `tools:` cap; if a declared role cap leaves no available tools, delegation is refused.
301
+ Concurrent children are always forced read-only. Children stream timeline events through
302
+ `.pi/agent-sessions/delegations/<persona>/events.jsonl`; the hub tails it and renders nested rows
303
+ under the parent's card (child id, model, tokens, status),
304
+ each openable with `/af-zoom <child-id>`. Each child also writes its full final output to
305
+ `.pi/agent-sessions/delegations/<persona>/results/<childId>.md`; the parent receives only status,
306
+ a required final `DIGEST:` section (≤30 lines with path:line citations), and the result-file path.
307
+ If a child omits `DIGEST:`, the parent gets the first ~30 lines plus a no-DIGEST warning and the
308
+ result path. Spend rolls up: every child row and the parent's subtree
309
+ total show tokens, and a session-wide `Δ delegated` counter sits in the status line.
310
+ `/af-agents-kill` on the parent SIGTERMs its whole process group, so the delegation tree dies with
311
+ it. `context: fork` is accepted but treated as a summary brief in v1. Per project,
312
+ `subagents.<persona>.<role>:` and `delegate-depth.<persona>:` keys under `## agent-hub` in
313
+ `.ai/agent-fleet-overrides.md` replace individual sub-roles / the depth budget. An overridden
314
+ role retains its frontmatter model as a one-shot fallback under the same pre-work-only safety
315
+ rule; delegate cards and results show the model that ultimately ran. Six personas ship with
316
+ declared sub-roles, on a three-tier OpenAI model ladder — `gpt-5.3-codex-spark` for
317
+ recon/grep sweeps, `gpt-5.4` for analysis sweeps, the `gpt-5.5` (or opus) parent reserved for
318
+ synthesis and verdicts:
319
+ - `code-reviewer` — `preflight`+`docs` (spark), `quality`+`perf` (gpt-5.4); its first delegate
320
+ call is always `preflight`, which studies the project rules and the files under review and
321
+ returns a summary that drives the rest of the fan-out. Deep security review is not a
322
+ sub-role — it belongs to the separate `security-auditor` persona, which the reviewer
323
+ recommends dispatching when it spots deeper risk.
324
+ - `planner` — `scout`+`rules` (spark) fan out before the plan is drafted; `risk` (gpt-5.4)
325
+ optionally challenges the draft breakdown.
326
+ - `plan-reviewer` — `feasibility` (gpt-5.4) checks plan claims against the actual codebase;
327
+ `deps` (spark) verifies dependency ordering and file overlap. No preflight — the plan is
328
+ the map.
329
+ - `security-auditor` — solo `recon` (spark) maps the attack surface first, then
330
+ `input-sweep` (gpt-5.4) and `secrets-sweep` (spark) fan out; exploit reasoning stays with
331
+ the parent.
332
+ - `builder` — `recon` (spark) maps call sites before edits; `verifier` (spark, the one
333
+ `allow_write: true` child) runs the test suite after them. Implementation is never
334
+ delegated.
335
+ - `test-engineer` — `coverage-scout`+`conventions` (spark) inventory gaps and test patterns;
336
+ test writing is never delegated.
337
+ - **Default damage-control guardrails** — `just fleet` and `just fleet --no-coms` load the
338
+ `damage-control-continue` harness before `agent-hub`, so dispatcher tool calls are checked against
339
+ `.pi/damage-control-rules.yaml` and a blocked call feeds back instead of aborting the turn. A
340
+ guardrail is also re-loaded into every native specialist, research helper, and nested delegate
341
+ (see [Safety scope](#safety-scope)). Missing safety plumbing refuses child dispatch.
342
+ - **Embedded coms** — the dispatcher is a discoverable peer on the local machine. Multiple
343
+ `agent-hub` (or plain `coms`) sessions on the same box find each other through per-project registry
344
+ files and exchange messages over a unix socket (named pipe on Windows).
345
+
346
+ `/af-zoom <name|rN|child-id>` opens the selected agent's full-screen stream detail. For fleet rows,
347
+ it uses the [Fleet Dashboard detail controls](#fleet-dashboard-and-detail); a directly addressed
348
+ fallback stream keeps the legacy zoom controls. Both overlays size to the terminal.
349
+
350
+ ### `/af-agents-history`
351
+
352
+ `/af-agents-history` opens a read-only overlay (same chrome as `/af-zoom`) that replays the session as an
353
+ execution **tree**:
354
+
355
+ - **Orchestrator turns** — each dispatcher turn that actually dispatched something is a depth-0 row
356
+ labelled `(dispatcher)`. Chat-only turns add no rows.
357
+ - **Dispatched specialists and research helpers** nest one level beneath the turn that launched them;
358
+ **delegate sub-sub-agents** nest one level deeper still under the specialist that spawned them — in
359
+ start order at every level.
360
+ - **Parallel runs** — siblings whose run times overlap are marked with a `│→` connector, so a
361
+ concurrent fan-out reads as a visually grouped block.
362
+ - **Real-work durations** — each row shows that node's *own* work: its span **minus the time it spent
363
+ awaiting children**. A dispatcher blocked on six concurrent agents is credited only for the time it
364
+ actually worked between/around the awaits, never for the await itself — so the same wall-clock isn't
365
+ counted twice up the tree. The same subtraction applies to a specialist awaiting its own delegate
366
+ children. Format: plain seconds under a minute (`42sec`), `m:ss` above it (`10:20min` for 620s).
367
+ Running rows tick live (the overlay re-renders once a second) and a new dispatch appears the instant
368
+ it starts.
369
+ - **Footer** shows `Σ real work <total> · <n> runs (agents <a> + dispatchers <d>)` — the real work of
370
+ *everyone*: the dispatched specialists' and research helpers' full runtime (`agents`) plus each
371
+ dispatcher turn's own work (`dispatchers` — its span minus the time it awaited agents **and** the
372
+ human via `ask_user`). Wall-clock is deliberately **not** shown: it would fold in the idle gaps
373
+ while you're away between turns, and `ask_user` waits are subtracted for the same reason.
374
+
375
+ Navigate with `↑/↓`, press `G` to jump back to the live tail, and `Q`/`Esc` to close. The log resets
376
+ on each session start.
377
+
378
+ The agent view starts with the **compact widget** enabled: one line per *running* specialist —
379
+ `name · context% · state` — *below* the input box, just above pi's status bar. Idle and done agents
380
+ and all research helpers are hidden here (running helpers live in the Fleet Dashboard), and the coms
381
+ pool widget collapses too, so an idle session collapses to just the prompt and footer.
382
+ **`Alt+Shift+A`** toggles that widget on or off; the footer reports
383
+ `Alt+A fleet · Alt+M Operator · Alt+Shift+A widget:compact|off`.
384
+
385
+ ### Work Mode picker
386
+
387
+ Press **`Alt+M`** or run **`/af-work-mode`** to open the work mode picker:
388
+ **operator** (direct tools) or **orchestrator** (delegate-only). Arrow keys move, Enter applies,
389
+ and Esc cancels with no change. Orchestrator requires a native roster. On macOS, the outer
390
+ terminal must send Option as Meta or Alt+M will not reach the Hub.
391
+
392
+ ### Fleet Dashboard and detail
393
+
394
+ Press **`Alt+A`** or run **`/af-agents-list`** to open the full-screen **Fleet Dashboard**. It is a
395
+ separate, live overlay—not an alternate compact-widget mode—and lists specialists, nested delegates,
396
+ running research helpers, and coms peers. It shows status, hierarchy, model, context/tokens, elapsed time,
397
+ tool count, and recent work; its summary counts running/done/failed rows, overlap-aware wall time,
398
+ and visible token totals. Finished/idle/stale rows are hidden by default.
399
+
400
+ - **`↑`/`↓`** or **`j`/`k`** selects a row; **`PgUp`/`PgDn`** pages; **Enter** opens its full-screen
401
+ detail view.
402
+ - **`f`** starts a name/model/recent-work filter; type the query and press **Enter** to apply it, or
403
+ **Esc** to clear it. **`a`** toggles finished rows.
404
+ - **`x`** requests a kill and **`r`** requests a restart; press the same key again within two seconds
405
+ to confirm. Kill acts on a local running specialist, a coms-backed specialist, or a research helper.
406
+ Confirmed restart terminates a running specialist when necessary, clears its session, and re-dispatches
407
+ its previous task fresh; it is refused for peer/delegate/research rows and rows with no previous task.
408
+ If a research detail view is already open when that helper finishes, it stays as a read-only terminal
409
+ snapshot until Esc; returning to the dashboard shows no completed research row.
410
+ - **`q`** or **Esc** closes the dashboard.
411
+
412
+ The detail view streams the selected local agent's assistant text, provider-emitted thinking, tool
413
+ arguments, and tool results (including success/error and duration). Normal events request an immediate
414
+ render; a 2-second ticker recovers missed file notifications and advances elapsed time. Use **`v`** to
415
+ switch between scan-friendly **Compact** rows and wrapped **Verbose** output. The choice is preserved
416
+ while drilling into other rows in the same open dashboard.
417
+
418
+ Use **`↑`/`↓`**, **`PgUp`/`PgDn`**, and **Home**/**End** to navigate. Manual movement pauses tail-follow;
419
+ **End** restores it. **Enter** expands a selected tool row in Compact mode and **Ctrl+C** copies the
420
+ selected entry. **`m`** replaces the log area with a full-screen picker containing every model currently
421
+ reported by Pi's available-model registry. Use **`↑`/`↓`**, **`PgUp`/`PgDn`**, or **Home**/**End**, then
422
+ **Enter** to apply; **Esc** cancels back to the logs.
423
+
424
+ Each local run also writes an append-only transcript under `.pi/agent-sessions/transcripts/`. The
425
+ directory/file permissions are owner-only (0700/0600 where the platform supports them), large events
426
+ are chunked, and the live in-memory window is bounded. Common authorization headers, API keys, access
427
+ tokens, passwords, provider tokens, and private-key blocks become `[REDACTED]` **before both persistence
428
+ and display**. This is pattern-based protection, so operators should still avoid deliberately printing
429
+ unknown secret formats.
430
+
431
+ “Thinking” means only text explicitly emitted by the provider/runtime; hidden model reasoning is not
432
+ available, and personas with thinking disabled have no thinking rows. Model switching works for local
433
+ specialists, a currently running research helper, and nested delegate roles. It applies on the next dispatch or
434
+ continuation and never interrupts a running child. A coms-backed specialist stores the choice for native
435
+ fallback runs; external coms peers control their own model, have no picker, and have no local transcript.
436
+ **Esc**/**`q`** returns to the dashboard. **`/af-zoom <name|rN>`** opens this same detail view directly.
437
+
438
+ ### Version footer
439
+
440
+ `agent-hub` renders its local harness version first in its custom footer:
441
+ `agent fleet v<version> · <model><thinking> · <team>`. It replaces pi's default footer, so it does **not**
442
+ consume or render the shared version status; it reads its own adjacent stamped manifest directly.
443
+ The three persistent-UI harnesses (`agent-hub`, `coms`, and
444
+ `damage-control-continue`) still register that one shared key, which gives default footers one
445
+ version in stacked non-hub sessions. In the supported guardrail-plus-hub stack, the hub's custom
446
+ footer supplies the single visible version. Damage-Control can update its own safety status after
447
+ a violation without overwriting the shared version entry. The canonical source is the
448
+ repository-root `package.json`; the adjacent harness manifest is a synchronized stamp maintained
449
+ by `bin/sync-harness-versions.js`. Its local `version.ts` reader intentionally stays with the
450
+ harness for copied or symlinked installs, but those installs still need the pre-existing full
451
+ `.pi/harnesses/` dependency installation.
452
+
453
+ The `agent fleet` half of the label is an OSC 8 terminal hyperlink to the project homepage —
454
+ clickable in terminals that support hyperlinks, ignored (rendered as plain text) elsewhere, and
455
+ free of footer columns because pi strips OSC sequences before measuring width. It opens the
456
+ repository in a browser, not a TUI panel: pi has no mouse tracking, so a click never reaches the
457
+ harness. `AGENT_FLEET_NO_LINKS=1` restores the plain label on multiplexers that mangle OSC 8
458
+ (GNU screen, tmux before 3.4).
459
+
460
+ ### Voice dictation indicator
461
+
462
+ The custom footer renders the optional [`pi-voice-stt`](../../extensions/pi-voice-stt/README.md)
463
+ extension's recording indicator on a line **below the model line** — e.g.
464
+ `● REC 0:01 ⏎ send · esc cancel` while recording, or a `transcribing…` dot. Because agent-hub
465
+ replaces pi's built-in footer (where that indicator normally lives), it reads the extension's
466
+ `setStatus("voice-stt", …)` value via the footer data provider and surfaces it itself. The
467
+ indicator only appears once `pi-voice-stt` is installed and configured; otherwise the footer is
468
+ the single model line. Press **`Alt+S`** to start/stop dictation as in a normal pi session.
469
+
470
+ ### Compact-view agent switcher
471
+
472
+ With the **compact widget enabled**, the running-specialists list below the input doubles as a
473
+ switcher. **`Alt+]`** and **`Alt+[`** move a marker (`›` + highlight) to the next/previous running
474
+ specialist; **`Alt+\`** opens the full-screen detail view on the marked one (`q`/`Esc` to return).
475
+ This only changes what you *view* — **the input box always prompts the main session**, and `main` is
476
+ never a marker target (it is the session under the input, not a subagent). There is no transcript
477
+ takeover: a subagent stream is shown in an overlay, never by replacing the main scrollback. These
478
+ keys require the compact widget; use `/af-zoom <name>` or the Fleet Dashboard otherwise.
479
+
480
+ > Terminal note: `Alt+[` emits `ESC [` (a CSI prefix) and may be swallowed by some terminals'
481
+ > escape parsers; `Alt+]` and `Alt+\` are the reliable pair. `Alt+↑/↓/←/→` are reserved by the pi
482
+ > editor, which is why the switcher uses the bracket/backslash keys.
483
+ >
484
+ > On macOS, configure the outer terminal to send Option as Meta. For Zed, set
485
+ > `terminal.option_as_meta` to `true`; otherwise Option combinations produce composed characters.
486
+
487
+ ## Configuration
488
+
489
+ At session start, `agent-hub` reads `.ai/agent-fleet-overrides.md` in the workspace. The
490
+ canonical section name is `## agent-hub` (the legacy `## agent-team` name is still accepted):
491
+
492
+ ```markdown
493
+ ## agent-hub
494
+ # Replace Bulgarian with any language name.
495
+ language: Bulgarian
496
+ ```
497
+
498
+ Omit the section to keep the default `English`. `language` applies to dispatcher replies,
499
+ `ask_user` questions and `context` fields, handoff summaries, and user-facing status text;
500
+ specialist task strings stay in English.
501
+
502
+ The same section can point the team at the project's own rule files and documentation
503
+ entry points:
504
+
505
+ ```markdown
506
+ ## agent-hub
507
+ rules: docs/rules, .ai/rules
508
+ docs: Docs/AGENTS.md, Docs/architecture/ARCHITECTURE_OVERVIEW.md
509
+ ```
510
+
511
+ `rules:` lists repo-relative folders of HOW rules — implementation patterns the work must
512
+ comply with. Resolution is **index-first**: a folder with a top-level `README.md`/`index.md`
513
+ is treated as curated — personas read the index first and follow its loading manifest
514
+ (session bundles, conditional-load lists) instead of bulk-reading the tree; a folder without
515
+ an index is searched **recursively** through all subfolders. When set, every dispatched
516
+ specialist's system prompt gains a "Project rules" block naming the folders and the
517
+ resolution order; the planner and code-reviewer personas additionally validate their subject
518
+ against the relevant rules and pass them on (cited in plan acceptance criteria / handed to
519
+ delegate sub-reviewers).
520
+
521
+ `docs:` lists repo-relative WHAT/WHY documentation entry points — canonical files (e.g. an
522
+ `AGENTS.md`, an architecture overview) or doc folders (personas start from the folder's
523
+ README/index). Docs orient rather than bind: every dispatched specialist **and every research
524
+ helper** gains a "Project docs" block telling it to read the entry points relevant to its
525
+ task and follow their links instead of bulk-reading doc trees. The code-reviewer flags
526
+ changes that alter documented behavior without a doc update; the documenter treats the entry
527
+ points and the trees they link as the documentation it maintains.
528
+
529
+ `research-keep:` is **removed**. An existing key warns at session start and has no effect; delete it.
530
+ Live research helpers disappear from the Fleet Dashboard when they finish. Session/transcript/findings
531
+ files and `/af-agents-history` records remain.
532
+
533
+ ### Bounded local-disk searches
534
+
535
+ Every `read`, `grep`, `find`, and `ls` call made by a native research helper or a nested
536
+ `delegate` child has a **parent-side** watchdog. The default is **120 seconds per tool call**;
537
+ it is a per-tool bound, not a whole-run deadline — the whole-run bound is the execution
538
+ mode's per-run deadline below. Configure it in the repository-standard overrides file:
539
+
540
+ ```markdown
541
+ ## agent-hub
542
+ recon-search-timeout-s: 120 # integer 1..3600
543
+ # recon-search-timeout-s: off # disable this per-tool watchdog
544
+ ```
545
+
546
+ Invalid values warn at session start and use 120. Calls are tracked independently by their
547
+ JSONL `toolCallId`; a repeated start/update cannot extend an existing deadline. A timeout returns
548
+ `tool_timeout` with the call metadata, ends the research/delegate lifecycle, sends SIGTERM to the
549
+ child's explicitly owned process group, then SIGKILL after a finite grace period. The parent also
550
+ has a final settlement timer, so it settles rather than waiting indefinitely for `close` or
551
+ inherited pipe drain. If child/process-group death cannot be confirmed after this bounded cleanup,
552
+ the timeout metadata reports `terminationConfirmed: false`: this prevents the parent hanging, but
553
+ may indicate an uninterruptible OS-level process that needs operator attention. This group
554
+ ownership covers descendants even when the pi leader exits first; nested delegates own their groups
555
+ and forward parent cancellation, avoiding detached-orphan processes. Caller
556
+ cancellation follows the same bounded cleanup path but is reported as `cancelled`, not
557
+ `tool_timeout`.
558
+
559
+ ### Task-tier budgets
560
+
561
+ The hub runs **per-user-turn budgets enforced in code**, not prose, keyed off the current
562
+ **task tier**. This is the guardrail against runaway orchestration (the observed failure
563
+ mode: 100+ dispatches and 100M+ tokens for one task, most of it re-billed stale specialist
564
+ context).
565
+
566
+ | Budget (per user turn) | trivial | small | feature | project |
567
+ |-----------------------------------|---------|-------|---------|---------|
568
+ | `dispatch_agent` calls | 1 | 2 | 8 | 12 |
569
+ | `spawn_research` calls | 1 | 2 | 4 | 6 |
570
+ | Turn wall clock | 15 min | 15 min| 60 min | 90 min |
571
+ | Per-run deadline (specialist/research/delegate) | 10 min | 10 min | 30 min | 30 min |
572
+ | Specialist session recycled after | 3 runs | 3 runs| 5 runs | 5 runs |
573
+ | Nested delegation | off | off | on | on |
574
+
575
+ When a budget is exhausted, `dispatch_agent`/`spawn_research` **refuse** with instructions
576
+ to summarize and ask one localized Yes/No `ask_user` question. **Yes** renews the turn budget
577
+ inside the same tool loop; the user does not type `continue` or run a slash command. A normal
578
+ new user message still opens a fresh turn window. Time blocked in any `ask_user` question is
579
+ excluded from the turn wall clock, so a slow human answer cannot exhaust the next dispatch.
580
+ Raise the task with `set_task_tier` when the work outgrew the current envelope. Override keys
581
+ in `.ai/agent-fleet-overrides.md` are a **ceiling** (`min` with the tier); `off` stays at the
582
+ tier rather than lifting the cap. A leftover `mode:` key is ignored with a warning.
583
+
584
+ ```markdown
585
+ ## agent-hub
586
+ max-dispatches-per-turn: 8 # integer ceiling, or off (stays at the tier)
587
+ max-research-per-turn: 4 # integer ceiling, or off (stays at the tier)
588
+ turn-wall-time-s: 3600 # integer ceiling, or off (stays at the tier)
589
+ agent-turn-timeout-s: 1800 # whole-run deadline per spawned run; integer or off
590
+ session-recycle-runs: 5 # recycle a specialist session after N resumed runs; integer or off
591
+ run-history-keep: 10 # previous sessions' artifact archives to retain; integer or off
592
+ ```
593
+
594
+ #### Task budget (the bound a turn window cannot provide)
595
+
596
+ A per-message allowance cannot bound a task. In the run this guardrail comes from, every
597
+ steering message opened a fresh window of 8 dispatches and 60 minutes, so no counter ever
598
+ bound: one workspace stayed open **47 hours**, while the same change made in a narrow
599
+ workspace took **13 minutes**.
600
+
601
+ So there is a second envelope, **`TASK_BUDGET_MULTIPLIER` (3) × the turn envelope**, whose
602
+ counters are **not** reset by a user message:
603
+
604
+ | | per turn (`feature`) | per task |
605
+ |---|---|---|
606
+ | `dispatch_agent` | 8 | 24 |
607
+ | `spawn_research` | 4 | 12 |
608
+ | clock | 60 min wall | 180 min **active** |
609
+
610
+ Exhausting it is a **hard stop**: the refusal says so, and another user message does not
611
+ reopen it. The hub asks one localized Yes/No `ask_user` question. **Yes** opens one audited
612
+ continuation tranche and resumes directly; it resets the task dispatch/research counters,
613
+ active-time clock, review allowance, and the current turn budget while preserving the task
614
+ tier, assertion ledger, capability packs, label, blockers, and accumulated progress. **No**
615
+ (or cancellation) stops. Each accepted tranche appends `agent-hub-budget-continuation` with
616
+ bounded prior usage and allowlisted process/session/pane identity.
617
+
618
+ `set_task_tier` with `new_task: true` remains the lifecycle action for genuinely different work.
619
+ It clears task identity/state as well as counters and appends an `agent-hub-task-reset` audit
620
+ entry. Do not use it merely to continue the same task. The status chip still shows both turn and
621
+ task usage (`… · task 4/18`).
622
+
623
+ The reasoning: three full envelopes still require an explicit human decision, but that decision
624
+ is now a single confirmation rather than a fake new task followed by a second message.
625
+
626
+ Both turn and task clocks charge **active time only** — turns that actually ran, minus the
627
+ time the dispatcher sat blocked on `ask_user`. Inter-turn idle costs nothing, because no turn
628
+ is open across it. Raw wall clock would bill a lunch break, an overnight pause, and every long
629
+ human answer against the task; at `fast` mode's 45-minute envelope a coffee break would
630
+ hard-stop a task with two dispatches spent. A false stop is worse than no stop — it teaches
631
+ people to reset the task window reflexively, and that reset is the one thing that has to
632
+ stay deliberate. Dispatch and research counts remain the honest hard stops.
633
+
634
+ The **auto-research pipe** (specialist emits `NEEDS_RESEARCH`, the hub fans out read-only
635
+ helpers in code) stays exempt from the TURN budget — it is hub mechanics, not a dispatcher
636
+ decision, and it must not steal the dispatcher's slots — but it **is** charged against the
637
+ task envelope. At 2 rounds × 4 questions per dispatch and 18 dispatches per task, leaving it
638
+ uncounted would have put 144 research runs inside the bound that is supposed to be the outer
639
+ one. When the task's research envelope is spent the pipe does not spawn and the specialist is
640
+ not resumed; the dispatch result says so.
641
+
642
+ Two related always-on behaviors: specialist **context pressure is measured over
643
+ input + cacheRead + cacheWrite** (resumed sessions re-send their whole accumulated context
644
+ as cache reads — counting `input` alone hid that entirely), and a specialist session is
645
+ **recycled** (fresh session, no `-c` resume) once it has served `session-recycle-runs` runs
646
+ or its measured context passes 60%. The dispatch result notes the recycle so the dispatcher
647
+ knows the specialist starts without session memory — task text and `artifacts:` paths must
648
+ carry the state, which the deliverable-to-file protocol already ensures.
649
+
650
+ Context is measured against **that agent's own** model window, resolved from pi's model
651
+ registry (`ctx.modelRegistry.find`) with the source recorded on every resolution. Dividing a
652
+ 49k local model's usage by the dispatcher's window is what produced unactionable readings
653
+ like `⚠ Planner context at 315%`; a reading above 100% now emits a one-time diagnostic that
654
+ names the window and where the number came from, so a mis-resolved window is distinguishable
655
+ from a genuine overflow. Two recycle rules follow from it: a session at or past a **full**
656
+ window is recycled unconditionally (no threshold override keeps it alive), and a resumed
657
+ session whose *projected* prompt — prior tokens plus this task — would overflow is recycled
658
+ **before** the spawn instead of after the run.
659
+
660
+ #### Per-provider concurrency
661
+
662
+ A dispatch may fan out to four delegate children at once and several specialists can be
663
+ mid-run, with nothing bounding how many requests land on one provider. That is fine against
664
+ a hosted endpoint and not against a local one. Requests are capped per process — **2 in
665
+ flight for `custom/*` and `omlx/*` by default, unlimited elsewhere**:
666
+
667
+ ```bash
668
+ AGENT_HUB_PROVIDER_LIMITS="custom=4" # raise the local cap
669
+ AGENT_HUB_PROVIDER_LIMITS="custom=off" # disable it
670
+ AGENT_HUB_PROVIDER_LIMITS="custom=2,ollama=1"
671
+ ```
672
+
673
+ Queued runs still execute — they wait for a permit, and the wait is announced rather than
674
+ looking like a hang. The cap applies per **level** of the delegation tree (each pi process
675
+ runs its own semaphore over the children it spawns), and a nested spawn reuses its parent's
676
+ permit, so a child can never wait on its own ancestor. The drift judge and the return
677
+ extractor are deliberately ungated: both run while a specialist holds a permit, so queueing
678
+ them behind it would stall the watchdog meant to stop it.
679
+
680
+ The per-run deadline lands as `turn_timeout` (exit 124) with partial output preserved, for
681
+ dispatched specialists, research helpers, and nested delegate children alike — a hung child
682
+ can no longer hold its parent for hours.
683
+
684
+ ### Task triage (complexity tiers)
685
+
686
+ The dispatcher classifies the current TASK with the `set_task_tier` tool BEFORE its first
687
+ dispatch — `trivial` / `small` / `feature` / `project` — and that classification *is* the
688
+ budget envelope (see the table above). The tier shows in the `hub-tier` status chip
689
+ (`Tier: small · …`), with a trailing `?` while it is only assumed.
690
+
691
+ Skipping the call makes the hub assume **`small`**, not `feature`. Because the tier is
692
+ task-scoped, a skipped triage latches for the whole task — and skipped triage is precisely
693
+ the case where the dispatcher was not thinking about proportionality. Assuming `feature`
694
+ there would unlock planner/plan-reviewer/security-auditor, loosen the review caps, and hand
695
+ out the full feature envelope: the over-apparatus failure mode, granted by forgetting a tool
696
+ call. Assuming `small` costs one explicit escalation when the work really is bigger, which
697
+ is the cheap direction to be wrong in. An assumed tier is not a ratchet baseline either: the
698
+ dispatcher's own first `set_task_tier` is treated as an initial declaration, so it never
699
+ needs a `reason` it had no way to know it needed.
700
+
701
+ The tier is **task-scoped and ratcheted**. It survives the user's next message, and it
702
+ moves in one direction cheaply: **lowering it is always free, raising it requires a
703
+ `reason`** naming what the ask turned out to contain (refused in code otherwise). A
704
+ turn-scoped tier could not bind on a steered run — every correction reset it to null, the
705
+ next dispatch re-assumed `feature`, and the effective tier drifted to the ceiling, because
706
+ nobody ever re-declares `trivial` after a steering message.
707
+
708
+ Three guards are enforced in code, not prose:
709
+
710
+ - **Duplicate-dispatch guard** — refuses re-dispatching the same agent with a
711
+ near-identical task inside one turn.
712
+ - **Tier persona gate** — at `trivial`/`small`, `dispatch_agent`/`spawn_research` refuse
713
+ `planner`, `plan-reviewer`, `architect`, `security-auditor` and `deep-researcher`
714
+ (`run-budget.js`). Each opens a document/finding loop whose output then has to be
715
+ executed and re-reviewed; the escape hatch is raising the tier *with a reason*, not a
716
+ flag. The refusal costs no budget slot.
717
+ - **Review round cap** — review dispatches per TASK are capped by tier (trivial/small 1,
718
+ feature 2, project uncapped) and the (N+1)-th is refused without spending a budget slot.
719
+ This is where the review ratchet is actually cut: findings become requirements and the
720
+ enlarged requirement set justifies the next round, so the round is the thing to bound.
721
+ - **Review finding budget** — a review persona's dispatch carries a blocking-finding cap
722
+ tied to the tier (trivial 1, small 2, feature 5, project uncapped) plus the rule that a
723
+ blocking finding may only enforce an invariant the task/plan/rules already state. The hub
724
+ **counts** what came back (`review-findings.js`) and appends a visible notice when the
725
+ return exceeds the cap — it never reclassifies a finding. No rule the hub can evaluate
726
+ distinguishes "invents a manifest nobody asked for" from "this logs a connection string";
727
+ both are a heading and a bullet, and silently demoting the second by position would, on
728
+ the day it matters, move a real security finding into the section nobody acts on.
729
+
730
+ Every budget/gate refusal is counted in `/af-hub-report`.
731
+
732
+ ### Docs lane (`docs-lane.js`)
733
+
734
+ A dispatch whose declared `scope` is documentation only — `Docs/**`, `**/*.md`,
735
+ `artifacts/evidence/*.png`, `.changeset/**` — runs in the single-worker docs lane:
736
+
737
+ - dispatching a review persona (`code-reviewer`, `plan-reviewer`, `security-auditor`,
738
+ `test-engineer`) on it is **refused** and costs no budget slot;
739
+ - any other persona's result carries a note telling the dispatcher not to open a review
740
+ gate for it.
741
+
742
+ An absent or empty `scope` is never the lighter lane — unknown is not docs. The refusal is
743
+ overridable per dispatch with `review_reason: "<why>"` for the cases that do warrant a gate
744
+ (the doc publishes a credential, or states a contract other systems depend on).
745
+
746
+ ### External-blocker stop (`external-blocker.js`)
747
+
748
+ A specialist that cannot proceed without something outside the fleet's reach — an account,
749
+ a permission, a deployment credential, a telemetry destination, a console-only action —
750
+ emits `EXTERNAL_BLOCKED: <what is missing, who owns it, what it blocks>` (the protocol is
751
+ injected into every specialist prompt). The hub records it and **refuses the next
752
+ dispatch/research** with an owner-escalation packet: what is missing and who owns it, which
753
+ assertions are blocked, what is already proven and where, and the human's options (provide
754
+ access / waive as UNPROVEN / drop from scope).
755
+
756
+ The gate opens when the human has been addressed — an `ask_user` call, or the next user
757
+ message. Without `ask_user` installed it fires exactly once, so a session that cannot reach
758
+ the human can still finish and report instead of deadlocking.
759
+
760
+ This exists because the alternative is the most expensive failure mode observed: with no
761
+ correlation destination available, a run kept substituting internal work for the missing
762
+ external fact — scripts, manifests, fixtures, diagnostic packets — for hours, and the
763
+ assertion still ended UNPROVEN.
764
+
765
+ ### Immutable per-run artifact namespaces (`run-namespace.js`)
766
+
767
+ Session start used to `rm -rf` `.pi/agent-sessions/artifacts/`, and specialist returns were
768
+ named by a per-session counter (`returns/builder-run1.md`). Both halves of that failed at
769
+ once: the next session's `builder-run1.md` claimed the same path as the previous one's, and
770
+ the wipe deleted the originals first — a post-mortem had to record eleven implementation
771
+ returns and two review artifacts as NOT RECOVERABLE.
772
+
773
+ Now each session **archives** the previous session's artifacts into
774
+ `.pi/agent-sessions/runs/<runId>/artifacts/` — a namespace written once and never reused —
775
+ alongside a read-only `meta.json` (run id, archive time, project, workspace, per-kind
776
+ artifact counts) and an appended `runs/index.json`. `runId` is a sortable UTC timestamp plus
777
+ a random suffix, so two sessions starting in the same second still get distinct namespaces.
778
+ Retention is `run-history-keep` (default 10, `off` keeps everything); an empty artifact tree
779
+ is not archived. If archiving fails the artifacts are **left in place** rather than deleted:
780
+ a stale tree is recoverable, a deleted one is not.
781
+
782
+ ### Drift watchdog (in-flight observation)
783
+
784
+ An armed dispatch is observed **while it runs**, from the same JSON event stream that
785
+ drives the cards — not post-hoc:
786
+
787
+ - **Layer 1 — deterministic rules, zero tokens** (`drift-watchdog.js`): a write/edit
788
+ outside the dispatch's declared `scope` globs, the identical tool call repeated 4×,
789
+ 5 consecutive failed tool calls, or 200 total tool calls in one run.
790
+ - **Layer 2 — LLM judge, escalation only**: when a rule fires (single-flight, 90 s
791
+ cooldown), a one-shot cheap run (default model: the researcher persona's; override with
792
+ `watchdog-judge-model`) reads the original task + declared scope + recent tool trail and
793
+ answers `VERDICT: ON_TRACK|DRIFTING|STUCK`. Judge failures fail open.
794
+ - **Intervention**: DRIFTING/STUCK terminates the run as **`drift_stop`** (exit 125,
795
+ partial output preserved) and the dispatch result instructs: re-dispatch ONCE with a
796
+ corrected, narrowed task — never the same task unchanged.
797
+
798
+ Enablement is dynamic. In **operator** work mode, precedence is the `watchdog: true|false`
799
+ param on a single `dispatch_agent` call → a per-agent override (`/af-watchdog builder
800
+ on|off|clear`) → the hub-wide setting (`/af-watchdog on|off|auto`, default `auto`, project
801
+ default via the `watchdog:` overrides key): `on`/`auto` arm and `off` disarms. In
802
+ **orchestrator** work mode, hub `auto`/`on` auto-arms; dispatch `watchdog: false` cannot
803
+ disarm it. Opt out with hub `/af-watchdog off` (or override `watchdog: off`), or a per-agent
804
+ `off`. Read-only research helpers are not monitored — they already run under the per-tool
805
+ watchdog + turn deadline and cannot write.
806
+
807
+ ### Dynamic teams
808
+
809
+ Rosters start from `.pi/agents/teams.yaml` but are not frozen there:
810
+
811
+ - `/af-agents-add <persona>…` / `/af-agents-drop <persona>…` — restructure the ACTIVE team
812
+ live (drop refuses running or last members; session files are kept for re-adding).
813
+ - `/af-agents-save <name>` — persist the current roster as a named team back into
814
+ `teams.yaml` (targeted block upsert; comments and other teams untouched).
815
+ - `team_adjust` — the dispatcher itself may add/drop a persona **with a stated reason**;
816
+ disabled at trivial/small tiers, capped at 8 roster members, and every change is notified to the
817
+ human. The system prompt is rebuilt each turn, so changes take effect immediately.
818
+
819
+ ### `/af-hub-report`
820
+
821
+ Per-turn cost accounting: dispatches (agent, status, elapsed, billed/output tokens),
822
+ research runs, session recycles, drift stops, and budget/duplicate refusals — for the
823
+ current turn, the last completed turn, and session totals. Billed tokens count
824
+ input + cacheRead + cacheWrite, the same measure the recycler uses.
825
+
826
+ Paths that don't exist produce a session-start warning, never an error. The full key list for
827
+ `## agent-hub` (models, sub-roles, depth budgets, persona gate, research retention, watchdog,
828
+ mode/budget keys) is documented in `docs/agent-fleet-setup.md`.
829
+
830
+ ## The coms layer
831
+
832
+ > The runtime coordination protocols this layer implements (sentinels, push over
833
+ > polling, barriers, fan-out digests, racing) are catalogued in
834
+ > [references/fleet-coordination-patterns.md](../../../references/fleet-coordination-patterns.md).
835
+
836
+ ### Fleet tools (herdr)
837
+
838
+ Inside a [herdr](https://herdr.dev) pane with a live server, the dispatcher's tool
839
+ surface additionally gets (absent otherwise, like coms):
840
+
841
+ - `herdr_spawn_peer` — stand up a constrained Fleet peer through the shared peer-launch resolver.
842
+ The peer joins **this session's `--project` pool** (the model cannot override it), and a name
843
+ declared in `.pi/agents/peers.yaml` keeps its declared `runner:`/`extensions:`/`env_file:`,
844
+ including `runner: claude-code`; undeclared explicit shapes may select a Pi persona, identity-only
845
+ Fleet Core peer, or Claude Code. Manifest-declared env is the only env admitted. The peer gets a
846
+ sibling pane in the current workspace/tab, not a second process in the Hub pane. A spawn by name
847
+ therefore produces the same declared agent as a preset launch. A persona peer **boots idle**
848
+ and does nothing until a `coms_send` reaches it, so the call waits (bounded, ~45s) for it to
849
+ register and returns `peer_ready` plus its coms name instead of a bare pane id; on failure it
850
+ returns the pane's last output, which means the peer did not start rather than that it is slow.
851
+ Peers spawned but never addressed are named at turn end and in `/af-hub-report` with a close
852
+ suggestion — closing stays the human's call.
853
+ Mechanism: herdr's `pane.split` takes **no command** — it opens a shell — so the spawn splits,
854
+ waits for the pane's prompt, and types the argv (text and Enter sent separately, because bash
855
+ bracketed paste would swallow a newline). Only `layout.apply` pane nodes carry an argv, which is
856
+ why declarative preset layouts were never affected by this.
857
+ - `herdr_spawn_pane` — create an arbitrary command pane when a constrained/addressable Fleet peer
858
+ is not the desired shape; raw commands are intentionally excluded from `herdr_spawn_peer`.
859
+ Orchestrators may use this for auxiliary processes such as watchers or servers, never to bypass
860
+ delegate-only implementation policy.
861
+ - `herdr_read_pane` — bounded `pane.read` (≤200 lines), read-to-decide on workers/tools;
862
+ messaging still goes through coms, and peer busy state comes from `coms_list`, not from
863
+ reading the screen
864
+ - `herdr_close_pane` — kills a pane; **asks the human to confirm every call**; the
865
+ bash-level `herdr pane close`/`workspace close`/`server stop` verbs are hard-blocked
866
+ for spawned specialists by `.pi/damage-control-rules.yaml`
867
+ - `herdr_notify` — desktop notification to reach the human when they are away
868
+
869
+ This closes the fleet loop: spawn a worker, watch it, notify the human, tear it down —
870
+ without leaving the session. Claude Code panes join the same pool via the
871
+ [coms bridge](../../../docs/claude-code-coms-bridge.md).
872
+
873
+ ### Presence backend (herdr or files)
874
+
875
+ Presence is pluggable, exactly as in the standalone [coms harness](../coms/README.md#presence-backends-herdr-vs-files):
876
+ inside a [herdr](https://herdr.dev) pane with a live server, the ping cycle is replaced by
877
+ push events (`agent.list` + `events.subscribe`) and the hub reports itself into the herdr
878
+ sidebar (`custom_status` = `<name> <pct>% q<depth>`); everywhere else the original 10s
879
+ ping loop runs unchanged. The file registry is written in both backends, and the
880
+ pool-scope boundary is enforced identically.
881
+
882
+ ### Identity
883
+
884
+ Each session registers a coms identity at start-up, resolved in this precedence order:
885
+
886
+ 1. **CLI flags** — `--name`, `--purpose`, `--project`, `--color`, `--explicit`
887
+ 2. **Defaults** — auto-generated name `hub-<id>`, purpose `agent-hub dispatcher`, project
888
+ `default`, a deterministic color derived from the session id
889
+
890
+ Names are de-duplicated per project (`resolveUniqueName`), so two hubs that both want `architect`
891
+ become `architect` and `architect-2`. `--explicit` marks a **private** peer — kept out of every
892
+ pool by default, so it is neither listed nor reachable until a human opts in with `/af-coms --all`
893
+ (see [Pool scope is the reach boundary](#pool-scope-is-the-reach-boundary)). The registry lives
894
+ under `~/.pi/coms/projects/<project>/agents/<name>.json` and is created at runtime.
895
+
896
+ ### Commands & tools (local dispatcher plus coms)
897
+
898
+ - `/af-coms` — coms control surface (peer list / status)
899
+ - `/af-handoff <peer>` — hand the whole session off to a coms peer (see [Handoff](#handoff))
900
+ - `/af-poll [--panel NAME] [--persona NAME] <question>` — ask every voice in a named model panel (from `.pi/agents/voices.yaml`) the same question. `--panel` wins; else `poll-panel:` in `## agent-hub`; else a refusal listing available panels. Counts as **one** turn-budget dispatch. The main loop gets an immediate `POLL STARTED` receipt (no dispatcher turn), then one `POLL VOICE` line per finished voice, then the digest. Full opinions stay on disk under `.pi/agent-sessions/artifacts/polls/<runId>/`.
901
+ - `/af-debate [--panel NAME] [--persona NAME] [--rounds N] <question>` — same panel, 2–5 harness-mediated rounds (default 3). Each surviving voice sees the labeled positions of the others from the previous round. There is no judge and no hidden merge. Counts as **one** turn-budget dispatch. Per-round files land under `.pi/agent-sessions/artifacts/polls/<runId>/debate/round-<n>/`.
902
+ - `/af-compound [focus]` — end-of-session **compound-learning pass**: the dispatcher composes a
903
+ candidate-lessons brief from the session (corrections, recurring findings, root causes),
904
+ confirms it with the user, then dispatches the `documenter` to land the approved lessons as
905
+ minimal diffs on the project's `rules:`/`docs:` targets per `skills/compound-learning/SKILL.md`.
906
+ Requires the `documenter` persona in the active team; run it before `/af-handoff` or session end.
907
+ - `coms_list` — discover the peers in your pool: names, models, live context usage, purpose,
908
+ `pane_id`, and `status` (`idle` | `working` | `booting`). Check status before sending: `working`
909
+ means your send waits behind the peer's current turn, `booting` means it is not addressable yet.
910
+ This is the field whose absence drove 127 `herdr_read_pane` calls in one session. Scoped
911
+ to your project and excluding private peers; the LLM cannot widen it (see
912
+ [Pool scope is the reach boundary](#pool-scope-is-the-reach-boundary)).
913
+ - `coms_send` — send a prompt to a peer **in your pool**; returns a `msg_id`
914
+ - `coms_await` — **block** until that `msg_id`'s reply lands (default 30 min,
915
+ `PI_COMS_TIMEOUT_MS`)
916
+ - `coms_get` — **non-blocking** poll of a `msg_id` (status `pending|complete|error`)
917
+
918
+ `/af-coms` and `/af-handoff` tab-complete live peer names **in your pool**.
919
+
920
+ ### Pool scope is the reach boundary
921
+
922
+ The set of peers shown in the pool widget is the security boundary: **a peer is reachable only if it
923
+ is in your pool.** `coms_list`, `coms_send`, and `/af-handoff` all resolve targets through the same
924
+ `peersInScope()` helper, so the dispatcher can never message a peer it cannot see. Two knobs define
925
+ the pool, and **both are human-only** — the LLM cannot widen scope to reach more peers:
926
+
927
+ - **Project** — defaults to your own `identity.project`. A human can retarget with `/af-coms --project
928
+ <name>` (one project) or `/af-coms --all` (every project). `coms_list`'s own parameters cannot
929
+ override this; an LLM request for a wider project is clamped back to the current pool and flagged.
930
+ - **Explicit (private) peers** — excluded from every pool by default. `/af-coms --all` opts them in.
931
+
932
+ This closes a cross-project leak where a peer reachable through the mesh was *not* shown in the
933
+ default project-scoped pool — so it could be messaged without being "connected." Now the reachable
934
+ set is always a subset of what the widget shows. To reach a peer outside the pool, a human widens
935
+ scope first; the dispatcher is told to **ask** rather than attempt it, and not to pass cross-project
936
+ context to a peer the human has not approved.
937
+
938
+ ### Peer as subagent
939
+
940
+ The dispatcher uses a peer as a subagent by pairing the tools: `coms_send(target, prompt)` to
941
+ issue the task, then `coms_await(msg_id)` to block for the reply (or `coms_get` to poll). This sits
942
+ alongside `dispatch_agent` — local persona specialists are dispatched as subprocesses; remote peers
943
+ are reached over coms. The two paths stay explicit for the LLM, but
944
+ [coms-backed dispatch](#coms-backed-dispatch-dispatch-policyyaml) can route a `dispatch_agent` call
945
+ to a same-name peer under the hood. (The specialist-level `delegate` tool is a third,
946
+ nested path: a dispatched specialist spawning its own declared sub-agents — it does not auto-route
947
+ between local and remote either.) Multi-hop is inherited from coms: a peer handling a dispatched task can `coms_send`
948
+ onward, hops accumulating up to `MAX_HOPS` (5).
949
+
950
+ ### Coms-backed dispatch (dispatch-policy.yaml)
951
+
952
+ `just fleet --agents <roster> --peers <preset>` boots the Hub next to standing peers from
953
+ `.pi/agents/peers.yaml` — and some
954
+ of them (e.g. `code-reviewer`, `plan-reviewer` with `runner: claude-code`) intentionally share a name
955
+ with a team member. `.pi/agents/dispatch-policy.yaml` tells the dispatcher to serve such members
956
+ **through the peer** instead of spawning a native subagent:
957
+
958
+ ```yaml
959
+ default: native # coms = substitute ANY member with a live same-name pool peer
960
+ grace_s: 30 # poll window for coms-required members
961
+ substitutions:
962
+ code-reviewer:
963
+ prefer: coms
964
+ fallback: native # none = coms-required: refuse with guidance instead of spawning
965
+ # timeout_s: 3600 # per-member reply timeout (default PI_COMS_TIMEOUT_MS, 30 min)
966
+ ```
967
+
968
+ Semantics:
969
+
970
+ - **One API with an explicit override.** `dispatch_agent(..., backend: "auto"|"native"|"coms")`
971
+ defaults to `auto`, which follows this policy. `native` always starts the local Pi specialist even
972
+ when a same-name peer is live. `coms` requires that live same-name peer and never falls back to
973
+ native. The whole downstream pipeline — structured return contract,
974
+ `ASK_USER:` extraction, the NEEDS_RESEARCH auto-research pipe, assertions, history, the grid —
975
+ consumes a coms reply exactly like a subagent's final output (the dispatch protocols ride in the
976
+ message body, since a standing peer only receives a user prompt).
977
+ - **Decided per dispatch, against the live pool.** Hub and peers boot in parallel, so the first
978
+ dispatch may land before the peer registers: with `fallback: native` it runs natively (one notice
979
+ per member per team activation), and later dispatches pick up the peer once it is live. With
980
+ `fallback: none` the dispatch polls the pool for `grace_s` seconds, then refuses with remediation
981
+ steps. The name match is scoped to the coms pool — the same security boundary as `coms_send`.
982
+ - **Standing context is the point.** Re-dispatches (ASK_USER answers, research resumes) go back to
983
+ the same peer session, so a Claude Code reviewer keeps its review context across rounds.
984
+ - **Visibility.** The member's grid card shows a `⇄coms <peer-model>` badge, history entries are
985
+ annotated `(coms)`, and `/af-dispatch-policy` prints the resolved routing per member with live-peer
986
+ status.
987
+ - **Limitations.** `/af-agents-kill` on a coms-backed run only abandons the wait — the peer keeps
988
+ running in its own pane and cannot be killed from the hub (`/af-agents-restart` abandons, then
989
+ re-dispatches). `/af-zoom` shows only the final reply (there is no stream), tool counts stay 0, and
990
+ context% is a registry snapshot. `/af-agent-model` overrides apply only to native(-fallback) runs —
991
+ the peer's model is set in `peers.yaml`.
992
+
993
+ Missing file = everything native. HOW a peer runs (persona, model, `runner: claude-code`, env) stays
994
+ in `peers.yaml`; this file only decides WHEN the hub prefers a peer over a native spawn.
995
+
996
+ ### Handoff
997
+
998
+ `/af-handoff <peer>` transfers the session to another **main** agent. Following the plan's
999
+ **decision G1**, it does *not* try to extract a compaction summary; instead it asks the dispatcher
1000
+ LLM to compose a **self-contained brief** ("everything the target needs, assume no shared history"),
1001
+ then `coms_send`s that brief to the peer, `coms_await`s the reply, and relays it back — in the
1002
+ configured user-facing language. When the handoff `coms_send` fires, the hub appends machine-generated
1003
+ sections after the LLM brief: `## Verification ledger (verbatim, machine-appended)` with every current
1004
+ assertion in canonical ledger form, and `## Artifact index` with artifact paths plus first headings.
1005
+ The target peer must treat the machine-appended ledger as the contract, not the paraphrased brief.
1006
+ The target peer takes over; the source relays the result. There is no raw session copy (pi sessions
1007
+ aren't portable between live agents). The target must be a peer in your pool — `/af-handoff` resolves
1008
+ through the same [scope boundary](#pool-scope-is-the-reach-boundary) as `coms_send`, so you cannot
1009
+ hand a session to a peer you cannot see.
1010
+
1011
+ ### Pool widget
1012
+
1013
+ A live "pool" widget lists connected peers with name, model, and live context usage, refreshed by a
1014
+ ping cycle; a keepalive cycle re-writes this session's own registry entry (and self-heals it if an
1015
+ external prune removed it). Both timers are `unref`'d so they never hold the process open.
1016
+
1017
+ ### Purpose
1018
+
1019
+ The coms identity `purpose` is the `--purpose` CLI flag when set, otherwise the default
1020
+ `agent-hub dispatcher`. There is no runtime dispatcher-persona picker.
1021
+
1022
+ ### Graceful degradation
1023
+
1024
+ If the coms socket can't bind at start-up (`comsReady` stays `false`), the session degrades to a
1025
+ local dispatcher without coms: the `coms_*` tools are withheld from `setActiveTools`, the
1026
+ `/af-handoff` command refuses with a notice, and the "Peer agents (coms)" prompt section is omitted.
1027
+ Orchestration, research helpers, and the grid keep working.
1028
+
1029
+ ### Tool surface
1030
+
1031
+ `setActiveTools` always preserves the orchestration surface and adds runtime-ready capabilities.
1032
+ Operator work mode also preserves the baseline direct/extension tools; orchestrator work mode does not.
1033
+ Coms tools are active only when coms is ready, Herdr tools only in a live Herdr pane, and `ask_user`
1034
+ only when registered. Work mode switching recomputes this list live without touching session state.
1035
+
1036
+ `set_assertions` / `update_assertion` / `get_assertions` are the always-on Verification Contract ledger tools (see
1037
+ [What it does](#what-it-does)); like `dispatch_agent` / `spawn_research` they stay on the
1038
+ orchestration surface in both work modes.
1039
+
1040
+ ## Optional Hermes local monitor transport
1041
+
1042
+ The optional monitor is an Agent Fleet-owned transport boundary, not a Hermes runtime API or a
1043
+ bundled Hermes plugin. When enabled, `agent-hub` publishes dispatcher-turn and specialist-run
1044
+ state and owns generation-safe cancellation. A separate local Hermes UI or operator client may
1045
+ consume the owner-only discovery + Unix-socket contract documented in
1046
+ [`hermes/README.md`](../../../hermes/README.md#local-agent-hub-monitor-integration).
1047
+
1048
+ Set these before the hub starts:
1049
+
1050
+ ```bash
1051
+ export AGENT_FLEET_PROFILE_ID="approved-profile-id"
1052
+ export AGENT_FLEET_MONITOR_RUNTIME_DIR="/absolute/owner-only/runtime-root"
1053
+ ```
1054
+
1055
+ Both are required for monitor startup; the runtime root must be absolute and owner-only, and the
1056
+ profile ID must be a safe identifier. The monitor also starts only for a Herdr-backed hub with
1057
+ `HERDR_WORKSPACE_ID` and `HERDR_PANE_ID`; retain those values and `HERDR_SOCKET_PATH` in the
1058
+ standard `just fleet --agents <roster> --peers <preset>` flow. Workspace labels are display metadata, not monitor identity.
1059
+
1060
+ The live contract exposes three authenticated newline-delimited JSON requests: `snapshot`, cursor-
1061
+ based `output`, and exact-generation `cancel`. The monitor is local-only and fails closed when its
1062
+ profile discovery, lease, token, or Unix socket is unavailable. A native cancel targets only the
1063
+ matching hub-owned process generation. A coms cancel abandons the local wait only; its peer can
1064
+ continue. Neither path controls or closes a Herdr workspace/pane.
1065
+
1066
+ Example startup:
1067
+
1068
+ ```bash
1069
+ monitor_runtime="${XDG_RUNTIME_DIR:?}/agent-fleet-monitor"
1070
+ install -d -m 700 "$monitor_runtime"
1071
+ AGENT_FLEET_PROFILE_ID=dev \
1072
+ AGENT_FLEET_MONITOR_RUNTIME_DIR="$monitor_runtime" \
1073
+ just fleet --agents default --peers default
1074
+ ```
1075
+
1076
+ No Desktop/backend plugin installation is required or provided. Consumers must re-discover after
1077
+ lease or socket loss and must never persist or log the token.
1078
+
1079
+ ## Requires
1080
+
1081
+ - `.pi/agents/teams.yaml` for fixed specialist teams, the referenced persona `.md` files, and
1082
+ (strongly recommended) [`pi-ask-user`](https://github.com/edlsh/pi-ask-user).
1083
+ - `.pi/damage-control-rules.yaml` for every guarded `just fleet` Pi mode.
1084
+ - Nothing extra in-repo for coms — the peer registry lives at `~/.pi/coms/` and is created at
1085
+ runtime.
1086
+
1087
+ ## Usage
1088
+
1089
+ ```bash
1090
+ # Unified Fleet interface (Fleet Core + Agent Hub are loaded together)
1091
+ just fleet
1092
+ just fleet --work-mode operator --agents frontend --project myrepo
1093
+ just fleet --agents frontend --peers frontend --project myrepo
1094
+
1095
+ # equivalent direct guarded launch
1096
+ pi -e .pi/harnesses/damage-control-continue/index.ts -e .pi/harnesses/ask-user-remote/index.ts -e .pi/harnesses/agent-hub/index.ts
1097
+ pi -e .pi/harnesses/damage-control-continue/index.ts -e .pi/harnesses/ask-user-remote/index.ts -e .pi/harnesses/agent-hub/index.ts --name releaser --explicit
1098
+
1099
+ # direct unguarded launch, only when you intentionally want to skip damage-control
1100
+ pi -e .pi/harnesses/agent-hub/index.ts
1101
+ ```
1102
+
1103
+ Identity flags: `--name`, `--purpose`, `--project`, `--color`, `--explicit`.
1104
+
1105
+ ### Safety scope
1106
+
1107
+ `just fleet` and `just fleet --no-coms` load Fleet Core before `agent-hub`, so guardrails and `ask_user` apply
1108
+ to hub/dispatcher tool calls in that parent pi process — and because it is the *continue* variant, a
1109
+ blocked dispatcher call feeds back and the turn keeps going rather than aborting. Specialist and
1110
+ research agents are spawned as separate pi subprocesses with `--no-extensions` — but `agent-hub`
1111
+ resolves `damage-control-continue` from this session's `-e` flags, else the repo-local harness, and
1112
+ re-loads it into every native specialist, research helper, and nested delegate via explicit `-e`.
1113
+ `--no-extensions` keeps discovery off, so children never auto-load `.pi/extensions/` utilities or
1114
+ recursively re-load `agent-hub`; the explicit guardrail still checks every child's tool calls against
1115
+ `.pi/damage-control-rules.yaml`. Protected-path blocks escalate to the hub for explicit approval;
1116
+ protected deletions offer only Deny or Allow once, while inherently dangerous command patterns are
1117
+ non-exemptible. Denial or timeout blocks the call without aborting the child's turn. If continue
1118
+ cannot be resolved, dispatch is refused—children are never spawned unguarded. Research helpers are
1119
+ additionally read-only by construction. Guided setup enforces `agent-hub` ⇒
1120
+ `damage-control-continue` + `ask-user-remote`.
1121
+
1122
+ ### Related recipes
1123
+
1124
+ ```bash
1125
+ # Operator/native work without coms
1126
+ just fleet --no-coms
1127
+
1128
+ # Hub-only Herdr workspace and a combined topology
1129
+ just fleet --herdr --project af
1130
+ just fleet --agents default --peers docs --project af
1131
+ just fleet --agents default --peers docs --project af --dry-run
1132
+
1133
+ # Compatibility aliases (accepted with migration warnings)
1134
+ just fleet hub --solo
1135
+ just fleet team docs
1136
+
1137
+ # Snapshot refs / close cleanly / restore conversations
1138
+ just fleet snapshot docs
1139
+ just fleet down docs
1140
+ just fleet resume docs
1141
+ ```
1142
+
1143
+ `peers.yaml` groups reusable peers into named teams; each entry is `name` / `persona`
1144
+ (+ optional `model`). The persona's frontmatter `description`/`color` become the peer's
1145
+ coms purpose/color.
1146
+
1147
+ ## How it differs from its sources
1148
+
1149
+ - **Embedded, not stacked (decision 1).** coms is folded into this one `index.ts`; the identity
1150
+ flags are registered once. Loading `coms` as a second `-e` would double-register
1151
+ `--name/--purpose/...` and abort start-up.
1152
+ - **Single `session_start`.** coms init is folded into the former dispatcher's `session_start` and
1153
+ guarded by `if (!comsReady)`, so `/new` reuses the same peer identity (no leaked socket).
1154
+ - **Dispatcher is also a peer.** `setActiveTools` lists `coms_*` alongside `dispatch_agent` +
1155
+ `spawn_research` (+ `ask_user`); the system prompt gains a "Peer agents (coms)" section when coms
1156
+ is ready. The persona's `description` drives the coms `purpose` (decision 6 / Phase 6 peer
1157
+ mapping) instead of a static `--purpose`.
1158
+ - **`/af-handoff` uses an LLM-composed brief**, not a compaction-summary extraction (decision G1).
1159
+ - **Clean shutdown** SIGTERMs any running specialist/research children, clears the coms pool
1160
+ widget, and removes the registry entry on `session_shutdown` / SIGINT / SIGTERM.