@chankov/agent-fleet 0.0.4 → 0.0.5

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 (321) hide show
  1. package/.claude/commands/set-hermes-telegram.md +15 -0
  2. package/.opencode/commands/af-set-hermes-telegram.md +15 -0
  3. package/.pi/agents/dispatch-policy.yaml +1 -1
  4. package/.pi/agents/peers.yaml +4 -4
  5. package/.pi/extensions/chrome-devtools-mcp/README.md +1 -1
  6. package/.pi/extensions/mcp-bridge/README.md +1 -1
  7. package/.pi/harnesses/agent-hub/README.md +26 -26
  8. package/.pi/harnesses/agent-hub/index.ts +6 -6
  9. package/.pi/harnesses/agent-hub/monitor-lifecycle.ts +1 -1
  10. package/.pi/harnesses/agent-hub/monitor-publisher.ts +3 -3
  11. package/.pi/harnesses/agent-hub/monitor-session-bridge.ts +1 -1
  12. package/.pi/harnesses/agent-hub/package.json +1 -1
  13. package/.pi/harnesses/ask-user-remote/README.md +1 -0
  14. package/.pi/harnesses/ask-user-remote/index.ts +36 -8
  15. package/.pi/harnesses/coms/README.md +5 -5
  16. package/.pi/harnesses/coms/package.json +1 -1
  17. package/.pi/harnesses/damage-control-continue/README.md +7 -7
  18. package/.pi/harnesses/damage-control-continue/package.json +1 -1
  19. package/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  20. package/.pi/harnesses/lib/hermes-monitor-model.ts +9 -0
  21. package/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  22. package/.pi/harnesses/lib/hermes-monitor-socket.ts +118 -0
  23. package/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  24. package/.pi/prompts/set-hermes-telegram.md +15 -0
  25. package/.versions/0.0.5/.claude/commands/build.md +44 -0
  26. package/.versions/0.0.5/.claude/commands/code-simplify.md +22 -0
  27. package/.versions/0.0.5/.claude/commands/design-agent.md +14 -0
  28. package/.versions/0.0.5/.claude/commands/doctor-agent-fleet.md +17 -0
  29. package/.versions/0.0.5/.claude/commands/orchestrate.md +112 -0
  30. package/.versions/0.0.5/.claude/commands/plan.md +16 -0
  31. package/.versions/0.0.5/.claude/commands/prime.md +22 -0
  32. package/.versions/0.0.5/.claude/commands/review.md +16 -0
  33. package/.versions/0.0.5/.claude/commands/set-hermes-telegram.md +15 -0
  34. package/.versions/0.0.5/.claude/commands/setup-agent-fleet.md +25 -0
  35. package/.versions/0.0.5/.claude/commands/ship.md +72 -0
  36. package/.versions/0.0.5/.claude/commands/spec.md +15 -0
  37. package/.versions/0.0.5/.claude/commands/test.md +19 -0
  38. package/.versions/0.0.5/.claude/commands/webperf.md +32 -0
  39. package/.versions/0.0.5/.claude/orchestrate-teams.yaml +24 -0
  40. package/.versions/0.0.5/.opencode/commands/af-build.md +17 -0
  41. package/.versions/0.0.5/.opencode/commands/af-code-simplify.md +16 -0
  42. package/.versions/0.0.5/.opencode/commands/af-compound.md +16 -0
  43. package/.versions/0.0.5/.opencode/commands/af-design-agent.md +15 -0
  44. package/.versions/0.0.5/.opencode/commands/af-doctor-agent-fleet.md +17 -0
  45. package/.versions/0.0.5/.opencode/commands/af-orchestrate.md +112 -0
  46. package/.versions/0.0.5/.opencode/commands/af-plan.md +16 -0
  47. package/.versions/0.0.5/.opencode/commands/af-prime.md +22 -0
  48. package/.versions/0.0.5/.opencode/commands/af-review.md +15 -0
  49. package/.versions/0.0.5/.opencode/commands/af-set-hermes-telegram.md +15 -0
  50. package/.versions/0.0.5/.opencode/commands/af-setup-agent-fleet.md +15 -0
  51. package/.versions/0.0.5/.opencode/commands/af-ship.md +16 -0
  52. package/.versions/0.0.5/.opencode/commands/af-spec.md +16 -0
  53. package/.versions/0.0.5/.opencode/commands/af-test.md +21 -0
  54. package/.versions/0.0.5/.opencode/commands/af-webperf.md +32 -0
  55. package/.versions/0.0.5/.opencode/orchestrate-teams.yaml +24 -0
  56. package/.versions/0.0.5/.pi/agents/dispatch-policy.yaml +32 -0
  57. package/.versions/0.0.5/.pi/agents/model-profiles.yaml +20 -0
  58. package/.versions/0.0.5/.pi/agents/peers.yaml +146 -0
  59. package/.versions/0.0.5/.pi/agents/teams.yaml +39 -0
  60. package/.versions/0.0.5/.pi/damage-control-rules.yaml +297 -0
  61. package/.versions/0.0.5/.pi/extensions/agent-fleet-update-check/README.md +58 -0
  62. package/.versions/0.0.5/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
  63. package/.versions/0.0.5/.pi/extensions/agent-fleet-update-check/package.json +6 -0
  64. package/.versions/0.0.5/.pi/extensions/btw/README.md +118 -0
  65. package/.versions/0.0.5/.pi/extensions/btw/index.ts +917 -0
  66. package/.versions/0.0.5/.pi/extensions/btw/package.json +6 -0
  67. package/.versions/0.0.5/.pi/extensions/btw/state.js +179 -0
  68. package/.versions/0.0.5/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
  69. package/.versions/0.0.5/.pi/extensions/chrome-devtools-mcp/index.ts +92 -0
  70. package/.versions/0.0.5/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  71. package/.versions/0.0.5/.pi/extensions/compact-and-continue/README.md +42 -0
  72. package/.versions/0.0.5/.pi/extensions/compact-and-continue/index.ts +120 -0
  73. package/.versions/0.0.5/.pi/extensions/compact-and-continue/package.json +6 -0
  74. package/.versions/0.0.5/.pi/extensions/mcp-bridge/README.md +46 -0
  75. package/.versions/0.0.5/.pi/extensions/mcp-bridge/index.ts +206 -0
  76. package/.versions/0.0.5/.pi/extensions/mcp-bridge/package.json +6 -0
  77. package/.versions/0.0.5/.pi/extensions/package-lock.json +1143 -0
  78. package/.versions/0.0.5/.pi/extensions/package.json +9 -0
  79. package/.versions/0.0.5/.pi/extensions/pi-voice-stt/README.md +201 -0
  80. package/.versions/0.0.5/.pi/extensions/pi-voice-stt/config.ts +198 -0
  81. package/.versions/0.0.5/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  82. package/.versions/0.0.5/.pi/extensions/pi-voice-stt/index.ts +248 -0
  83. package/.versions/0.0.5/.pi/extensions/pi-voice-stt/package.json +6 -0
  84. package/.versions/0.0.5/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  85. package/.versions/0.0.5/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  86. package/.versions/0.0.5/.pi/harnesses/agent-hub/README.md +798 -0
  87. package/.versions/0.0.5/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  88. package/.versions/0.0.5/.pi/harnesses/agent-hub/artifacts.js +92 -0
  89. package/.versions/0.0.5/.pi/harnesses/agent-hub/backend-policy.js +153 -0
  90. package/.versions/0.0.5/.pi/harnesses/agent-hub/delegate.ts +386 -0
  91. package/.versions/0.0.5/.pi/harnesses/agent-hub/drift-watchdog.js +165 -0
  92. package/.versions/0.0.5/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  93. package/.versions/0.0.5/.pi/harnesses/agent-hub/footer.ts +29 -0
  94. package/.versions/0.0.5/.pi/harnesses/agent-hub/helpers.ts +214 -0
  95. package/.versions/0.0.5/.pi/harnesses/agent-hub/index.ts +8045 -0
  96. package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  97. package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  98. package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  99. package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  100. package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  101. package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-session-bridge.ts +11 -0
  102. package/.versions/0.0.5/.pi/harnesses/agent-hub/package.json +7 -0
  103. package/.versions/0.0.5/.pi/harnesses/agent-hub/research-retention.js +34 -0
  104. package/.versions/0.0.5/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  105. package/.versions/0.0.5/.pi/harnesses/agent-hub/return-contract.js +215 -0
  106. package/.versions/0.0.5/.pi/harnesses/agent-hub/run-budget.js +155 -0
  107. package/.versions/0.0.5/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  108. package/.versions/0.0.5/.pi/harnesses/agent-hub/scope-gate.js +103 -0
  109. package/.versions/0.0.5/.pi/harnesses/agent-hub/spawn.ts +246 -0
  110. package/.versions/0.0.5/.pi/harnesses/agent-hub/version.ts +18 -0
  111. package/.versions/0.0.5/.pi/harnesses/ask-user-remote/README.md +19 -0
  112. package/.versions/0.0.5/.pi/harnesses/ask-user-remote/index.ts +321 -0
  113. package/.versions/0.0.5/.pi/harnesses/ask-user-remote/race-core.js +106 -0
  114. package/.versions/0.0.5/.pi/harnesses/coms/README.md +92 -0
  115. package/.versions/0.0.5/.pi/harnesses/coms/index.ts +1745 -0
  116. package/.versions/0.0.5/.pi/harnesses/coms/package.json +7 -0
  117. package/.versions/0.0.5/.pi/harnesses/coms/version.ts +18 -0
  118. package/.versions/0.0.5/.pi/harnesses/damage-control-continue/README.md +117 -0
  119. package/.versions/0.0.5/.pi/harnesses/damage-control-continue/index.ts +536 -0
  120. package/.versions/0.0.5/.pi/harnesses/damage-control-continue/package.json +7 -0
  121. package/.versions/0.0.5/.pi/harnesses/damage-control-continue/version.ts +18 -0
  122. package/.versions/0.0.5/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  123. package/.versions/0.0.5/.pi/harnesses/lib/herdr-client.ts +458 -0
  124. package/.versions/0.0.5/.pi/harnesses/lib/herdr-presence.ts +288 -0
  125. package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  126. package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-model.ts +9 -0
  127. package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  128. package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-socket.ts +118 -0
  129. package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  130. package/.versions/0.0.5/.pi/harnesses/package-lock.json +35 -0
  131. package/.versions/0.0.5/.pi/harnesses/package.json +9 -0
  132. package/.versions/0.0.5/.pi/prompts/build.md +24 -0
  133. package/.versions/0.0.5/.pi/prompts/code-simplify.md +22 -0
  134. package/.versions/0.0.5/.pi/prompts/doctor-agent-fleet.md +15 -0
  135. package/.versions/0.0.5/.pi/prompts/plan.md +16 -0
  136. package/.versions/0.0.5/.pi/prompts/review.md +16 -0
  137. package/.versions/0.0.5/.pi/prompts/set-hermes-telegram.md +15 -0
  138. package/.versions/0.0.5/.pi/prompts/setup-agent-fleet.md +27 -0
  139. package/.versions/0.0.5/.pi/prompts/ship.md +17 -0
  140. package/.versions/0.0.5/.pi/prompts/spec.md +15 -0
  141. package/.versions/0.0.5/.pi/prompts/test.md +19 -0
  142. package/.versions/0.0.5/.pi/skills/bowser/SKILL.md +145 -0
  143. package/.versions/0.0.5/.version +1 -0
  144. package/.versions/0.0.5/agents/architect.md +23 -0
  145. package/.versions/0.0.5/agents/bowser.md +26 -0
  146. package/.versions/0.0.5/agents/builder.md +53 -0
  147. package/.versions/0.0.5/agents/code-reviewer.md +205 -0
  148. package/.versions/0.0.5/agents/deep-researcher.md +31 -0
  149. package/.versions/0.0.5/agents/documenter.md +18 -0
  150. package/.versions/0.0.5/agents/orchestrator.md +54 -0
  151. package/.versions/0.0.5/agents/plan-reviewer.md +60 -0
  152. package/.versions/0.0.5/agents/planner.md +69 -0
  153. package/.versions/0.0.5/agents/releaser.md +24 -0
  154. package/.versions/0.0.5/agents/researcher.md +28 -0
  155. package/.versions/0.0.5/agents/security-auditor.md +166 -0
  156. package/.versions/0.0.5/agents/test-engineer.md +151 -0
  157. package/.versions/0.0.5/agents/web-debugger.md +42 -0
  158. package/.versions/0.0.5/agents/web-performance-auditor.md +192 -0
  159. package/.versions/0.0.5/codex/CONDUCTOR.md +148 -0
  160. package/.versions/0.0.5/docs/ARCHITECTURE.md +210 -0
  161. package/.versions/0.0.5/docs/agent-fleet-setup.md +366 -0
  162. package/.versions/0.0.5/docs/claude-code-coms-bridge.md +103 -0
  163. package/.versions/0.0.5/docs/codex-remote-conductor.md +170 -0
  164. package/.versions/0.0.5/docs/coms-hermes-bridge.md +179 -0
  165. package/.versions/0.0.5/docs/getting-started.md +183 -0
  166. package/.versions/0.0.5/docs/npm-install.md +337 -0
  167. package/.versions/0.0.5/docs/opencode-setup.md +249 -0
  168. package/.versions/0.0.5/docs/pi-extensions.md +293 -0
  169. package/.versions/0.0.5/docs/pi-setup.md +472 -0
  170. package/.versions/0.0.5/docs/skill-anatomy.md +150 -0
  171. package/.versions/0.0.5/hermes/README.md +231 -0
  172. package/.versions/0.0.5/hermes/skills/hub-conductor/SKILL.md +84 -0
  173. package/.versions/0.0.5/hermes/skills/hub-liaison/SKILL.md +84 -0
  174. package/.versions/0.0.5/hooks/SIMPLIFY-IGNORE.md +90 -0
  175. package/.versions/0.0.5/hooks/coms-stop-hook.mjs +73 -0
  176. package/.versions/0.0.5/hooks/hooks.json +14 -0
  177. package/.versions/0.0.5/hooks/session-start.sh +74 -0
  178. package/.versions/0.0.5/hooks/simplify-ignore.sh +302 -0
  179. package/.versions/0.0.5/justfile +245 -0
  180. package/.versions/0.0.5/references/accessibility-checklist.md +160 -0
  181. package/.versions/0.0.5/references/definition-of-done.md +67 -0
  182. package/.versions/0.0.5/references/fleet-coordination-patterns.md +151 -0
  183. package/.versions/0.0.5/references/observability-checklist.md +91 -0
  184. package/.versions/0.0.5/references/orchestration-patterns.md +370 -0
  185. package/.versions/0.0.5/references/performance-checklist.md +153 -0
  186. package/.versions/0.0.5/references/prompting-patterns.md +380 -0
  187. package/.versions/0.0.5/references/security-checklist.md +179 -0
  188. package/.versions/0.0.5/references/testing-patterns.md +236 -0
  189. package/.versions/0.0.5/scripts/codex-conductor.ts +41 -0
  190. package/.versions/0.0.5/scripts/codex-remote-control.ts +167 -0
  191. package/.versions/0.0.5/scripts/coms-claude-bridge.ts +286 -0
  192. package/.versions/0.0.5/scripts/coms-cli.ts +484 -0
  193. package/.versions/0.0.5/scripts/coms-hermes-bridge.ts +413 -0
  194. package/.versions/0.0.5/scripts/fleet.ts +141 -0
  195. package/.versions/0.0.5/scripts/hermes-monitor-capability-runner.ts +25 -0
  196. package/.versions/0.0.5/scripts/hermes-monitor-scenario.ts +7 -0
  197. package/.versions/0.0.5/scripts/lib/claude-bridge-core.ts +100 -0
  198. package/.versions/0.0.5/scripts/lib/codex-conductor.ts +88 -0
  199. package/.versions/0.0.5/scripts/lib/codex-remote-control.ts +480 -0
  200. package/.versions/0.0.5/scripts/lib/coms-envelope.ts +539 -0
  201. package/.versions/0.0.5/scripts/lib/fake-herdr-server.ts +88 -0
  202. package/.versions/0.0.5/scripts/lib/fleet-command.ts +109 -0
  203. package/.versions/0.0.5/scripts/lib/herdr-layout.ts +263 -0
  204. package/.versions/0.0.5/scripts/lib/hermes-bridge-core.ts +241 -0
  205. package/.versions/0.0.5/scripts/lib/hermes-monitor-herdr.ts +2 -0
  206. package/.versions/0.0.5/scripts/lib/hermes-monitor-model.ts +3 -0
  207. package/.versions/0.0.5/scripts/lib/hermes-monitor-registry.ts +2 -0
  208. package/.versions/0.0.5/scripts/lib/hermes-monitor-socket.ts +2 -0
  209. package/.versions/0.0.5/scripts/lib/hermes-monitor-store.ts +2 -0
  210. package/.versions/0.0.5/scripts/lib/persona-banner.ts +62 -0
  211. package/.versions/0.0.5/scripts/lib/spawn-stagger.ts +101 -0
  212. package/.versions/0.0.5/scripts/lib/team-project.ts +191 -0
  213. package/.versions/0.0.5/scripts/lib/team-snapshot.ts +147 -0
  214. package/.versions/0.0.5/scripts/peer-banner.ts +40 -0
  215. package/.versions/0.0.5/scripts/team-snapshot.ts +237 -0
  216. package/.versions/0.0.5/scripts/team-up.ts +351 -0
  217. package/.versions/0.0.5/skills/_internal/grilling.md +11 -0
  218. package/.versions/0.0.5/skills/browser-testing-with-devtools/SKILL.md +352 -0
  219. package/.versions/0.0.5/skills/code-review-and-quality/SKILL.md +381 -0
  220. package/.versions/0.0.5/skills/compound-learning/SKILL.md +137 -0
  221. package/.versions/0.0.5/skills/context-engineering/SKILL.md +291 -0
  222. package/.versions/0.0.5/skills/deprecation-and-migration/SKILL.md +206 -0
  223. package/.versions/0.0.5/skills/designing-agents/SKILL.md +394 -0
  224. package/.versions/0.0.5/skills/designing-agents/pi-harness-authoring.md +222 -0
  225. package/.versions/0.0.5/skills/frontend-ui-engineering/SKILL.md +328 -0
  226. package/.versions/0.0.5/skills/git-workflow-and-versioning/SKILL.md +316 -0
  227. package/.versions/0.0.5/skills/guided-workspace-setup/SKILL.md +542 -0
  228. package/.versions/0.0.5/skills/guided-workspace-setup/companion-manifest.json +35 -0
  229. package/.versions/0.0.5/skills/idea-refine/SKILL.md +182 -0
  230. package/.versions/0.0.5/skills/idea-refine/examples.md +238 -0
  231. package/.versions/0.0.5/skills/idea-refine/frameworks.md +99 -0
  232. package/.versions/0.0.5/skills/idea-refine/refinement-criteria.md +113 -0
  233. package/.versions/0.0.5/skills/idea-refine/scripts/idea-refine.sh +15 -0
  234. package/.versions/0.0.5/skills/incremental-implementation/SKILL.md +287 -0
  235. package/.versions/0.0.5/skills/interview-me/SKILL.md +226 -0
  236. package/.versions/0.0.5/skills/orchestration-verification/SKILL.md +181 -0
  237. package/.versions/0.0.5/skills/peer-coms/SKILL.md +90 -0
  238. package/.versions/0.0.5/skills/performance-optimization/SKILL.md +350 -0
  239. package/.versions/0.0.5/skills/planning-and-task-breakdown/SKILL.md +236 -0
  240. package/.versions/0.0.5/skills/security-and-hardening/SKILL.md +461 -0
  241. package/.versions/0.0.5/skills/spec-driven-development/SKILL.md +245 -0
  242. package/.versions/0.0.5/skills/using-agent-skills/SKILL.md +199 -0
  243. package/.versions/0.0.5/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
  244. package/.versions/0.0.5/vendor/agent-skills-upstream/LICENSE +21 -0
  245. package/.versions/0.0.5/vendor/agent-skills-upstream/README.md +11 -0
  246. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
  247. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  248. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  249. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  250. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  251. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
  252. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  253. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  254. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
  255. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  256. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  257. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  258. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  259. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  260. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  261. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  262. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  263. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  264. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  265. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
  266. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
  267. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
  268. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
  269. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
  270. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
  271. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
  272. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
  273. package/.versions/0.0.5/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
  274. package/CHANGELOG.md +9 -0
  275. package/README.md +14 -13
  276. package/bin/cli.js +83 -1
  277. package/bin/lib/set-hermes-telegram.js +323 -0
  278. package/docs/ARCHITECTURE.md +4 -4
  279. package/docs/agent-fleet-setup.md +1 -1
  280. package/docs/claude-code-coms-bridge.md +4 -4
  281. package/docs/codex-remote-conductor.md +12 -12
  282. package/docs/coms-hermes-bridge.md +62 -4
  283. package/docs/getting-started.md +4 -4
  284. package/docs/opencode-setup.md +1 -0
  285. package/docs/pi-extensions.md +30 -25
  286. package/docs/pi-setup.md +17 -8
  287. package/hermes/README.md +14 -11
  288. package/justfile +141 -152
  289. package/package.json +6 -3
  290. package/references/fleet-coordination-patterns.md +1 -1
  291. package/scripts/coms-hermes-bridge.ts +18 -8
  292. package/scripts/fleet.ts +141 -0
  293. package/scripts/lib/fleet-command.ts +109 -0
  294. package/scripts/lib/hermes-bridge-core.ts +5 -2
  295. package/scripts/lib/hermes-monitor-herdr.ts +2 -28
  296. package/scripts/lib/hermes-monitor-model.ts +3 -9
  297. package/scripts/lib/hermes-monitor-registry.ts +2 -6
  298. package/scripts/lib/hermes-monitor-socket.ts +2 -118
  299. package/scripts/lib/hermes-monitor-store.ts +2 -31
  300. package/scripts/lib/team-project.ts +10 -3
  301. package/scripts/team-snapshot.ts +4 -5
  302. package/scripts/team-up.ts +24 -6
  303. package/skills/guided-workspace-setup/SKILL.md +13 -6
  304. package/skills/guided-workspace-setup/companion-manifest.json +3 -1
  305. package/skills/peer-coms/SKILL.md +1 -1
  306. package/hermes/plugins/agent-fleet-monitor/dashboard/dist/index.js +0 -10
  307. /package/{hermes → .versions/0.0.5/hermes}/desktop-plugins/agent-fleet-monitor/plugin.js +0 -0
  308. /package/{hermes → .versions/0.0.5/hermes}/desktop-plugins/agent-fleet-monitor/state.js +0 -0
  309. /package/{hermes → .versions/0.0.5/hermes}/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +0 -0
  310. /package/{hermes → .versions/0.0.5/hermes}/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +0 -0
  311. /package/{hermes → .versions/0.0.5/hermes}/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +0 -0
  312. /package/{hermes → .versions/0.0.5/hermes}/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +0 -0
  313. /package/{hermes → .versions/0.0.5/hermes}/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +0 -0
  314. /package/{hermes → .versions/0.0.5/hermes}/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +0 -0
  315. /package/{hermes → .versions/0.0.5/hermes}/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +0 -0
  316. /package/{hermes → .versions/0.0.5/hermes}/plugins/agent-fleet-monitor/dashboard/adapter.py +0 -0
  317. /package/{hermes → .versions/0.0.5/hermes}/plugins/agent-fleet-monitor/dashboard/adapter.test.py +0 -0
  318. /package/{hermes → .versions/0.0.5/hermes}/plugins/agent-fleet-monitor/dashboard/manifest.json +0 -0
  319. /package/{hermes → .versions/0.0.5/hermes}/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +0 -0
  320. /package/{hermes → .versions/0.0.5/hermes}/plugins/agent-fleet-monitor/dashboard/plugin_api.py +0 -0
  321. /package/{hermes → .versions/0.0.5/hermes}/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +0 -0
@@ -42,12 +42,12 @@ checks the setup. A simplified port of [`cgarrot/pi-voice-stt`](https://github.c
42
42
  see [.pi/extensions/pi-voice-stt/README.md](../.pi/extensions/pi-voice-stt/README.md).
43
43
 
44
44
  The documented harnesses below are different: each is a **session harness**. They
45
- reshape the whole pi session — some remove every codebase tool and leave only an
46
- orchestration tool, some set UI surfaces, some gate every tool call. Most are loaded
47
- one per session; the supported stack is `damage-control-continue` + `ask-user-remote`
48
- before `agent-hub`, which the `just hub` recipes use by default. They live in
49
- **`.pi/harnesses/`** — a directory pi does *not* auto-discover — so a plain `pi`
50
- run never loads them.
45
+ reshape the whole pi session — some set orchestration/UI surfaces and some gate every
46
+ tool call. The unified `just fleet` entry point composes them with a deterministic
47
+ Fleet Core: `damage-control-continue`, `ask-user-remote`, STT, Compact & Continue,
48
+ BTW, and the update checker. `just fleet hub` adds `agent-hub`; `just fleet peer`
49
+ adds standalone coms. Harnesses live in **`.pi/harnesses/`** — a directory pi does
50
+ *not* auto-discover — so a plain `pi` run still loads no safety/orchestration harness.
51
51
 
52
52
  ### Selective loading — read this first
53
53
 
@@ -57,8 +57,8 @@ all of them. If the harnesses lived there, a plain `pi` run would load them all
57
57
  same CLI flags would abort startup with duplicate registrations. So the harnesses live in
58
58
  `.pi/harnesses/` instead, and you load the desired recipe explicitly:
59
59
 
60
- - through the `justfile` — `just hub`, `just ext-damage-control-continue`, `just safe-coms`, …
61
- - or directly — `pi -e .pi/harnesses/<name>/index.ts`
60
+ - through the unified `justfile` interface — `just fleet`, `just fleet hub`, `just fleet peer <name>`, `just fleet team <preset>`, …
61
+ - or directly — `pi -e .pi/harnesses/<name>/index.ts` (advanced use; you must compose safety/utilities yourself)
62
62
 
63
63
  When you consume this repo from another project, point `pi -e` at the harness file you
64
64
  want, or symlink that one directory into *its* `.pi/harnesses/` — never drop the harnesses
@@ -71,15 +71,20 @@ exception is loading `damage-control-continue` and `ask-user-remote` before `age
71
71
  ## Setup
72
72
 
73
73
  ```bash
74
- just install # one-time — installs runtime deps for extensions + harnesses
75
- just hub # launch the supported multi-agent hub with damage-control guardrails
76
- just --list # see every recipe
74
+ just fleet install # one-time runtime deps only; starts no Pi/harness
75
+ just fleet # guarded Pi + STT and core utilities
76
+ just fleet hub # guarded multi-agent hub
77
+ just fleet team docs # hub + guarded Herdr peer team
78
+ just fleet help # unified command grammar
79
+ just --list # shows the single public `fleet` entry point
77
80
  ```
78
81
 
79
82
  `just install` runs `npm install` for both dependency roots: `.pi/extensions/` for the
80
83
  utilities (`@modelcontextprotocol/sdk`, `typebox`) and `.pi/harnesses/` for the harnesses
81
- (`@sinclair/typebox`, `yaml`). The `@mariozechner/pi-*` packages are provided by the pi
82
- runtime itself.
84
+ (`@sinclair/typebox`, `yaml`). The extension dependencies are also root production dependencies
85
+ of the published `@chankov/agent-fleet` package. This is intentional: npm does not install a
86
+ nested `.pi/extensions/package.json`, and Node resolves symlinked extensions from their real path
87
+ inside the package. The `@mariozechner/pi-*` packages are provided by the pi runtime itself.
83
88
 
84
89
  ---
85
90
 
@@ -87,19 +92,19 @@ runtime itself.
87
92
 
88
93
  | Extension | Category | What it does | Run |
89
94
  |-----------|----------|--------------|-----|
90
- | [agent-hub](../.pi/harnesses/agent-hub/README.md) | Orchestration | Supported multi-agent hub: damage-control guardrails by default via `just hub`, dispatcher grid, specialist delegation, research helpers, persona gate, embedded coms, `/handoff`, peer-as-subagent, and footer `v<version> · <model><thinking> · <team>` — plus, inside a [herdr](https://herdr.dev) pane, fleet tools (`herdr_spawn_peer` / `herdr_read_pane` / `herdr_close_pane` with human confirmation / `herdr_notify`) | `just hub` |
91
- | [ask-user-remote](../.pi/harnesses/ask-user-remote/README.md) | Orchestration | Captures stock `pi-ask-user` and registers the default `ask_user`; with `user-remote` live it races local UI against the Hermes bridge, otherwise it is stock local behavior | loaded by `just hub` / `hub-solo` |
92
- | [damage-control-continue](../.pi/harnesses/damage-control-continue/README.md) | Safety | Only supported safety harness; guards the hub plus every native specialist, researcher, and delegate. Blocks feed back without aborting the turn; protected paths support explicit approval, while dangerous command patterns remain non-exemptible | `just ext-damage-control-continue` |
93
- | [coms](../.pi/harnesses/coms/README.md) | Messaging | Peer-to-peer messaging between pi agents on one machine; launches damage-control-continue-guarded under a chosen name | `just safe-coms <name>` |
94
- | [Hermes local monitor transport](../hermes/README.md#local-agent-hub-monitor-integration) | Optional local companion | Owner-only discovery + Unix socket for agent-hub snapshots, cursor output, and exact-generation cancellation; consumed by a separate local Hermes client | Set the two monitor environment variables, then run `just hub-team <team>` |
95
+ | [agent-hub](../.pi/harnesses/agent-hub/README.md) | Orchestration | Supported multi-agent hub: Fleet Core guardrails, dispatcher grid, specialist delegation, research helpers, persona gate, embedded coms, `/handoff`, peer-as-subagent, and footer `v<version> · <model><thinking> · <team>` — plus, inside a [herdr](https://herdr.dev) pane, fleet tools (`herdr_spawn_peer` / `herdr_read_pane` / `herdr_close_pane` with human confirmation / `herdr_notify`) | `just fleet hub` |
96
+ | [ask-user-remote](../.pi/harnesses/ask-user-remote/README.md) | Orchestration | Captures stock `pi-ask-user` and registers the default `ask_user`; with `user-remote` live it races local UI against the Hermes bridge, otherwise it is stock local behavior | Fleet Core (`just fleet`) |
97
+ | [damage-control-continue](../.pi/harnesses/damage-control-continue/README.md) | Safety | Fleet Core safety harness; guards default Pi, Hub, native children, and Herdr Pi peers. Blocks feed back without aborting the turn; protected paths support explicit approval, while dangerous command patterns remain non-exemptible | `just fleet` |
98
+ | [coms](../.pi/harnesses/coms/README.md) | Messaging | Peer-to-peer messaging between agents on one machine, composed with Fleet Core safety and utilities | `just fleet peer <name>` |
99
+ | [Hermes local monitor transport](../hermes/README.md#local-agent-hub-monitor-integration) | Optional local companion | Owner-only discovery + Unix socket for agent-hub snapshots, cursor output, and exact-generation cancellation; consumed by a separate local Hermes client | Set the two monitor environment variables, then run `just fleet team <team>` |
95
100
 
96
101
  Each extension directory has its own `README.md` with the full description, command/tool
97
102
  surface, requirements, and per-extension upstream changes.
98
103
 
99
104
  ### Migration: retired hard-stop harness
100
105
 
101
- The former `.pi/harnesses/damage-control/` hard-stop harness and `just ext-damage-control`
102
- recipe are retired. Refresh pi harnesses with guided setup: it removes only an unchanged,
106
+ The former `.pi/harnesses/damage-control/` hard-stop harness and its standalone recipe
107
+ are retired. Refresh pi harnesses with guided setup: it removes only an unchanged,
103
108
  setup-recorded copy (or an agent-fleet source symlink), preserves user-modified/unowned copies,
104
109
  and refreshes the managed `justfile` region. Use `damage-control-continue` for standalone and
105
110
  Agent Hub safety; missing child safety now fails closed instead of falling back or spawning
@@ -148,7 +153,7 @@ harnesses:
148
153
  - **Persona gate** — requires an orchestrator persona at startup unless disabled in the local
149
154
  override file; the chosen persona also feeds the coms purpose when no explicit `--purpose` is set.
150
155
  - **Operator controls** — `/zoom` timeline inspection plus child-agent kill/restart controls.
151
- - **Damage-control + ask_user by default** — `just hub` / `just hub-solo` load the
156
+ - **Damage-control + ask_user by default** — `just fleet hub` and `just fleet hub --solo` load the
152
157
  `damage-control-continue` safety harness and `ask-user-remote` before `agent-hub`, so the
153
158
  dispatcher's tool calls are checked against the rules file and the `askUserAvailable` probe sees
154
159
  `ask_user`. A blocked call feeds back and the turn keeps going rather than aborting. `agent-hub` also
@@ -161,7 +166,7 @@ harnesses:
161
166
  and a missing continue harness refuses child dispatch.
162
167
  - **Embedded coms** — peer discovery, `coms_list` / `coms_send` / `coms_get` / `coms_await`,
163
168
  `/handoff`, and peer-as-subagent flows.
164
- - **Solo mode** — `just hub-solo` keeps the dispatcher grid, delegation, research helpers, persona
169
+ - **Solo mode** — `just fleet hub --solo` keeps the dispatcher grid, delegation, research helpers, persona
165
170
  gate, and controls, but starts without the embedded coms layer.
166
171
  - **Optional Hermes local monitor transport** — uses `AGENT_FLEET_PROFILE_ID`, the absolute
167
172
  `AGENT_FLEET_MONITOR_RUNTIME_DIR`, and the Herdr `HERDR_WORKSPACE_ID` and `HERDR_PANE_ID`
@@ -208,7 +213,7 @@ The `justfile` sets `dotenv-load`, so a `.env` file at the repo root is auto-loa
208
213
  | `AZURE_SPEECH_KEY` | `pi-voice-stt` (azure backend) | Azure Speech resource key |
209
214
  | `AZURE_SPEECH_ENDPOINT` | `pi-voice-stt` (azure backend) | Azure resource endpoint, used when `provider.endpoint` is unset |
210
215
  | `PI_STT_CONFIG` / `PI_STT_KEYBIND` | `pi-voice-stt` | Override config (inline JSON or path) / the record hotkey (default `alt+s`) |
211
- | `AGENT_FLEET_SPAWN_DELAY` | `_peer` / `_peer-plus` recipes | Seconds to sleep before launching pi in a fleet pane (set per pane by `team-up`/`team-resume`, see below) |
216
+ | `AGENT_FLEET_SPAWN_DELAY` | `_peer` / `_peer-plus` recipes | Seconds to sleep before launching pi in a fleet pane (set per pane by `just fleet team`/`just fleet resume`, see below) |
212
217
 
213
218
  The `chrome-devtools-mcp` server starts once at extension load, so changing its vars needs a pi
214
219
  restart / `/reload` to take effect.
@@ -218,7 +223,7 @@ restart / `/reload` to take effect.
218
223
  pi loads its credential store (`~/.pi/agent/auth.json`) once at boot under a short-retry
219
224
  file lock. When the stored OAuth token is stale, the first pi to boot refreshes it over
220
225
  the network *while holding that lock*; sibling panes spawned in the same instant (as
221
- `just team-up` / `just hub-team` / `just team-resume` do) lose the lock race and come up
226
+ `just fleet team` / `just fleet resume` do) lose the lock race and come up
222
227
  with every provider showing **unconfigured**. To dodge this, the team scripts check
223
228
  `auth.json` before spawning (only `type`/`expires` are read — values never leave the
224
229
  process): if any OAuth credential is expired or about to expire, one pi pane (the hub
@@ -240,7 +245,7 @@ These ported files are runtime dependencies of the extensions above:
240
245
  The earlier `reviewer` and `red-team` personas were folded into `code-reviewer` and
241
246
  `security-auditor`; the remaining team/peer configs already reference the canonical names.
242
247
  A peer entry may carry an optional `extensions:` field (comma-separated names under
243
- `.pi/extensions/`) — `team-up` then routes it through the `_peer-plus` recipe so those
248
+ `.pi/extensions/`) — Fleet's team launcher then routes it through the `_peer-plus` recipe so those
244
249
  extensions load into the peer process. The `web-debugger` peer uses this to get
245
250
  `chrome-devtools-mcp`'s `chrome_devtools__*` tools (see the two-browser-stacks section above).
246
251
  - **`.pi/damage-control-rules.yaml`** — the destructive-command / protected-path rule set
package/docs/pi-setup.md CHANGED
@@ -181,24 +181,29 @@ This repo ships **3 supported session harnesses** ported or consolidated from [d
181
181
 
182
182
  - **Orchestration** — `agent-hub` (dispatcher grid, specialist delegation, research helpers, persona gate, embedded coms)
183
183
  - **Safety** — `damage-control-continue` (fail-closed blocks feed back so the agent can report or safely adapt)
184
- - **Pi-to-Pi messaging** — `coms` (launched guarded via `just safe-coms <name>`, and embedded in `agent-hub`)
184
+ - **Pi-to-Pi messaging** — `coms` (launched guarded via `just fleet peer <name>`, and embedded in `just fleet hub`)
185
185
 
186
186
  Unlike the utilities above, each harness reshapes the entire pi session, and most are loaded one per session rather than all at once. The supported stack loads `damage-control-continue` and `ask-user-remote` before `agent-hub`; the hub then re-loads continue into every native specialist, research helper, and nested delegate. Protected-path blocks can escalate for explicit approval, while dangerous command patterns remain non-exemptible. Missing child safety refuses dispatch. pi auto-discovers and loads *everything* under `.pi/extensions/`, so the harnesses deliberately live in a separate directory — **`.pi/harnesses/`** — which pi does *not* auto-discover. **Never copy or symlink a harness into `.pi/extensions/`**: that would load it on every plain `pi` run, and stacking all harnesses aborts startup (harnesses that register the same CLI flags clash). Load a harness recipe explicitly instead — there is nothing to symlink:
187
187
 
188
188
  ```bash
189
189
  # from the agent-fleet clone, via the bundled justfile
190
- just --list # list every harness recipe
191
- just hub # launch the guarded consolidated multi-agent hub
190
+ just fleet help # unified runtime grammar
191
+ just fleet # guarded Pi + STT and core utilities
192
+ just fleet hub # guarded consolidated multi-agent hub
193
+ just fleet team docs # hub + guarded Herdr peer team
194
+ just --list # confirms the single public Fleet entry point
192
195
 
193
196
  # or directly, from anywhere — point pi -e at the guarded harness stack
197
+ # Advanced/manual equivalent of only the harness part; `just fleet hub` also
198
+ # loads STT, Compact & Continue, BTW, and update-check as Fleet Core utilities.
194
199
  pi -e /path/to/agent-fleet/.pi/harnesses/damage-control-continue/index.ts -e /path/to/agent-fleet/.pi/harnesses/ask-user-remote/index.ts -e /path/to/agent-fleet/.pi/harnesses/agent-hub/index.ts
195
200
  ```
196
201
 
197
202
  **Upgrading from the retired hard-stop harness:** `.pi/harnesses/damage-control/` and
198
- `just ext-damage-control` are no longer shipped. Re-run guided setup to remove only an
199
- unchanged setup-owned copy (or source symlink) and refresh the managed `justfile` region;
200
- user-modified and unowned copies are preserved. Use `just ext-damage-control-continue` for
201
- a standalone safety session.
203
+ the old standalone damage-control recipes are no longer shipped. Re-run guided setup to
204
+ remove only an unchanged setup-owned copy (or source symlink) and refresh the managed
205
+ `justfile` region; user-modified and unowned copies are preserved. Use `just fleet` for a
206
+ standalone guarded session.
202
207
 
203
208
  The harnesses have their own runtime dependencies (`yaml`, `@sinclair/typebox`) declared in `.pi/harnesses/package.json` — separate from the extension deps above. Install both at once with `just install` from the clone, or run `npm ci` in `.pi/harnesses/` as well. The [pi extension catalog](pi-extensions.md) has the full list, per-extension `README.md` pointers, required environment variables (for `chrome-devtools-mcp`), and what changed from upstream.
204
209
 
@@ -396,13 +401,17 @@ If skill autocomplete is empty, check that `.agents/skills` points to a director
396
401
 
397
402
  If lifecycle command autocomplete is empty, check that `.pi/prompts` points to a directory containing the command Markdown files and run `/reload` or restart pi.
398
403
 
399
- If extension loading reports `Cannot find module '@modelcontextprotocol/sdk/client/index.js'`, the extension runtime dependencies are not installed. Run:
404
+ If `/chrome_devtools-status` reports `Cannot find module '@modelcontextprotocol/sdk/client/index.js'`, the MCP extension loaded but its runtime initialization failed. An `[Extensions]` startup entry alone does not prove its tools registered.
405
+
406
+ For a cloned or copied install, run:
400
407
 
401
408
  ```bash
402
409
  cd /path/to/agent-fleet/.pi/extensions
403
410
  npm ci
404
411
  ```
405
412
 
413
+ For extensions symlinked into a published `@chankov/agent-fleet` package, update to a package version that declares the extension dependencies at its root, then restart/reload pi. Do not rely on installing only the target workspace's `.pi/extensions/node_modules`: Node may resolve the symlink to the package's real path. Verify the repair with `/chrome_devtools-status`; it must report `connected` and a non-zero registered tool count.
414
+
406
415
  The harnesses install separately — if a harness reports `Cannot find module 'yaml'` or `'@sinclair/typebox'`, run `npm ci` in `.pi/harnesses/` as well (or `just install` from the clone, which does both).
407
416
 
408
417
  Then run `/reload` or restart pi.
package/hermes/README.md CHANGED
@@ -9,21 +9,24 @@ This directory contains in-repository Hermes skills for the coms Hermes bridge p
9
9
 
10
10
  ## Install
11
11
 
12
- Install a skill into the desired Hermes profile with either option supported by your Hermes setup:
12
+ For `hub-liaison`, use Agent Fleet's deterministic profile-aware installer rather than a raw copy:
13
13
 
14
14
  ```bash
15
- hermes skills install hermes/skills/hub-liaison
16
- hermes skills install hermes/skills/hub-conductor
15
+ agent-fleet set-hermes-telegram status --profile default
16
+ agent-fleet set-hermes-telegram install --profile default
17
+ # Only when status reports a differing local tree:
18
+ agent-fleet set-hermes-telegram install --profile default --force
19
+ # Restart a currently running gateway only by explicit request:
20
+ agent-fleet set-hermes-telegram install --profile default --force --restart
17
21
  ```
18
22
 
19
- Or copy the skill directories into the profile's skills directory:
23
+ The corresponding Pi/Claude slash command is `/set-hermes-telegram`; OpenCode uses `/af-set-hermes-telegram`. The installer resolves the real profile path via `hermes profile show`, refuses drift without `--force`, backs up forced replacements, copies atomically, and verifies skill/tool/gateway readiness. It never sends a test Telegram message and never starts a stopped gateway. See [the bridge runbook](../docs/coms-hermes-bridge.md#set-hermes-telegram-bridge-control).
20
24
 
21
- ```bash
22
- cp -R hermes/skills/hub-liaison ~/.hermes/<profile>/skills/
23
- cp -R hermes/skills/hub-conductor ~/.hermes/<profile>/skills/
24
- ```
25
+ The current `hermes skills install` CLI documents registry identifiers and direct HTTP(S) `SKILL.md` URLs, not local directories, so `hermes skills install hermes/skills/hub-liaison` is not the supported local installation path.
26
+
27
+ `hub-conductor` remains a source artifact for the human's dev/conductor profile. Install it by a reviewed local copy into the path reported by `hermes profile show <profile>`, or publish/install it through a pinned Hermes skill source; it is intentionally not managed by the Telegram bridge command.
25
28
 
26
- Use `hub-liaison` in the gateway-owning Telegram profile and `hub-conductor` in the human's dev/conductor profile. Verify availability with your normal Hermes skill listing command before relying on them.
29
+ Use `hub-liaison` in the gateway-owning Telegram profile and `hub-conductor` in the human's dev/conductor profile. Verify availability with `hermes --profile <profile> skills list --enabled-only` before relying on them.
27
30
 
28
31
  ## Local agent-hub monitor integration
29
32
 
@@ -66,7 +69,7 @@ install -d -m 700 "$monitor_runtime"
66
69
  export AGENT_FLEET_PROFILE_ID="dev"
67
70
  export AGENT_FLEET_MONITOR_RUNTIME_DIR="$monitor_runtime"
68
71
 
69
- just hub-team default
72
+ just fleet team default
70
73
  ```
71
74
 
72
75
  If either monitor variable is missing or invalid, or if the hub lacks stable Herdr identity, the
@@ -213,7 +216,7 @@ For `hub-conductor`, either start the pi team/pool outside Hermes first, or use
213
216
 
214
217
  ```bash
215
218
  just conductor docs # conductor pane (`hermes -p dev`) + docs team panes
216
- just conductor-dry docs # dry-run layout, no herdr calls
219
+ just fleet conductor hermes docs --dry-run # preview, no Herdr calls
217
220
  ```
218
221
 
219
222
  Inside Hermes, discover and delegate only through coms:
package/justfile CHANGED
@@ -28,70 +28,120 @@ set dotenv-load := true
28
28
  # unaffected (the fleet scripts import only relative paths + node builtins).
29
29
  node_ts := "node --experimental-strip-types --preserve-symlinks --preserve-symlinks-main"
30
30
 
31
- # List all recipes
31
+ # Fleet Core is the invariant Pi runtime used by every new `just fleet` mode and
32
+ # every Pi peer spawned into Herdr. `--no-extensions` makes the baseline
33
+ # deterministic; these modules are then loaded explicitly:
34
+ # • damage-control-continue — fail-closed safety with actionable feedback
35
+ # • ask-user-remote — stock local ask_user, optionally raced with Hermes
36
+ # • pi-voice-stt — Alt+S dictation (silent no-op until configured)
37
+ # • compact-and-continue — request_compaction at explicit workflow checkpoints
38
+ # • btw — /btw and Alt+' side sessions
39
+ # • update check — bounded, non-blocking package update notification
40
+ # `--browser` additionally loads chrome-devtools-mcp. `--all-extensions` removes
41
+ # `--no-extensions`, so project/global auto-discovered extensions also load; use
42
+ # it only when a session intentionally needs extensions outside Fleet Core.
43
+ fleet_core_extensions := "-e .pi/harnesses/damage-control-continue/index.ts -e .pi/harnesses/ask-user-remote/index.ts -e .pi/extensions/pi-voice-stt/index.ts -e .pi/extensions/compact-and-continue/index.ts -e .pi/extensions/btw/index.ts -e .pi/extensions/agent-fleet-update-check/index.ts"
44
+ fleet_browser_extension := "-e .pi/extensions/chrome-devtools-mcp/index.ts"
45
+
46
+ # Show the complete Fleet command guide, descriptions, and runnable examples.
32
47
  default:
33
- @just --list
48
+ @just fleet help
34
49
 
35
- # ---------------------------------------------------------------- setup
50
+ # ---------------------------------------------------------------- unified Fleet interface
36
51
 
37
- # Install the shared runtime dependencies for the pi extensions + harnesses
38
- install:
52
+ # Agent Fleet — one guarded entry point, additive capabilities, and lifecycle verbs.
53
+ #
54
+ # SAFE INTERACTIVE PI (recommended default)
55
+ # just fleet
56
+ # just fleet --model openai-codex/gpt-5.6-terra
57
+ # just fleet --browser # add live Chrome DevTools tools
58
+ # just fleet --all-extensions # also auto-load project/global extensions
59
+ #
60
+ # ADDRESSABLE COMS PEER
61
+ # just fleet peer nick --project af
62
+ # just fleet peer web-debugger --browser --project af
63
+ #
64
+ # AGENT HUB
65
+ # just fleet hub --project af # dispatcher + embedded coms
66
+ # just fleet hub --solo # dispatcher + local children, no coms
67
+ # just fleet hub --browser --project af # browser tools in the hub/main process
68
+ #
69
+ # HERDR TEAMS (preset names come from .pi/agents/peers.yaml)
70
+ # just fleet team frontend --project af # guarded hub + guarded peer grid
71
+ # just fleet team frontend --no-hub # guarded peer grid only
72
+ # just fleet team review --dry-run # print layout; do not touch Herdr
73
+ # just fleet team web --browser # browser in hub; peer extras still come from YAML
74
+ #
75
+ # TEAM LIFECYCLE
76
+ # just fleet snapshot frontend --project af
77
+ # just fleet down frontend --project af
78
+ # just fleet resume frontend --project af
79
+ #
80
+ # REMOTE CONDUCTORS
81
+ # just fleet conductor hermes docs --project af
82
+ # just fleet conductor codex setup docs --project af
83
+ # just fleet conductor codex pair
84
+ # just fleet conductor codex start
85
+ # just fleet conductor codex docs --project af
86
+ # just fleet conductor codex status
87
+ # just fleet conductor codex stop
88
+ #
89
+ # BOOTSTRAP / HELP
90
+ # just fleet install # npm runtime deps only; starts no harness
91
+ # just fleet help
92
+ #
93
+ # Unified guarded Pi, Hub, peers, teams, lifecycle, and conductor entry point.
94
+ fleet *args:
95
+ @{{node_ts}} scripts/fleet.ts {{args}}
96
+
97
+ # Hidden Fleet Core launcher. Positional booleans are emitted only by fleet.ts.
98
+ _fleet-core browser="false" all_extensions="false" *args:
99
+ discovery="--no-extensions"; if [ "{{all_extensions}}" = "true" ]; then discovery=""; fi; browser_ext=""; if [ "{{browser}}" = "true" ]; then browser_ext="{{fleet_browser_extension}}"; fi; pi $discovery {{fleet_core_extensions}} $browser_ext {{args}}
100
+
101
+ # Hidden guarded peer launcher for an interactive, addressable Fleet node.
102
+ _fleet-peer name browser="false" all_extensions="false" *args:
103
+ discovery="--no-extensions"; if [ "{{all_extensions}}" = "true" ]; then discovery=""; fi; browser_ext=""; if [ "{{browser}}" = "true" ]; then browser_ext="{{fleet_browser_extension}}"; fi; pi $discovery {{fleet_core_extensions}} -e .pi/harnesses/coms/index.ts $browser_ext --name {{name}} {{args}}
104
+
105
+ # Hidden Hub launcher. Agent Hub re-loads Damage Control into every native
106
+ # specialist, researcher, and nested delegate even though children use
107
+ # --no-extensions. `solo=true` disables only the embedded coms layer.
108
+ _fleet-hub solo="false" browser="false" all_extensions="false" *args:
109
+ discovery="--no-extensions"; if [ "{{all_extensions}}" = "true" ]; then discovery=""; fi; browser_ext=""; if [ "{{browser}}" = "true" ]; then browser_ext="{{fleet_browser_extension}}"; fi; solo_flag=""; if [ "{{solo}}" = "true" ]; then solo_flag="--solo"; fi; persona=""; if [ -f agents/orchestrator.md ]; then persona="--append-system-prompt agents/orchestrator.md"; fi; pi $discovery {{fleet_core_extensions}} -e .pi/harnesses/agent-hub/index.ts $browser_ext $solo_flag $persona {{args}}
110
+
111
+ # Hidden dependency bootstrap used by `just fleet install`.
112
+ # It installs only Node runtime dependencies. It does NOT launch Pi, activate a
113
+ # harness, configure STT, install ffmpeg/Herdr, or pair a remote conductor.
114
+ _fleet-install:
39
115
  npm install --prefix .pi/extensions
40
116
  npm install --prefix .pi/harnesses
41
117
 
42
- # Default pi — only the always-on utilities auto-load, no harness
43
- pi:
44
- pi
45
-
46
- # ---------------------------------------------------------------- safety
47
-
48
- # Damage-control: blocks deliver feedback so the agent adapts and keeps working
49
- # instead of aborting the turn. Default guardrail for the hub and native children.
50
- ext-damage-control-continue:
51
- pi -e .pi/harnesses/damage-control-continue/index.ts
52
-
53
- # ---------------------------------------------------------------- orchestration
54
-
55
- # Accepts coms identity flags: --name --purpose --project --color --explicit.
56
- # Loads the orchestrator persona by default (the Verification-Contract dispatcher that owns
57
- # the acceptance assertions — see skills/orchestration-verification); it is appended only if
58
- # agents/orchestrator.md is installed, so the hub still launches when it is absent. Override
59
- # with your own --system-prompt <persona>.md passed after `just hub`.
60
- # Guarded agent hub: damage-control-continue + remote-capable ask_user + dispatcher grid + research helpers + embedded coms + orchestrator.
61
- # The main session and every native child use the continue guardrail; blocked calls
62
- # feed back so the agent can report or safely adapt without aborting its turn.
63
- hub *args:
64
- persona=""; if [ -f agents/orchestrator.md ]; then persona="--append-system-prompt agents/orchestrator.md"; fi; pi -e .pi/harnesses/damage-control-continue/index.ts -e .pi/harnesses/ask-user-remote/index.ts -e .pi/harnesses/agent-hub/index.ts $persona {{args}}
65
-
66
- # Agent hub (solo): guarded hub without the coms layer — fixed specialists + research only.
67
- # Same orchestrator-persona default, remote-capable ask_user, and continue-guardrail main session as `just hub`.
68
- hub-solo *args:
69
- persona=""; if [ -f agents/orchestrator.md ]; then persona="--append-system-prompt agents/orchestrator.md"; fi; pi -e .pi/harnesses/damage-control-continue/index.ts -e .pi/harnesses/ask-user-remote/index.ts -e .pi/harnesses/agent-hub/index.ts --solo $persona {{args}}
70
-
71
- # Internal helper for team-up: launch a reusable coms peer (coms + compact-and-continue + a persona).
72
- # Prints a colored identity banner (peer name + persona purpose) before pi starts,
73
- # so every pane announces who lives in it — works in any terminal, herdr or not.
74
- # AGENT_FLEET_SPAWN_DELAY (set per pane by team-up when the stored pi OAuth token
75
- # is stale) delays this pi's boot so a sibling pane can refresh the token first —
76
- # simultaneous boots race on the auth.json lock and lose their logins.
77
- # Hidden from `just --list` because recipes prefixed with `_` are private.
118
+
119
+ # Internal helper for `fleet team`: launch a reusable GUARDED Pi peer.
120
+ # Every peer gets Fleet Core + coms + its persona. This closes the historical
121
+ # gap where Hub children and standalone peers were protected but Herdr Pi peers were
122
+ # not. `--no-extensions` keeps peer capabilities deterministic; declare extras
123
+ # such as chrome-devtools-mcp in .pi/agents/peers.yaml.
124
+ # AGENT_FLEET_SPAWN_DELAY lets one pane refresh a stale shared OAuth token before
125
+ # sibling Pi processes start. Hidden recipes (`_...`) do not appear in --list.
78
126
  _peer persona name="" model="" session="" project="default":
79
- d="${AGENT_FLEET_SPAWN_DELAY:-0}"; if [ "$d" != "0" ]; then echo "⏳ waiting ${d}s for the pi auth pre-warm (stale OAuth token)"; sleep "$d"; fi; {{node_ts}} scripts/peer-banner.ts {{persona}} {{name}} 2>/dev/null || true; persona_path="agents/{{persona}}.md"; if [ ! -f "$persona_path" ]; then persona_path=".pi/agents/{{persona}}.md"; fi; pi -e .pi/harnesses/coms/index.ts -e .pi/extensions/compact-and-continue/index.ts --project {{project}} --append-system-prompt "$persona_path" {{ if name != "" { "--name " + name } else { "" } }} {{ if model != "" { "--model " + model } else { "" } }} {{ if session != "" { "--session " + session } else { "" } }}
127
+ d="${AGENT_FLEET_SPAWN_DELAY:-0}"; if [ "$d" != "0" ]; then echo "⏳ waiting ${d}s for the pi auth pre-warm (stale OAuth token)"; sleep "$d"; fi; {{node_ts}} scripts/peer-banner.ts {{persona}} {{name}} 2>/dev/null || true; persona_path="agents/{{persona}}.md"; if [ ! -f "$persona_path" ]; then persona_path=".pi/agents/{{persona}}.md"; fi; pi --no-extensions {{fleet_core_extensions}} -e .pi/harnesses/coms/index.ts --project {{project}} --append-system-prompt "$persona_path" {{ if name != "" { "--name " + name } else { "" } }} {{ if model != "" { "--model " + model } else { "" } }} {{ if session != "" { "--session " + session } else { "" } }}
80
128
 
81
- # Like _peer, but also loads extra always-on extensions (comma-separated names under
82
- # .pi/extensions/) into the peer process — e.g. a chrome-devtools-mcp browser-debug peer
83
- # whose `chrome_devtools__*` tools a normal --no-extensions subagent could not get.
129
+ # Guarded peer plus comma-separated explicit extras from .pi/extensions/.
130
+ # Example peers.yaml entry:
131
+ # extensions: chrome-devtools-mcp
132
+ # The extra tools stay in this reusable peer; Hub's headless specialists still
133
+ # run --no-extensions and therefore cannot accidentally inherit them.
84
134
  _peer-plus extensions persona name="" model="" session="" project="default":
85
- d="${AGENT_FLEET_SPAWN_DELAY:-0}"; if [ "$d" != "0" ]; then echo "⏳ waiting ${d}s for the pi auth pre-warm (stale OAuth token)"; sleep "$d"; fi; {{node_ts}} scripts/peer-banner.ts {{persona}} {{name}} 2>/dev/null || true; persona_path="agents/{{persona}}.md"; if [ ! -f "$persona_path" ]; then persona_path=".pi/agents/{{persona}}.md"; fi; extra=""; old_ifs="$IFS"; IFS=','; for x in {{extensions}}; do x="$(echo "$x" | xargs)"; if [ -n "$x" ]; then extra="$extra -e .pi/extensions/$x/index.ts"; fi; done; IFS="$old_ifs"; pi -e .pi/harnesses/coms/index.ts -e .pi/extensions/compact-and-continue/index.ts $extra --project {{project}} --append-system-prompt "$persona_path" {{ if name != "" { "--name " + name } else { "" } }} {{ if model != "" { "--model " + model } else { "" } }} {{ if session != "" { "--session " + session } else { "" } }}
135
+ d="${AGENT_FLEET_SPAWN_DELAY:-0}"; if [ "$d" != "0" ]; then echo "⏳ waiting ${d}s for the pi auth pre-warm (stale OAuth token)"; sleep "$d"; fi; {{node_ts}} scripts/peer-banner.ts {{persona}} {{name}} 2>/dev/null || true; persona_path="agents/{{persona}}.md"; if [ ! -f "$persona_path" ]; then persona_path=".pi/agents/{{persona}}.md"; fi; extra=""; old_ifs="$IFS"; IFS=','; for x in {{extensions}}; do x="$(echo "$x" | xargs)"; if [ -n "$x" ]; then extra="$extra -e .pi/extensions/$x/index.ts"; fi; done; IFS="$old_ifs"; pi --no-extensions {{fleet_core_extensions}} -e .pi/harnesses/coms/index.ts $extra --project {{project}} --append-system-prompt "$persona_path" {{ if name != "" { "--name " + name } else { "" } }} {{ if model != "" { "--model " + model } else { "" } }} {{ if session != "" { "--session " + session } else { "" } }}
86
136
 
87
- # Internal helper for team-up: a `runner: claude-code` peer — interactive
137
+ # Internal team helper for a `runner: claude-code` peer — interactive
88
138
  # Claude Code plus its coms bridge (scripts/coms-claude-bridge.ts) in ONE pane.
89
139
  # The bridge registers the pane as coms peer <name>; the trailing session
90
- # positional maps to `claude --resume <id>` for team-resume.
140
+ # positional maps to `claude --resume <id>` for `just fleet resume`.
91
141
  _claude-peer name model="" session="" project="default":
92
142
  {{node_ts}} scripts/coms-claude-bridge.ts --name {{name}} --project {{project}} & bridge_pid=$!; trap 'kill $bridge_pid 2>/dev/null' EXIT; claude {{ if model != "" { "--model " + model } else { "" } }} {{ if session != "" { "--resume " + session } else { "" } }}
93
143
 
94
- # The team recipes below take the team as a positional arg (defaults to "full")
144
+ # The hidden team implementations take the team as a positional arg (default "full")
95
145
  # and pass everything after it straight to the script.
96
146
  #
97
147
  # Herdr workspace labels are auto-scoped to the CHECKOUT: <worktree-tag>-<mode>-<team>
@@ -110,147 +160,86 @@ _claude-peer name model="" session="" project="default":
110
160
  # NOT a flag — just treats bare key=value args as variable overrides, so it is
111
161
  # silently ignored and the team still joins the "default" pool.
112
162
 
113
- # Team up: spawn every peer of a team from .pi/agents/peers.yaml into a herdr
114
- # workspace (one tiled pane per peer). Requires a running herdr server.
115
- # e.g. just team-up full
116
- # just team-up review --project af
117
- team-up team="full" *args:
163
+ # Peers-only implementation for:
164
+ # just fleet team full --no-hub
165
+ # just fleet team review --no-hub --project af
166
+ _fleet-team-up team="full" *args:
118
167
  {{node_ts}} scripts/team-up.ts --team {{team}} {{args}}
119
168
 
120
- # Team up (dry run): print the resolved layout + per-peer commands without touching herdr.
121
- # e.g. just team-up-dry full
122
- # just team-up-dry review --project af
123
- team-up-dry team="full" *args:
169
+ # Peers-only dry run:
170
+ # just fleet team review --no-hub --dry-run --project af
171
+ _fleet-team-up-dry team="full" *args:
124
172
  {{node_ts}} scripts/team-up.ts --team {{team}} --dry-run {{args}}
125
173
 
126
- # Hub + team in ONE herdr workspace: the guarded hub (`just hub`) in a larger
127
- # main pane, the team's peers tiled beside it.
128
- # e.g. just hub-team docs
129
- # just hub-team review --project af
130
- hub-team team="full" *args:
174
+ # Default team mode: guarded Fleet Hub in the main pane plus guarded peers.
175
+ # just fleet team docs
176
+ # just fleet team review --project af
177
+ _fleet-hub-team team="full" *args:
131
178
  {{node_ts}} scripts/team-up.ts --team {{team}} --hub {{args}}
132
179
 
133
- # Hub + team (dry run): print the combined layout without touching herdr.
134
- # e.g. just hub-team-dry review --project af
135
- hub-team-dry team="full" *args:
180
+ # Hub + team preview without touching Herdr:
181
+ # just fleet team review --dry-run --project af
182
+ _fleet-hub-team-dry team="full" *args:
136
183
  {{node_ts}} scripts/team-up.ts --team {{team}} --hub --dry-run {{args}}
137
184
 
138
- # Hermes conductor + team in ONE herdr workspace: Hermes dev profile in a conductor pane,
139
- # the team's peers tiled beside it. Hermes delegates via coms-cli and never drives herdr.
140
- # e.g. just conductor docs --project af
141
- conductor team="full" *args:
185
+ # Hermes conductor + team:
186
+ # just fleet conductor hermes docs --project af
187
+ _fleet-conductor team="full" *args:
142
188
  {{node_ts}} scripts/team-up.ts --team {{team}} --conductor {{args}}
143
189
 
144
- # Hermes conductor + team (dry run): print the combined layout without touching herdr.
145
- # e.g. just conductor-dry docs --project af
146
- conductor-dry team="full" *args:
190
+ # Hermes conductor preview:
191
+ # just fleet conductor hermes docs --dry-run --project af
192
+ _fleet-conductor-dry team="full" *args:
147
193
  {{node_ts}} scripts/team-up.ts --team {{team}} --conductor --dry-run {{args}}
148
194
 
149
195
  # Experimental Codex remote-control conductor lifecycle (verified with CLI
150
196
  # 0.144.x). Pairing stays interactive and its short-lived code must never be
151
197
  # captured. The user service is singleton across repos/projects.
152
- # e.g. just conductor-codex-setup docs --project af
153
- conductor-codex-setup team="full" *args:
198
+ # just fleet conductor codex setup docs --project af
199
+ _fleet-conductor-codex-setup team="full" *args:
154
200
  {{node_ts}} scripts/codex-remote-control.ts setup-conductor --codex-bin "$(command -v codex)" --repo-root "$(pwd -P)" --coms-dir "$HOME/.pi/coms" --team "{{team}}" --timeout 300000 {{args}}
155
201
 
156
- conductor-codex-reconfigure team="full" *args:
202
+ _fleet-conductor-codex-reconfigure team="full" *args:
157
203
  {{node_ts}} scripts/codex-remote-control.ts reconfigure-conductor --codex-bin "$(command -v codex)" --repo-root "$(pwd -P)" --coms-dir "$HOME/.pi/coms" --team "{{team}}" --timeout 300000 {{args}}
158
204
 
159
- conductor-codex-pair:
160
- {{node_ts}} scripts/codex-remote-control.ts pair
161
-
162
- conductor-codex-start:
163
- {{node_ts}} scripts/codex-remote-control.ts start
164
-
165
- conductor-codex-status:
166
- {{node_ts}} scripts/codex-remote-control.ts status
167
-
168
- conductor-codex-stop:
169
- {{node_ts}} scripts/codex-remote-control.ts stop
170
-
171
- conductor-codex-recover:
172
- {{node_ts}} scripts/codex-remote-control.ts recover --confirm operator-confirmed
173
-
174
- conductor-codex-uninstall:
175
- {{node_ts}} scripts/codex-remote-control.ts uninstall --confirm operator-confirmed
176
-
177
- # Codex conductor + team in one workspace. The root is a requested-state
178
- # control pane; systemd owns the remote-control daemon.
179
- # e.g. just conductor-codex docs --project af
180
- conductor-codex team="full" *args:
181
- {{node_ts}} scripts/team-up.ts --team {{team}} --conductor codex {{args}}
182
-
183
- conductor-codex-dry team="full" *args:
184
- {{node_ts}} scripts/team-up.ts --team {{team}} --conductor codex --dry-run {{args}}
185
-
186
- # Legacy pilot aliases retained for the 0.144.x experimental rollout.
187
- # Setup/reconfigure resolve the selected binary and persist one validated
188
- # repo/project/team/coms context.
189
- # e.g. just conductor-codex-pilot-setup docs --project af
190
- conductor-codex-pilot-setup team="full" *args:
191
- {{node_ts}} scripts/codex-remote-control.ts setup-pilot --codex-bin "$(command -v codex)" --repo-root "$(pwd -P)" --coms-dir "$HOME/.pi/coms" --team "{{team}}" --timeout 300000 {{args}}
192
-
193
- conductor-codex-pilot-reconfigure team="full" *args:
194
- {{node_ts}} scripts/codex-remote-control.ts reconfigure-pilot --codex-bin "$(command -v codex)" --repo-root "$(pwd -P)" --coms-dir "$HOME/.pi/coms" --team "{{team}}" --timeout 300000 {{args}}
195
-
196
- conductor-codex-pilot-pair:
205
+ _fleet-conductor-codex-pair:
197
206
  {{node_ts}} scripts/codex-remote-control.ts pair
198
207
 
199
- conductor-codex-pilot-start:
208
+ _fleet-conductor-codex-start:
200
209
  {{node_ts}} scripts/codex-remote-control.ts start
201
210
 
202
- conductor-codex-pilot-status:
211
+ _fleet-conductor-codex-status:
203
212
  {{node_ts}} scripts/codex-remote-control.ts status
204
213
 
205
- conductor-codex-pilot-stop:
214
+ _fleet-conductor-codex-stop:
206
215
  {{node_ts}} scripts/codex-remote-control.ts stop
207
216
 
208
- conductor-codex-pilot-recover:
217
+ _fleet-conductor-codex-recover:
209
218
  {{node_ts}} scripts/codex-remote-control.ts recover --confirm operator-confirmed
210
219
 
211
- conductor-codex-pilot-uninstall:
220
+ _fleet-conductor-codex-uninstall:
212
221
  {{node_ts}} scripts/codex-remote-control.ts uninstall --confirm operator-confirmed
213
222
 
214
- # Legacy pilot live aliases use the same verified implementation. The root pane
215
- # is the lifecycle helper's foreground control pane, never a daemon command.
216
- # e.g. just conductor-codex-pilot docs --project af
217
- conductor-codex-pilot team="full" *args:
223
+ # Codex conductor + team; systemd owns the remote-control daemon:
224
+ # just fleet conductor codex docs --project af
225
+ _fleet-conductor-codex team="full" *args:
218
226
  {{node_ts}} scripts/team-up.ts --team {{team}} --conductor codex {{args}}
219
227
 
220
- # Legacy pilot dry-run alias.
221
- # e.g. just conductor-codex-pilot-dry docs --project af
222
- conductor-codex-pilot-dry team="full" *args:
228
+ _fleet-conductor-codex-dry team="full" *args:
223
229
  {{node_ts}} scripts/team-up.ts --team {{team}} --conductor codex --dry-run {{args}}
224
230
 
225
- # Snapshot a RUNNING team's session refs to ~/.pi/team-snapshots/<team>.json
226
- # (team keeps running — take one proactively so a crash is resumable).
227
- # A team launched with --project must snapshot with the same --project.
228
- # e.g. just team-snapshot review --project af
229
- team-snapshot team="full" *args:
231
+ # Save session refs while the team keeps running:
232
+ # just fleet snapshot review --project af
233
+ _fleet-team-snapshot team="full" *args:
230
234
  {{node_ts}} scripts/team-snapshot.ts snapshot {{team}} {{args}}
231
235
 
232
- # Snapshot, then close the team workspace cleanly (peers get SIGTERM).
233
- # e.g. just team-down review --project af
234
- team-down team="full" *args:
236
+ # Snapshot and close cleanly:
237
+ # just fleet down review --project af
238
+ _fleet-team-down team="full" *args:
235
239
  {{node_ts}} scripts/team-snapshot.ts down {{team}} {{args}}
236
240
 
237
- # Rebuild a team from its snapshot — each pi peer resumes its previous
238
- # conversation (`pi --session <ref>`); peers whose ref is gone start fresh.
239
- # e.g. just team-resume review --project af
240
- team-resume team="full" *args:
241
+ # Rebuild from snapshot; missing session refs start fresh:
242
+ # just fleet resume review --project af
243
+ _fleet-team-resume team="full" *args:
241
244
  {{node_ts}} scripts/team-snapshot.ts resume {{team}} {{args}}
242
-
243
- # ---------------------------------------------------------------- coms (Pi-to-Pi messaging)
244
-
245
- # Safe coms: a FULL pi (all auto-discovered local .pi/extensions/ + global extensions and
246
- # commands) plus damage-control-continue guardrails and the coms peer layer, under a chosen name.
247
- # Unlike `just hub`, this does NOT pass --no-extensions, so every local-only extension (MCP
248
- # bridges like chrome-devtools-mcp, project-specific extensions, …) loads into THIS process.
249
- # Use it as the agent-hub dispatcher/orchestrator peer that needs those local tools: spawned
250
- # specialists run --no-extensions, so the tools stay scoped here and never leak into subagents.
251
- # The required `name` becomes this peer's coms identity (--name), so it is discoverable
252
- # under exactly that name to other coms peers in the project pool.
253
- # e.g. just safe-coms orchestrator --project proj
254
- safe-coms name *args:
255
- pi -e .pi/harnesses/damage-control-continue/index.ts -e .pi/harnesses/coms/index.ts --name {{name}} {{args}}
256
245
  # <<< agent-fleet:harnesses <<<