@chankov/agent-fleet 0.0.8 → 0.0.9

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 (340) hide show
  1. package/.pi/agents/model-profiles.yaml +9 -2
  2. package/.pi/agents/peers.yaml +12 -16
  3. package/.pi/agents/teams.yaml +4 -2
  4. package/.pi/harnesses/agent-hub/README.md +20 -5
  5. package/.pi/harnesses/agent-hub/footer.ts +4 -2
  6. package/.pi/harnesses/agent-hub/index.ts +104 -11
  7. package/.pi/harnesses/agent-hub/package.json +1 -1
  8. package/.pi/harnesses/agent-hub/version.ts +25 -1
  9. package/.pi/harnesses/coms/README.md +8 -1
  10. package/.pi/harnesses/coms/package.json +1 -1
  11. package/.pi/harnesses/coms/version.ts +25 -1
  12. package/.pi/harnesses/damage-control-continue/README.md +8 -1
  13. package/.pi/harnesses/damage-control-continue/package.json +1 -1
  14. package/.pi/harnesses/damage-control-continue/version.ts +25 -1
  15. package/.pi/harnesses/lib/herdr-client.ts +10 -1
  16. package/.pi/harnesses/lib/spawned-peers.js +190 -0
  17. package/.versions/0.0.9/.claude/commands/build.md +44 -0
  18. package/.versions/0.0.9/.claude/commands/code-simplify.md +22 -0
  19. package/.versions/0.0.9/.claude/commands/design-agent.md +14 -0
  20. package/.versions/0.0.9/.claude/commands/doctor-agent-fleet.md +17 -0
  21. package/.versions/0.0.9/.claude/commands/orchestrate.md +112 -0
  22. package/.versions/0.0.9/.claude/commands/plan.md +16 -0
  23. package/.versions/0.0.9/.claude/commands/prime.md +22 -0
  24. package/.versions/0.0.9/.claude/commands/review.md +16 -0
  25. package/.versions/0.0.9/.claude/commands/set-hermes-telegram.md +15 -0
  26. package/.versions/0.0.9/.claude/commands/set-hermes-watchdog.md +6 -0
  27. package/.versions/0.0.9/.claude/commands/setup-agent-fleet.md +25 -0
  28. package/.versions/0.0.9/.claude/commands/ship.md +72 -0
  29. package/.versions/0.0.9/.claude/commands/spec.md +15 -0
  30. package/.versions/0.0.9/.claude/commands/test.md +19 -0
  31. package/.versions/0.0.9/.claude/commands/webperf.md +32 -0
  32. package/.versions/0.0.9/.claude/orchestrate-teams.yaml +24 -0
  33. package/.versions/0.0.9/.opencode/commands/af-build.md +17 -0
  34. package/.versions/0.0.9/.opencode/commands/af-code-simplify.md +16 -0
  35. package/.versions/0.0.9/.opencode/commands/af-compound.md +16 -0
  36. package/.versions/0.0.9/.opencode/commands/af-design-agent.md +15 -0
  37. package/.versions/0.0.9/.opencode/commands/af-doctor-agent-fleet.md +17 -0
  38. package/.versions/0.0.9/.opencode/commands/af-orchestrate.md +112 -0
  39. package/.versions/0.0.9/.opencode/commands/af-plan.md +16 -0
  40. package/.versions/0.0.9/.opencode/commands/af-prime.md +22 -0
  41. package/.versions/0.0.9/.opencode/commands/af-review.md +15 -0
  42. package/.versions/0.0.9/.opencode/commands/af-set-hermes-telegram.md +15 -0
  43. package/.versions/0.0.9/.opencode/commands/af-set-hermes-watchdog.md +6 -0
  44. package/.versions/0.0.9/.opencode/commands/af-setup-agent-fleet.md +15 -0
  45. package/.versions/0.0.9/.opencode/commands/af-ship.md +16 -0
  46. package/.versions/0.0.9/.opencode/commands/af-spec.md +16 -0
  47. package/.versions/0.0.9/.opencode/commands/af-test.md +21 -0
  48. package/.versions/0.0.9/.opencode/commands/af-webperf.md +32 -0
  49. package/.versions/0.0.9/.opencode/orchestrate-teams.yaml +24 -0
  50. package/.versions/0.0.9/.pi/agents/dispatch-policy.yaml +32 -0
  51. package/.versions/0.0.9/.pi/agents/model-profiles.yaml +27 -0
  52. package/.versions/0.0.9/.pi/agents/peers.yaml +142 -0
  53. package/.versions/0.0.9/.pi/agents/teams.yaml +41 -0
  54. package/.versions/0.0.9/.pi/damage-control-rules.yaml +297 -0
  55. package/.versions/0.0.9/.pi/extensions/agent-fleet-update-check/README.md +58 -0
  56. package/.versions/0.0.9/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
  57. package/.versions/0.0.9/.pi/extensions/agent-fleet-update-check/package.json +6 -0
  58. package/.versions/0.0.9/.pi/extensions/btw/README.md +118 -0
  59. package/.versions/0.0.9/.pi/extensions/btw/index.ts +917 -0
  60. package/.versions/0.0.9/.pi/extensions/btw/package.json +6 -0
  61. package/.versions/0.0.9/.pi/extensions/btw/state.js +179 -0
  62. package/.versions/0.0.9/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
  63. package/.versions/0.0.9/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
  64. package/.versions/0.0.9/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
  65. package/.versions/0.0.9/.pi/extensions/compact-and-continue/README.md +42 -0
  66. package/.versions/0.0.9/.pi/extensions/compact-and-continue/index.ts +120 -0
  67. package/.versions/0.0.9/.pi/extensions/compact-and-continue/package.json +6 -0
  68. package/.versions/0.0.9/.pi/extensions/mcp-bridge/README.md +46 -0
  69. package/.versions/0.0.9/.pi/extensions/mcp-bridge/index.ts +206 -0
  70. package/.versions/0.0.9/.pi/extensions/mcp-bridge/package.json +6 -0
  71. package/.versions/0.0.9/.pi/extensions/package-lock.json +1143 -0
  72. package/.versions/0.0.9/.pi/extensions/package.json +9 -0
  73. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/README.md +201 -0
  74. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/config.ts +198 -0
  75. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
  76. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/index.ts +248 -0
  77. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/package.json +6 -0
  78. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/providers.ts +214 -0
  79. package/.versions/0.0.9/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
  80. package/.versions/0.0.9/.pi/harnesses/agent-hub/README.md +872 -0
  81. package/.versions/0.0.9/.pi/harnesses/agent-hub/access-approval.ts +135 -0
  82. package/.versions/0.0.9/.pi/harnesses/agent-hub/artifacts.js +146 -0
  83. package/.versions/0.0.9/.pi/harnesses/agent-hub/assertion-ledger.js +58 -0
  84. package/.versions/0.0.9/.pi/harnesses/agent-hub/backend-policy.js +153 -0
  85. package/.versions/0.0.9/.pi/harnesses/agent-hub/context-window.js +106 -0
  86. package/.versions/0.0.9/.pi/harnesses/agent-hub/delegate.ts +435 -0
  87. package/.versions/0.0.9/.pi/harnesses/agent-hub/drift-watchdog.js +211 -0
  88. package/.versions/0.0.9/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
  89. package/.versions/0.0.9/.pi/harnesses/agent-hub/footer.ts +31 -0
  90. package/.versions/0.0.9/.pi/harnesses/agent-hub/helpers.ts +248 -0
  91. package/.versions/0.0.9/.pi/harnesses/agent-hub/index.ts +8702 -0
  92. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
  93. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
  94. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
  95. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
  96. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
  97. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
  98. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
  99. package/.versions/0.0.9/.pi/harnesses/agent-hub/monitor-session-bridge.ts +257 -0
  100. package/.versions/0.0.9/.pi/harnesses/agent-hub/package.json +7 -0
  101. package/.versions/0.0.9/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
  102. package/.versions/0.0.9/.pi/harnesses/agent-hub/research-retention.js +34 -0
  103. package/.versions/0.0.9/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
  104. package/.versions/0.0.9/.pi/harnesses/agent-hub/return-contract.js +293 -0
  105. package/.versions/0.0.9/.pi/harnesses/agent-hub/return-extract.js +75 -0
  106. package/.versions/0.0.9/.pi/harnesses/agent-hub/run-budget.js +181 -0
  107. package/.versions/0.0.9/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
  108. package/.versions/0.0.9/.pi/harnesses/agent-hub/scope-gate.js +103 -0
  109. package/.versions/0.0.9/.pi/harnesses/agent-hub/session-health.js +110 -0
  110. package/.versions/0.0.9/.pi/harnesses/agent-hub/spawn.ts +354 -0
  111. package/.versions/0.0.9/.pi/harnesses/agent-hub/version.ts +42 -0
  112. package/.versions/0.0.9/.pi/harnesses/ask-user-remote/README.md +19 -0
  113. package/.versions/0.0.9/.pi/harnesses/ask-user-remote/index.ts +321 -0
  114. package/.versions/0.0.9/.pi/harnesses/ask-user-remote/race-core.js +106 -0
  115. package/.versions/0.0.9/.pi/harnesses/coms/README.md +100 -0
  116. package/.versions/0.0.9/.pi/harnesses/coms/index.ts +1767 -0
  117. package/.versions/0.0.9/.pi/harnesses/coms/package.json +7 -0
  118. package/.versions/0.0.9/.pi/harnesses/coms/version.ts +42 -0
  119. package/.versions/0.0.9/.pi/harnesses/damage-control-continue/README.md +124 -0
  120. package/.versions/0.0.9/.pi/harnesses/damage-control-continue/index.ts +536 -0
  121. package/.versions/0.0.9/.pi/harnesses/damage-control-continue/package.json +7 -0
  122. package/.versions/0.0.9/.pi/harnesses/damage-control-continue/version.ts +42 -0
  123. package/.versions/0.0.9/.pi/harnesses/lib/coms-registry-entry.ts +94 -0
  124. package/.versions/0.0.9/.pi/harnesses/lib/damage-control-shared.ts +197 -0
  125. package/.versions/0.0.9/.pi/harnesses/lib/herdr-client.ts +472 -0
  126. package/.versions/0.0.9/.pi/harnesses/lib/herdr-presence.ts +399 -0
  127. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
  128. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
  129. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
  130. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
  131. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
  132. package/.versions/0.0.9/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
  133. package/.versions/0.0.9/.pi/harnesses/lib/spawned-peers.js +190 -0
  134. package/.versions/0.0.9/.pi/harnesses/package-lock.json +35 -0
  135. package/.versions/0.0.9/.pi/harnesses/package.json +9 -0
  136. package/.versions/0.0.9/.pi/prompts/af-build.md +24 -0
  137. package/.versions/0.0.9/.pi/prompts/af-code-simplify.md +22 -0
  138. package/.versions/0.0.9/.pi/prompts/af-doctor-agent-fleet.md +15 -0
  139. package/.versions/0.0.9/.pi/prompts/af-plan.md +16 -0
  140. package/.versions/0.0.9/.pi/prompts/af-review.md +16 -0
  141. package/.versions/0.0.9/.pi/prompts/af-set-hermes-telegram.md +15 -0
  142. package/.versions/0.0.9/.pi/prompts/af-set-hermes-watchdog.md +6 -0
  143. package/.versions/0.0.9/.pi/prompts/af-setup-agent-fleet.md +27 -0
  144. package/.versions/0.0.9/.pi/prompts/af-ship.md +17 -0
  145. package/.versions/0.0.9/.pi/prompts/af-spec.md +15 -0
  146. package/.versions/0.0.9/.pi/prompts/af-test.md +19 -0
  147. package/.versions/0.0.9/.pi/skills/bowser/SKILL.md +145 -0
  148. package/.versions/0.0.9/.version +1 -0
  149. package/.versions/0.0.9/agents/architect.md +24 -0
  150. package/.versions/0.0.9/agents/bowser.md +27 -0
  151. package/.versions/0.0.9/agents/builder.md +54 -0
  152. package/.versions/0.0.9/agents/code-reviewer.md +204 -0
  153. package/.versions/0.0.9/agents/deep-researcher.md +32 -0
  154. package/.versions/0.0.9/agents/documenter.md +18 -0
  155. package/.versions/0.0.9/agents/orchestrator.md +66 -0
  156. package/.versions/0.0.9/agents/plan-reviewer.md +62 -0
  157. package/.versions/0.0.9/agents/planner.md +70 -0
  158. package/.versions/0.0.9/agents/releaser.md +24 -0
  159. package/.versions/0.0.9/agents/researcher.md +28 -0
  160. package/.versions/0.0.9/agents/security-auditor.md +167 -0
  161. package/.versions/0.0.9/agents/test-engineer.md +153 -0
  162. package/.versions/0.0.9/agents/web-debugger.md +43 -0
  163. package/.versions/0.0.9/agents/web-performance-auditor.md +193 -0
  164. package/.versions/0.0.9/codex/CONDUCTOR.md +148 -0
  165. package/.versions/0.0.9/docs/ARCHITECTURE.md +262 -0
  166. package/.versions/0.0.9/docs/agent-fleet-setup.md +366 -0
  167. package/.versions/0.0.9/docs/claude-code-coms-bridge.md +109 -0
  168. package/.versions/0.0.9/docs/codex-remote-conductor.md +170 -0
  169. package/.versions/0.0.9/docs/coms-hermes-bridge.md +189 -0
  170. package/.versions/0.0.9/docs/getting-started.md +231 -0
  171. package/.versions/0.0.9/docs/npm-install.md +337 -0
  172. package/.versions/0.0.9/docs/opencode-setup.md +249 -0
  173. package/.versions/0.0.9/docs/pi-extensions.md +356 -0
  174. package/.versions/0.0.9/docs/pi-setup.md +476 -0
  175. package/.versions/0.0.9/docs/skill-anatomy.md +150 -0
  176. package/.versions/0.0.9/hermes/README.md +347 -0
  177. package/.versions/0.0.9/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
  178. package/.versions/0.0.9/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
  179. package/.versions/0.0.9/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
  180. package/.versions/0.0.9/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
  181. package/.versions/0.0.9/hermes/gates/gate-o-capability.md +8 -0
  182. package/.versions/0.0.9/hermes/gates/gate-o-validator-fixtures.json +1 -0
  183. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +770 -0
  184. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
  185. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
  186. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
  187. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
  188. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
  189. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
  190. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
  191. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
  192. package/.versions/0.0.9/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
  193. package/.versions/0.0.9/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
  194. package/.versions/0.0.9/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
  195. package/.versions/0.0.9/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
  196. package/.versions/0.0.9/hermes/skills/hub-conductor/SKILL.md +84 -0
  197. package/.versions/0.0.9/hermes/skills/hub-liaison/SKILL.md +84 -0
  198. package/.versions/0.0.9/hermes/skills/hub-watchdog/SKILL.md +76 -0
  199. package/.versions/0.0.9/hermes/skills/hub-watchdog/manifest.json +1 -0
  200. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
  201. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
  202. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
  203. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
  204. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
  205. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
  206. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
  207. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
  208. package/.versions/0.0.9/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
  209. package/.versions/0.0.9/hermes/watchdog-tests/__init__.py +0 -0
  210. package/.versions/0.0.9/hooks/SIMPLIFY-IGNORE.md +90 -0
  211. package/.versions/0.0.9/hooks/coms-stop-hook.mjs +84 -0
  212. package/.versions/0.0.9/hooks/hooks.json +14 -0
  213. package/.versions/0.0.9/hooks/session-start.sh +74 -0
  214. package/.versions/0.0.9/hooks/simplify-ignore.sh +302 -0
  215. package/.versions/0.0.9/justfile +254 -0
  216. package/.versions/0.0.9/references/accessibility-checklist.md +160 -0
  217. package/.versions/0.0.9/references/definition-of-done.md +67 -0
  218. package/.versions/0.0.9/references/fleet-coordination-patterns.md +151 -0
  219. package/.versions/0.0.9/references/observability-checklist.md +91 -0
  220. package/.versions/0.0.9/references/orchestration-patterns.md +370 -0
  221. package/.versions/0.0.9/references/performance-checklist.md +153 -0
  222. package/.versions/0.0.9/references/prompting-patterns.md +380 -0
  223. package/.versions/0.0.9/references/security-checklist.md +179 -0
  224. package/.versions/0.0.9/references/testing-patterns.md +236 -0
  225. package/.versions/0.0.9/scripts/codex-conductor.ts +41 -0
  226. package/.versions/0.0.9/scripts/codex-remote-control.ts +167 -0
  227. package/.versions/0.0.9/scripts/coms-claude-bridge.ts +401 -0
  228. package/.versions/0.0.9/scripts/coms-cli.ts +484 -0
  229. package/.versions/0.0.9/scripts/coms-hermes-bridge.ts +413 -0
  230. package/.versions/0.0.9/scripts/fleet.ts +168 -0
  231. package/.versions/0.0.9/scripts/hermes-monitor-capability-runner.ts +25 -0
  232. package/.versions/0.0.9/scripts/hermes-monitor-scenario.ts +474 -0
  233. package/.versions/0.0.9/scripts/hermes-watchdog-capability-probe.ts +45 -0
  234. package/.versions/0.0.9/scripts/install-hermes-plugin.sh +180 -0
  235. package/.versions/0.0.9/scripts/lib/claude-bridge-core.ts +165 -0
  236. package/.versions/0.0.9/scripts/lib/codex-conductor.ts +88 -0
  237. package/.versions/0.0.9/scripts/lib/codex-remote-control.ts +480 -0
  238. package/.versions/0.0.9/scripts/lib/coms-envelope.ts +582 -0
  239. package/.versions/0.0.9/scripts/lib/fake-herdr-server.ts +88 -0
  240. package/.versions/0.0.9/scripts/lib/fleet-command.ts +111 -0
  241. package/.versions/0.0.9/scripts/lib/herdr-layout.ts +281 -0
  242. package/.versions/0.0.9/scripts/lib/hermes-bridge-core.ts +241 -0
  243. package/.versions/0.0.9/scripts/lib/hermes-monitor-events.ts +1 -0
  244. package/.versions/0.0.9/scripts/lib/hermes-monitor-herdr.ts +2 -0
  245. package/.versions/0.0.9/scripts/lib/hermes-monitor-model.ts +3 -0
  246. package/.versions/0.0.9/scripts/lib/hermes-monitor-registry.ts +2 -0
  247. package/.versions/0.0.9/scripts/lib/hermes-monitor-socket.ts +2 -0
  248. package/.versions/0.0.9/scripts/lib/hermes-monitor-store.ts +2 -0
  249. package/.versions/0.0.9/scripts/lib/monitor-env.ts +120 -0
  250. package/.versions/0.0.9/scripts/lib/peer-launch.ts +314 -0
  251. package/.versions/0.0.9/scripts/lib/persona-banner.ts +62 -0
  252. package/.versions/0.0.9/scripts/lib/spawn-stagger.ts +101 -0
  253. package/.versions/0.0.9/scripts/lib/team-project.ts +193 -0
  254. package/.versions/0.0.9/scripts/lib/team-snapshot.ts +147 -0
  255. package/.versions/0.0.9/scripts/peer-banner.ts +40 -0
  256. package/.versions/0.0.9/scripts/peer-launch.ts +259 -0
  257. package/.versions/0.0.9/scripts/team-snapshot.ts +237 -0
  258. package/.versions/0.0.9/scripts/team-up.ts +360 -0
  259. package/.versions/0.0.9/skills/_internal/grilling.md +11 -0
  260. package/.versions/0.0.9/skills/browser-testing-with-devtools/SKILL.md +352 -0
  261. package/.versions/0.0.9/skills/code-review-and-quality/SKILL.md +381 -0
  262. package/.versions/0.0.9/skills/compound-learning/SKILL.md +137 -0
  263. package/.versions/0.0.9/skills/context-engineering/SKILL.md +291 -0
  264. package/.versions/0.0.9/skills/deprecation-and-migration/SKILL.md +206 -0
  265. package/.versions/0.0.9/skills/designing-agents/SKILL.md +394 -0
  266. package/.versions/0.0.9/skills/designing-agents/pi-harness-authoring.md +222 -0
  267. package/.versions/0.0.9/skills/frontend-ui-engineering/SKILL.md +328 -0
  268. package/.versions/0.0.9/skills/git-workflow-and-versioning/SKILL.md +316 -0
  269. package/.versions/0.0.9/skills/guided-workspace-setup/SKILL.md +544 -0
  270. package/.versions/0.0.9/skills/guided-workspace-setup/companion-manifest.json +38 -0
  271. package/.versions/0.0.9/skills/idea-refine/SKILL.md +182 -0
  272. package/.versions/0.0.9/skills/idea-refine/examples.md +238 -0
  273. package/.versions/0.0.9/skills/idea-refine/frameworks.md +99 -0
  274. package/.versions/0.0.9/skills/idea-refine/refinement-criteria.md +113 -0
  275. package/.versions/0.0.9/skills/idea-refine/scripts/idea-refine.sh +15 -0
  276. package/.versions/0.0.9/skills/incremental-implementation/SKILL.md +287 -0
  277. package/.versions/0.0.9/skills/interview-me/SKILL.md +226 -0
  278. package/.versions/0.0.9/skills/orchestration-verification/SKILL.md +181 -0
  279. package/.versions/0.0.9/skills/peer-coms/SKILL.md +90 -0
  280. package/.versions/0.0.9/skills/performance-optimization/SKILL.md +350 -0
  281. package/.versions/0.0.9/skills/planning-and-task-breakdown/SKILL.md +236 -0
  282. package/.versions/0.0.9/skills/security-and-hardening/SKILL.md +461 -0
  283. package/.versions/0.0.9/skills/spec-driven-development/SKILL.md +245 -0
  284. package/.versions/0.0.9/skills/using-agent-skills/SKILL.md +199 -0
  285. package/.versions/0.0.9/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
  286. package/.versions/0.0.9/vendor/agent-skills-upstream/LICENSE +21 -0
  287. package/.versions/0.0.9/vendor/agent-skills-upstream/README.md +11 -0
  288. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
  289. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
  290. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
  291. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
  292. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
  293. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
  294. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
  295. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
  296. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
  297. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
  298. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
  299. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
  300. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
  301. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
  302. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
  303. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
  304. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
  305. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
  306. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
  307. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
  308. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
  309. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
  310. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
  311. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
  312. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
  313. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
  314. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
  315. package/.versions/0.0.9/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
  316. package/CHANGELOG.md +38 -0
  317. package/agents/architect.md +1 -0
  318. package/agents/bowser.md +1 -0
  319. package/agents/builder.md +1 -0
  320. package/agents/code-reviewer.md +4 -5
  321. package/agents/deep-researcher.md +2 -1
  322. package/agents/orchestrator.md +1 -0
  323. package/agents/plan-reviewer.md +3 -1
  324. package/agents/planner.md +3 -2
  325. package/agents/security-auditor.md +1 -0
  326. package/agents/test-engineer.md +3 -1
  327. package/agents/web-debugger.md +1 -0
  328. package/agents/web-performance-auditor.md +1 -0
  329. package/docs/ARCHITECTURE.md +1 -1
  330. package/docs/pi-extensions.md +66 -3
  331. package/justfile +10 -1
  332. package/package.json +2 -2
  333. package/scripts/fleet.ts +22 -3
  334. package/scripts/lib/fleet-command.ts +5 -3
  335. package/scripts/lib/herdr-layout.ts +18 -0
  336. package/scripts/lib/peer-launch.ts +314 -0
  337. package/scripts/lib/team-project.ts +3 -1
  338. package/scripts/peer-launch.ts +259 -0
  339. package/skills/guided-workspace-setup/companion-manifest.json +2 -0
  340. package/.pi/harnesses/agent-hub/spawned-peers.js +0 -74
@@ -0,0 +1,191 @@
1
+ ---
2
+ name: using-agent-skills
3
+ description: Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.
4
+ ---
5
+
6
+ # Using Agent Skills
7
+
8
+ ## Overview
9
+
10
+ Agent Skills is a collection of engineering workflow skills organized by development phase. Each skill encodes a specific process that senior engineers follow. This meta-skill helps you discover and apply the right skill for your current task.
11
+
12
+ ## Skill Discovery
13
+
14
+ When a task arrives, identify the development phase and apply the corresponding skill:
15
+
16
+ ```
17
+ Task arrives
18
+ │
19
+ ├── Don't know what you want yet? ──────→ interview-me
20
+ ├── Have a rough concept, need variants? → idea-refine
21
+ ├── New project/feature/change? ──→ spec-driven-development
22
+ ├── Have a spec, need tasks? ──────→ planning-and-task-breakdown
23
+ ├── Implementing code? ────────────→ incremental-implementation
24
+ │ ├── UI work? ─────────────────→ frontend-ui-engineering
25
+ │ ├── API work? ────────────────→ api-and-interface-design
26
+ │ ├── Need better context? ─────→ context-engineering
27
+ │ ├── Need doc-verified code? ───→ source-driven-development
28
+ │ └── Stakes high / unfamiliar code? ──→ doubt-driven-development
29
+ ├── Writing/running tests? ────────→ test-driven-development
30
+ │ └── Browser-based? ───────────→ browser-testing-with-devtools
31
+ ├── Something broke? ──────────────→ debugging-and-error-recovery
32
+ ├── Reviewing code? ───────────────→ code-review-and-quality
33
+ │ ├── Too complex? ─────────────→ code-simplification
34
+ │ ├── Security concerns? ───────→ security-and-hardening
35
+ │ └── Performance concerns? ────→ performance-optimization
36
+ ├── Committing/branching? ─────────→ git-workflow-and-versioning
37
+ ├── CI/CD pipeline work? ──────────→ ci-cd-and-automation
38
+ ├── Deprecating/migrating? ────────→ deprecation-and-migration
39
+ ├── Writing docs/ADRs? ───────────→ documentation-and-adrs
40
+ ├── Adding logs/metrics/alerts? ───→ observability-and-instrumentation
41
+ └── Deploying/launching? ─────────→ shipping-and-launch
42
+ ```
43
+
44
+ ## Core Operating Behaviors
45
+
46
+ These behaviors apply at all times, across all skills. They are non-negotiable.
47
+
48
+ ### 1. Surface Assumptions
49
+
50
+ Before implementing anything non-trivial, explicitly state your assumptions:
51
+
52
+ ```
53
+ ASSUMPTIONS I'M MAKING:
54
+ 1. [assumption about requirements]
55
+ 2. [assumption about architecture]
56
+ 3. [assumption about scope]
57
+ → Correct me now or I'll proceed with these.
58
+ ```
59
+
60
+ Don't silently fill in ambiguous requirements. The most common failure mode is making wrong assumptions and running with them unchecked. Surface uncertainty early — it's cheaper than rework.
61
+
62
+ ### 2. Manage Confusion Actively
63
+
64
+ When you encounter inconsistencies, conflicting requirements, or unclear specifications:
65
+
66
+ 1. **STOP.** Do not proceed with a guess.
67
+ 2. Name the specific confusion.
68
+ 3. Present the tradeoff or ask the clarifying question.
69
+ 4. Wait for resolution before continuing.
70
+
71
+ **Bad:** Silently picking one interpretation and hoping it's right.
72
+ **Good:** "I see X in the spec but Y in the existing code. Which takes precedence?"
73
+
74
+ ### 3. Push Back When Warranted
75
+
76
+ You are not a yes-machine. When an approach has clear problems:
77
+
78
+ - Point out the issue directly
79
+ - Explain the concrete downside (quantify when possible — "this adds ~200ms latency" not "this might be slower")
80
+ - Propose an alternative
81
+ - Accept the human's decision if they override with full information
82
+
83
+ Sycophancy is a failure mode. "Of course!" followed by implementing a bad idea helps no one. Honest technical disagreement is more valuable than false agreement.
84
+
85
+ ### 4. Enforce Simplicity
86
+
87
+ Your natural tendency is to overcomplicate. Actively resist it.
88
+
89
+ Before finishing any implementation, ask:
90
+ - Can this be done in fewer lines?
91
+ - Are these abstractions earning their complexity?
92
+ - Would a staff engineer look at this and say "why didn't you just..."?
93
+
94
+ If you build 1000 lines and 100 would suffice, you have failed. Prefer the boring, obvious solution. Cleverness is expensive.
95
+
96
+ ### 5. Maintain Scope Discipline
97
+
98
+ Touch only what you're asked to touch.
99
+
100
+ Do NOT:
101
+ - Remove comments you don't understand
102
+ - "Clean up" code orthogonal to the task
103
+ - Refactor adjacent systems as a side effect
104
+ - Delete code that seems unused without explicit approval
105
+ - Add features not in the spec because they "seem useful"
106
+
107
+ Your job is surgical precision, not unsolicited renovation.
108
+
109
+ ### 6. Verify, Don't Assume
110
+
111
+ Every skill includes a verification step. A task is not complete until verification passes. "Seems right" is never sufficient — there must be evidence (passing tests, build output, runtime data).
112
+
113
+ Per-skill verification is the local check. The project-wide bar that applies to *every* change, regardless of which skill is active, is the Definition of Done: tests pass, no regressions, behavior verified at runtime, docs updated. See `references/definition-of-done.md`. It complements each task's acceptance criteria rather than replacing them.
114
+
115
+ ## Failure Modes to Avoid
116
+
117
+ These are the subtle errors that look like productivity but create problems:
118
+
119
+ 1. Making wrong assumptions without checking
120
+ 2. Not managing your own confusion — plowing ahead when lost
121
+ 3. Not surfacing inconsistencies you notice
122
+ 4. Not presenting tradeoffs on non-obvious decisions
123
+ 5. Being sycophantic ("Of course!") to approaches with clear problems
124
+ 6. Overcomplicating code and APIs
125
+ 7. Modifying code or comments orthogonal to the task
126
+ 8. Removing things you don't fully understand
127
+ 9. Building without a spec because "it's obvious"
128
+ 10. Skipping verification because "it looks right"
129
+
130
+ ## Skill Rules
131
+
132
+ 1. **Check for an applicable skill before starting work.** Skills encode processes that prevent common mistakes.
133
+
134
+ 2. **Skills are workflows, not suggestions.** Follow the steps in order. Don't skip verification steps.
135
+
136
+ 3. **Multiple skills can apply.** A feature implementation might involve `idea-refine` → `spec-driven-development` → `planning-and-task-breakdown` → `incremental-implementation` → `test-driven-development` → `code-review-and-quality` → `code-simplification` → `shipping-and-launch` in sequence.
137
+
138
+ 4. **When in doubt, start with a spec.** If the task is non-trivial and there's no spec, begin with `spec-driven-development`.
139
+
140
+ ## Lifecycle Sequence
141
+
142
+ For a complete feature, the typical skill sequence is:
143
+
144
+ ```
145
+ 1. interview-me → Extract what the user actually wants
146
+ 2. idea-refine → Refine vague ideas
147
+ 3. spec-driven-development → Define what we're building
148
+ 4. planning-and-task-breakdown → Break into verifiable chunks
149
+ 5. context-engineering → Load the right context
150
+ 6. source-driven-development → Verify against official docs
151
+ 7. incremental-implementation → Build slice by slice
152
+ 8. observability-and-instrumentation → Instrument as you build (runs parallel with 7-9, not after)
153
+ 9. doubt-driven-development → Cross-examine non-trivial decisions in-flight
154
+ 10. test-driven-development → Prove each slice works
155
+ 11. code-review-and-quality → Review before merge
156
+ 12. code-simplification → Reduce unnecessary complexity while preserving behavior
157
+ 13. git-workflow-and-versioning → Clean commit history
158
+ 14. documentation-and-adrs → Document decisions
159
+ 15. deprecation-and-migration → Retire old systems and move users safely when needed
160
+ 16. shipping-and-launch → Deploy safely
161
+ ```
162
+
163
+ Not every task needs every skill. A bug fix might only need: `debugging-and-error-recovery` → `test-driven-development` → `code-review-and-quality`.
164
+
165
+ ## Quick Reference
166
+
167
+ | Phase | Skill | One-Line Summary |
168
+ |-------|-------|-----------------|
169
+ | Define | interview-me | Surface what the user actually wants before any plan, spec, or code exists |
170
+ | Define | idea-refine | Refine ideas through structured divergent and convergent thinking |
171
+ | Define | spec-driven-development | Requirements and acceptance criteria before code |
172
+ | Plan | planning-and-task-breakdown | Decompose into small, verifiable tasks |
173
+ | Build | incremental-implementation | Thin vertical slices, test each before expanding |
174
+ | Build | source-driven-development | Verify against official docs before implementing |
175
+ | Build | doubt-driven-development | Adversarial fresh-context review of every non-trivial decision |
176
+ | Build | context-engineering | Right context at the right time |
177
+ | Build | frontend-ui-engineering | Production-quality UI with accessibility |
178
+ | Build | api-and-interface-design | Stable interfaces with clear contracts |
179
+ | Verify | test-driven-development | Failing test first, then make it pass |
180
+ | Verify | browser-testing-with-devtools | Chrome DevTools MCP for runtime verification |
181
+ | Verify | debugging-and-error-recovery | Reproduce → localize → fix → guard |
182
+ | Review | code-review-and-quality | Five-axis review with quality gates |
183
+ | Review | code-simplification | Preserve behavior while reducing unnecessary complexity |
184
+ | Review | security-and-hardening | OWASP prevention, input validation, least privilege |
185
+ | Review | performance-optimization | Measure first, optimize only what matters |
186
+ | Ship | git-workflow-and-versioning | Atomic commits, clean history |
187
+ | Ship | ci-cd-and-automation | Automated quality gates on every change |
188
+ | Ship | deprecation-and-migration | Remove old systems and migrate users safely |
189
+ | Ship | documentation-and-adrs | Document the why, not just the what |
190
+ | Ship | observability-and-instrumentation | Structured logs, RED metrics, traces, symptom-based alerts |
191
+ | Ship | shipping-and-launch | Pre-launch checklist, monitoring, rollback plan |
package/CHANGELOG.md CHANGED
@@ -1,5 +1,43 @@
1
1
  # Agent Fleet changelog
2
2
 
3
+ ## 0.0.9
4
+
5
+ ### Patch Changes
6
+
7
+ - 5a3fa84: `just fleet peer <name>` now launches the peer in a Herdr pane of its own, and can launch any kind of peer — including Claude Code.
8
+
9
+ **Behavior change:** `just fleet peer <name>` used to turn the _calling terminal_ into a pi peer. It now opens a pane instead. Pass `--here` for the old behavior; the command it runs there is byte-identical to before.
10
+
11
+ Launching a Claude Code peer previously meant declaring it in `.pi/agents/peers.yaml` and running `just fleet team <preset>`, which builds a whole workspace. There was no way to say "give me one more agent, next to what I already have".
12
+
13
+ - The **name decides the shape**: a name declared in `peers.yaml` keeps its `runner`/`model`/`extensions`/`env_file`; a name matching `agents/<name>.md` becomes that guarded persona peer; anything else is the identity-only Fleet Core peer this command always launched. `--runner claude-code` needs no manifest entry at all. Note the second rule also changes meaning for existing invocations — `just fleet peer architect` is now the architect persona peer, because `agents/architect.md` exists. `--no-persona` forces the plain shape back.
14
+ - **Placement**: inside a Herdr pane it splits _that_ pane (`--direction right|down`); outside Herdr it creates a single-pane workspace labelled `<worktree-tag>-peer-<name>`, refusing to clobber an existing one; `--here` runs it in the calling terminal.
15
+ - New flags: `--runner pi|claude-code`, `--persona`, `--no-persona`, `--model`, `--extensions`, `--direction`, `--here`, `--dry-run`. `--browser` now also works on a persona peer, where it adds `chrome-devtools-mcp`. Raw pi arguments move behind a `--` separator (`just fleet peer architect --here -- --session …`).
16
+ - **Nothing is silently dropped**: a flag that cannot apply to the resolved peer shape is an error, not a no-op — `--all-extensions` on a persona peer, `--persona` on a Claude Code peer, a mistyped flag, or a pi flag that forgot its `--`.
17
+ - A pane launch waits (bounded) for the peer to register in the coms pool and exits non-zero with the pane's last output when it never does — the same "failed, not slow" policy `herdr_spawn_peer` uses.
18
+ - `--dry-run` prints the resolved plan and placement without touching Herdr, and never reads `env_file` values.
19
+
20
+ Pure logic lives in `scripts/lib/peer-launch.ts` under `node --test`; the Herdr wiring is `scripts/peer-launch.ts`, reusing the existing command builder (`peerCommand`) and pane-launch helper so hub spawns, team spawns, and CLI launches stay one behavior.
21
+
22
+ `spawned-peers.js` (pane launch + readiness policy) moves from `.pi/harnesses/agent-hub/` to the shared `.pi/harnesses/lib/`, because the fleet scripts are installed into target projects that may not have selected the `agent-hub` harness. Both new scripts are added to `companion-manifest.json` so guided setup installs and refreshes them with the rest of the runtime closure.
23
+
24
+ - f62cfe0: Fix `herdr_spawn_peer`: it opened panes without ever launching the peer.
25
+
26
+ herdr's `pane.split` takes no `command` — a split always opens a plain shell — and the server silently ignores unknown params. agent-hub passed `command: argv` to it, so every hub-spawned "peer" was an empty shell pane with the right label, the tool reported success, and the readiness wait then timed out on a peer that had never started. `just fleet team` was unaffected because it launches through `layout.apply`, whose pane nodes do carry an argv.
27
+
28
+ - The spawn now splits, waits for the new pane's shell prompt, and types the command line (text and Enter sent separately — bash bracketed paste swallows a newline inside sent text).
29
+ - Spawned peers join **this session's coms project pool** instead of always `default`, which had put them in a pool the hub cannot see.
30
+ - A name declared in `.pi/agents/peers.yaml` keeps its declared `runner:`, `extensions:`, and `env_file:`, so spawning `code-reviewer` produces the peer the fleet defines rather than a plain pi persona.
31
+ - Hub spawns honor the stale-OAuth spawn stagger that team launches already used, so back-to-back spawns cannot lose the credential lock race.
32
+ - `peer_ready: false` now returns the pane's last output and states that the peer failed to start; the orchestrator persona and hub guidance say not to send to it or spawn around it.
33
+ - `paneSplit` no longer advertises a `command` param, and the client test pins `pane.split` to its real wire shape.
34
+
35
+ - c7f42e0: The version shown by every `just fleet` harness now reads `agent fleet v<version>` instead of a bare `v<version>`, so a pi session started outside this project says whose version it is — and `agent fleet` is a clickable OSC 8 terminal hyperlink to the project homepage.
36
+
37
+ The shared status entry registered by `agent-hub`, `coms`, and `damage-control-continue` and the agent-hub footer (`agent fleet v0.0.7 · <model><thinking> · <team>`) both take the label from one `formatVersionLabel()` helper in each harness's local `version.ts`, so the two surfaces cannot drift.
38
+
39
+ The link is terminal-level, not a TUI control: pi has no mouse tracking, so a click hands the URL to the OS opener rather than opening an in-process overlay. Terminals without OSC 8 support render the label as plain text, and pi's `visibleWidth`/`truncateToWidth` strip OSC sequences, so the link costs no footer columns. Set `AGENT_FLEET_NO_LINKS=1` for a plain label on multiplexers that mangle unknown OSC sequences (GNU screen, tmux before 3.4).
40
+
3
41
  ## 0.0.8
4
42
 
5
43
  ### Patch Changes
@@ -3,6 +3,7 @@ name: architect
3
3
  description: System architect — owns design decisions and migration strategy; answers design questions with concrete, justified recommendations.
4
4
  model: openai-codex/gpt-5.6-sol
5
5
  models:
6
+ - github-copilot/claude-opus-5
6
7
  - openai-codex/gpt-5.6-terra
7
8
  - openai-codex/gpt-5.6-luna
8
9
  - ollama/nemotron-3-ultra:cloud
package/agents/bowser.md CHANGED
@@ -4,6 +4,7 @@ description: Headless browser automation agent using Playwright CLI. Use when yo
4
4
  tools: read,bash
5
5
  model: openai-codex/gpt-5.6-luna
6
6
  models:
7
+ - github-copilot/claude-opus-5
7
8
  - openai-codex/gpt-5.6-terra
8
9
  - ollama/minimax-m3:cloud
9
10
  - ollama/nemotron-3-ultra:cloud
package/agents/builder.md CHANGED
@@ -4,6 +4,7 @@ description: Implementation and code generation — lands changes in small verif
4
4
  tools: read,write,edit,bash,grep,find,ls
5
5
  model: openai-codex/gpt-5.6-terra
6
6
  models:
7
+ - github-copilot/claude-opus-5
7
8
  - openai-codex/gpt-5.6-sol
8
9
  - openai-codex/gpt-5.6-luna
9
10
  - openai-codex/gpt-5.3-codex-spark
@@ -2,13 +2,12 @@
2
2
  name: code-reviewer
3
3
  description: Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
4
4
  tools: read,bash,grep,find,ls
5
- model: openai-codex/gpt-5.6-terra
5
+ model: xai/grok-4.5
6
6
  models:
7
- - github-copilot/claude-opus-4.8
7
+ - openai-codex/gpt-5.6-terra
8
+ - github-copilot/claude-opus-5
8
9
  - openai-codex/gpt-5.6-sol
9
- - openai-codex/gpt-5.6-luna
10
- - github-copilot/claude-sonnet-4.6
11
- - github-copilot/claude-haiku-4.5
10
+ - openai-codex/gpt-5.6-luna
12
11
  - ollama/nemotron-3-ultra:cloud
13
12
  - ollama/kimi-k2.7-code:cloud
14
13
  - ollama/glm-5.2:cloud
@@ -3,8 +3,9 @@ name: deep-researcher
3
3
  description: Read-only deep reconnaissance for hard, ambiguous, or high-stakes questions — traces cross-cutting call paths, maps unfamiliar subsystems, and synthesizes findings across many files with file:line citations. Never edits or runs commands.
4
4
  tools: read,grep,find,ls
5
5
  kind: research
6
- model: openai-codex/gpt-5.6-terra
6
+ model: xai/grok-4.5
7
7
  models:
8
+ - openai-codex/gpt-5.6-terra
8
9
  - openai-codex/gpt-5.6-sol
9
10
  - openai-codex/gpt-5.6-luna
10
11
  - ollama/nemotron-3-ultra:cloud
@@ -62,4 +62,5 @@ Peers are long-lived agents in their own panes, not dispatches. They keep their
62
62
  - **`coms_list` is the status source; `herdr_read_pane` is not.** Every entry reports `pane_id` and `status` (`idle` | `working` | `booting`). Check it before you send: `working` means your `coms_send` waits behind the peer's current turn, and `booting` means the peer registered but cannot take work yet. Reading a pane to guess whether an agent is busy is screen-scraping a field you already have — reserve `herdr_read_pane` for unbridged panes and post-mortems, never for polling.
63
63
  - **Give a peer time, not retries.** Put the same budget on both calls: `coms_send(reply_timeout_ms: 1200000, ...)`, then `coms_await(timeout_ms: 1200000, ...)`. The send carries the receiver-side deadline; await controls only your local wait. The bridge waits for a busy pane instead of failing, and deadline exhaustion returns `pending` so you can await/get again without re-queueing the work.
64
64
  - **Spawn a peer only immediately before the first message to it.** `herdr_spawn_peer` starts a *reusable* peer that boots idle and waits for `coms_send`; it does not receive your task by being spawned. Spawn it, wait for `peer_ready`, and send. A peer spawned "to have it ready" and never addressed is an empty pane consuming a model session — exactly the failure this rule exists for.
65
+ - **`peer_ready: false` means the peer did not start.** The result carries the pane's last output; read it, fix the cause or close the pane, and spawn again. Do not `coms_send` into a name that never registered and do not spawn a second peer to work around the first — a pane that exists is not a peer, and the pool only ever contains names that actually registered.
65
66
  - **Close what you opened.** If a peer you spawned received no work by the end of the turn, say so and offer to close it. The hub names never-addressed hub-spawned panes in the end-of-session digest; `herdr_close_pane` still needs the human's confirmation, so surface the suggestion rather than assuming it.
@@ -2,8 +2,10 @@
2
2
  name: plan-reviewer
3
3
  description: Plan critic — reviews, challenges, and validates implementation plans
4
4
  tools: read,grep,find,ls
5
- model: openai-codex/gpt-5.6-terra
5
+ model: xai/grok-4.5
6
6
  models:
7
+ - openai-codex/gpt-5.6-terra
8
+ - github-copilot/claude-opus-5
7
9
  - openai-codex/gpt-5.6-sol
8
10
  - openai-codex/gpt-5.6-luna
9
11
  - ollama/nemotron-3-ultra:cloud
package/agents/planner.md CHANGED
@@ -4,6 +4,7 @@ description: Architecture and implementation planning — produces a written PLA
4
4
  tools: read,grep,find,ls,bash,write
5
5
  model: openai-codex/gpt-5.6-sol
6
6
  models:
7
+ - github-copilot/claude-fable-5
7
8
  - openai-codex/gpt-5.6-terra
8
9
  - openai-codex/gpt-5.6-luna
9
10
  - ollama/nemotron-3-ultra:cloud
@@ -12,13 +13,13 @@ thinking: high
12
13
  delegate_depth: 1
13
14
  subagents:
14
15
  scout:
15
- model: openai-codex/gpt-5.6-luna
16
+ model: openai-codex/gpt-5.3-codex-spark
16
17
  tools: read,grep,find,ls
17
18
  rules:
18
19
  model: openai-codex/gpt-5.6-luna
19
20
  tools: read,grep,find,ls
20
21
  risk:
21
- model: openai-codex/gpt-5.6-luna
22
+ model: xai/grok-4.5
22
23
  tools: read,grep,find,ls
23
24
  ---
24
25
  You are a planner agent. Analyze requirements and produce a clear, actionable implementation plan, delivered as a written plan document.
@@ -4,6 +4,7 @@ description: Security engineer focused on vulnerability detection, threat modeli
4
4
  tools: read,bash,grep,find,ls
5
5
  model: openai-codex/gpt-5.6-sol
6
6
  models:
7
+ - xai/grok-4.5
7
8
  - openai-codex/gpt-5.6-terra
8
9
  - openai-codex/gpt-5.6-luna
9
10
  - ollama/nemotron-3-ultra:cloud
@@ -2,8 +2,10 @@
2
2
  name: test-engineer
3
3
  description: QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
4
4
  tools: read,write,edit,bash,grep,find,ls
5
- model: openai-codex/gpt-5.6-terra
5
+ model: xai/grok-4.5
6
6
  models:
7
+ - github-copilot/claude-opus-5
8
+ - openai-codex/gpt-5.6-terra
7
9
  - openai-codex/gpt-5.6-sol
8
10
  - openai-codex/gpt-5.6-luna
9
11
  - ollama/kimi-k2.7-code:cloud
@@ -3,6 +3,7 @@ name: web-debugger
3
3
  description: Interactive headful Chrome debugging via Chrome DevTools MCP — live DOM snapshots, console, network, and performance traces. Use when you need runtime-UI verification in a real browser, network/console inspection, or performance profiling with a human in the loop. Runs as a coms peer that loads the chrome-devtools-mcp extension. Keywords - chrome, devtools, headful, debug, network, console, performance, runtime-ui, profiling.
4
4
  model: openai-codex/gpt-5.6-terra
5
5
  models:
6
+ - github-copilot/claude-opus-5
6
7
  - openai-codex/gpt-5.6-sol
7
8
  - openai-codex/gpt-5.6-luna
8
9
  - ollama/glm-5.2:cloud
@@ -4,6 +4,7 @@ description: Web performance engineer focused on Core Web Vitals, loading, rende
4
4
  tools: read,bash,grep,find,ls
5
5
  model: openai-codex/gpt-5.6-terra
6
6
  models:
7
+ - github-copilot/claude-opus-5
7
8
  - openai-codex/gpt-5.6-sol
8
9
  - openai-codex/gpt-5.6-luna
9
10
  - ollama/nemotron-3-ultra:cloud
@@ -167,7 +167,7 @@ These are the external systems Agent Fleet assumes or integrates with — not np
167
167
  .pi/ # Pi runtime: harnesses, extensions, agents config, prompts
168
168
  skills/ # Agent Fleet-native skills (shadow vendored names)
169
169
  agents/ # Personas/subagents used by Agent Fleet
170
- scripts/ # CLI helpers, bridges, team launchers (pure logic in scripts/lib/)
170
+ scripts/ # CLI helpers, bridges, team + one-off peer launchers (pure logic in scripts/lib/)
171
171
  hermes/ # Hermes-facing skills/integration assets
172
172
  codex/ # Canonical Codex conductor contract (runtime copy lives outside checkout)
173
173
  systemd/user/ # Owned user-unit template for Codex remote control
@@ -75,6 +75,7 @@ just fleet install # one-time runtime deps only; starts no Pi/harness
75
75
  just fleet # guarded Pi + STT and core utilities
76
76
  just fleet hub # guarded multi-agent hub
77
77
  just fleet team docs # hub + guarded Herdr peer team
78
+ just fleet peer code-reviewer --project af # ONE peer in its own Herdr pane, no team
78
79
  just fleet help # unified command grammar
79
80
  just --list # shows the single public `fleet` entry point
80
81
  ```
@@ -92,7 +93,7 @@ inside the package. The `@mariozechner/pi-*` packages are provided by the pi run
92
93
 
93
94
  | Extension | Category | What it does | Run |
94
95
  |-----------|----------|--------------|-----|
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, `/af-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
+ | [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, `/af-handoff`, peer-as-subagent, and footer `agent fleet 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
97
  | [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
98
  | [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
99
  | [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>` |
@@ -113,13 +114,22 @@ unguarded.
113
114
  ### Harness version footer and provenance
114
115
 
115
116
  The three persistent-UI harnesses — `agent-hub`, `coms`, and
116
- `damage-control-continue` — each register `v<version>` on one shared status key. In pi's
117
+ `damage-control-continue` — each register `agent fleet v<version>` on one shared status key. In pi's
117
118
  default status footer, that shared key gives a supported stack exactly one version instead of one
118
119
  copy per harness. `agent-hub` replaces the default footer: it does **not** consume that status
119
120
  key. Its custom footer reads its own adjacent stamped manifest and renders one local version
120
- first — `v<version> · <model><thinking> · <team>` — so an agent-hub stack also displays the
121
+ first — `agent fleet v<version> · <model><thinking> · <team>` — so an agent-hub stack also displays the
121
122
  version exactly once.
122
123
 
124
+ The `agent fleet` half of that label is an [OSC 8](https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda)
125
+ terminal hyperlink to the project homepage, so a click in a terminal that supports hyperlinks
126
+ (Ghostty, iTerm2, WezTerm, Kitty, VS Code, GNOME Terminal, tmux 3.4+) opens the repository. It is a
127
+ terminal-level link, not a TUI control: pi has no mouse tracking, so a click cannot open an
128
+ in-process overlay — the URL goes to the OS opener. Terminals without OSC 8 support render the
129
+ label unchanged, and pi's `visibleWidth`/`truncateToWidth` strip OSC sequences, so the link costs no
130
+ footer columns. Set `AGENT_FLEET_NO_LINKS=1` to fall back to a plain label on multiplexers that
131
+ mangle unknown OSC sequences (GNU screen, tmux before 3.4).
132
+
123
133
  The shared version status is independent of mutable owner status: for example, a
124
134
  Damage-Control violation can replace its own safety message without overwriting the version
125
135
  entry. The canonical value is the root `package.json` version. During a release,
@@ -199,6 +209,59 @@ This repo ships **two** ways to drive a browser from a pi agent. They are comple
199
209
 
200
210
  Why `web-debugger` is a coms peer and not a dispatchable subagent: its `chrome_devtools__*` tools come from the always-on `chrome-devtools-mcp` extension, and agent-hub spawns subagents with `--no-extensions`, so a dispatched child would not have those tools. A coms peer is its own pi process that loads the extension explicitly (via the `extensions:` field in `.pi/agents/peers.yaml`, routed through the `_peer-plus` recipe), and a long-lived peer maps naturally onto one persistent live browser. `bowser` has no such constraint because it only needs Bash + the `playwright-cli` binary on PATH.
201
211
 
212
+ ## One peer at a time — `just fleet peer`
213
+
214
+ `just fleet team <preset>` is the right tool for a *known* set of collaborators, but it
215
+ requires every peer to be declared in `.pi/agents/peers.yaml` and it builds a whole
216
+ workspace. When you want **one** more agent — often a Claude Code reviewer — next to
217
+ what you already have:
218
+
219
+ ```bash
220
+ just fleet peer code-reviewer --project af # peers.yaml decides the runner
221
+ just fleet peer scratch-reviewer --runner claude-code --model opus --project af
222
+ just fleet peer researcher --model openai-codex/gpt-5.6-luna --project af
223
+ just fleet peer web-debugger --browser --project af # persona peer + devtools MCP
224
+ just fleet peer nick --here --project af # this terminal, not a pane
225
+ just fleet peer anything --runner claude-code --dry-run # print the plan, touch nothing
226
+ ```
227
+
228
+ **The name decides the shape of the peer** — one verb, three launchers:
229
+
230
+ | The name… | Peer | Recipe |
231
+ |---|---|---|
232
+ | is declared in `peers.yaml` | whatever it declares (`runner`, `model`, `extensions`, `env_file`) | per declaration |
233
+ | matches `agents/<name>.md` | that guarded persona peer | `_peer` / `_peer-plus` |
234
+ | matches nothing | Fleet Core + coms under that identity, no persona | `_fleet-peer` |
235
+ | `--runner claude-code` | interactive Claude Code + its coms bridge in one pane | `_claude-peer` |
236
+
237
+ The third row is what this command meant before pane placement existed, and it is the
238
+ only shape that accepts raw pi arguments — everything after `--` goes to pi verbatim
239
+ (`just fleet peer nick --here -- --session /path/to/session.json`). Note that the
240
+ persona-by-name rule can change what an existing invocation means: `agents/architect.md`
241
+ exists, so `just fleet peer architect` is now the architect persona peer. `--no-persona`
242
+ forces the plain Fleet Core shape back.
243
+
244
+ - **Placement** — by default the peer gets its own pane: run inside a herdr pane and it
245
+ splits *that* pane (`--direction right|down`); run outside herdr and it creates a
246
+ single-pane workspace labelled `<worktree-tag>-peer-<name>`, refusing to clobber an
247
+ existing one. `--here` runs it in the calling terminal instead.
248
+ - **Field resolution** — explicit flag → the `peers.yaml` declaration for that *name*
249
+ (searched across every team) → a convention default. A name the fleet already defines
250
+ keeps its declared fields; a name it does not need no manifest entry at all.
251
+ - **Nothing is silently dropped** — a flag that cannot apply to the resolved shape is an
252
+ error, not a no-op: `--all-extensions` on a persona peer, `--persona` on a Claude Code
253
+ peer, a mistyped flag, or a pi flag that forgot its `--` separator.
254
+ - **`--project` matters** — same rule as teams: the flag form is `--project af`;
255
+ `project=af` is a `just` variable override and is silently ignored, leaving the peer
256
+ in the shared `default` pool.
257
+ - **Readiness** — a pane launch waits (bounded) for the peer to register in the coms pool
258
+ and exits non-zero with the pane's last output if it never does. A peer that missed
259
+ the window has failed to start, not started slowly.
260
+
261
+ Pure logic in `scripts/lib/peer-launch.ts` (under `node --test`); the herdr wiring is
262
+ `scripts/peer-launch.ts`. Inside a hub session the equivalent is the `herdr_spawn_peer`
263
+ tool, which shares the same command builder and readiness policy.
264
+
202
265
  ## Environment variables
203
266
 
204
267
  The `justfile` sets `dotenv-load`, so a `.env` file at the repo root is auto-loaded
package/justfile CHANGED
@@ -98,7 +98,16 @@ fleet *args:
98
98
  _fleet-core browser="false" all_extensions="false" *args:
99
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
100
 
101
- # Hidden guarded peer launcher for an interactive, addressable Fleet node.
101
+ # Hidden entry point for `just fleet peer <name>`: resolves the peer (runner,
102
+ # persona, model, extensions from .pi/agents/peers.yaml or flags) and launches it
103
+ # in a pane of its own — splitting the current pane inside herdr, else creating a
104
+ # one-pane workspace. `--here` runs it in the calling terminal instead.
105
+ _fleet-peer-launch *args:
106
+ {{node_ts}} scripts/peer-launch.ts {{args}}
107
+
108
+ # Hidden guarded peer launcher for an interactive, addressable Fleet node with no
109
+ # persona: Fleet Core + coms under `--name`, plus raw pi arguments. Reached via
110
+ # `just fleet peer <name>` when no persona resolves for the name.
102
111
  _fleet-peer name browser="false" all_extensions="false" *args:
103
112
  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
113
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@chankov/agent-fleet",
3
- "version": "0.0.8",
3
+ "version": "0.0.9",
4
4
  "description": "Multi-agent fleet orchestration for coding agents. Pi as the primary runtime, Herdr as the workspace control plane, coms as the peer data plane, and Hermes for remote control — plus skills, personas, harnesses, and a guided setup CLI.",
5
5
  "keywords": [
6
6
  "ai",
@@ -107,7 +107,7 @@
107
107
  "access": "public"
108
108
  },
109
109
  "scripts": {
110
- "test": "node bin/cli.js --version && node bin/cli.js --help && node bin/cli.js transform-persona --list --agent claude-code && node --test \"bin/test/*.test.js\" scripts/agent-hub-helpers.test.mjs scripts/agent-hub-spawn.test.mjs scripts/agent-hub-delegate.test.mjs scripts/agent-hub-research.test.mjs .pi/harnesses/lib/herdr-client.test.ts .pi/harnesses/lib/herdr-presence.test.ts .pi/harnesses/lib/coms-registry-entry.test.ts scripts/coms-cli.test.ts scripts/lib/codex-conductor.test.ts scripts/lib/codex-remote-control.test.ts scripts/lib/fleet-command.test.ts scripts/lib/team-project.test.ts scripts/lib/herdr-layout.test.ts scripts/lib/spawn-stagger.test.ts scripts/lib/monitor-env.test.ts scripts/lib/fleet-extras.test.ts scripts/lib/team-snapshot.test.ts scripts/team-snapshot.command.test.ts scripts/lib/coms-envelope.test.ts scripts/lib/claude-bridge-core.test.ts scripts/lib/hermes-bridge-core.test.ts scripts/coms-hermes-bridge.test.ts .pi/harnesses/ask-user-remote/race-core.test.js .pi/harnesses/ask-user-remote/index.test.ts .pi/harnesses/agent-hub/extension-loader.test.ts .pi/extensions/btw/state.test.js .pi/harnesses/agent-hub/footer.test.ts .pi/harnesses/agent-hub/view-default.test.ts .pi/harnesses/agent-hub/safety-routing.test.ts .pi/harnesses/agent-hub/approval-routing.integration.test.ts .pi/harnesses/agent-hub/run-budget.test.js .pi/harnesses/agent-hub/assertion-ledger.test.js .pi/harnesses/agent-hub/provider-semaphore.test.js .pi/harnesses/agent-hub/spawned-peers.test.js .pi/harnesses/agent-hub/context-window.test.js .pi/harnesses/agent-hub/drift-watchdog.test.js .pi/harnesses/agent-hub/session-health.test.js .pi/harnesses/agent-hub/return-contract.test.js .pi/harnesses/agent-hub/return-extract.test.js .pi/harnesses/agent-hub/backend-policy.test.js .pi/harnesses/agent-hub/artifacts.test.js .pi/harnesses/agent-hub/scope-gate.test.js .pi/harnesses/agent-hub/evidence-rules.test.js .pi/harnesses/agent-hub/research-retention.test.js .pi/harnesses/lib/damage-control-shared.test.ts .pi/harnesses/damage-control-continue/herdr-rules.test.js .pi/harnesses/damage-control-continue/exemptions.test.js scripts/lib/hermes-monitor-model.test.ts scripts/lib/hermes-monitor-events.test.ts scripts/lib/hermes-monitor-store.test.ts scripts/lib/hermes-monitor-retention.integration.test.ts scripts/lib/hermes-monitor-registry.test.ts scripts/lib/hermes-monitor-socket.test.ts scripts/lib/hermes-monitor-data-path.test.ts scripts/lib/hermes-monitor-slice7-9-backend.test.ts scripts/lib/hermes-monitor-control-socket.test.ts scripts/lib/hermes-monitor-e2e.test.ts scripts/lib/hermes-monitor-plugin-handshake.test.ts scripts/hermes-monitor-capability-runner.test.ts scripts/hermes-monitor-scenario.test.ts scripts/hermes-watchdog-capability-probe.test.ts .pi/harnesses/agent-hub/monitor-invoke.test.ts .pi/harnesses/agent-hub/monitor-invoke-journal.test.ts .pi/harnesses/agent-hub/monitor-control.test.ts .pi/harnesses/agent-hub/monitor-live-bridge-gaps.test.ts .pi/harnesses/agent-hub/monitor-review-live-wiring.red.test.ts .pi/harnesses/agent-hub/monitor-runtime.test.ts .pi/harnesses/agent-hub/monitor-bridge-runtime.test.ts .pi/harnesses/agent-hub/monitor-reconcile.test.ts .pi/harnesses/agent-hub/monitor-recovery.test.ts .pi/harnesses/agent-hub/monitor-lifecycle-lease.test.ts .pi/harnesses/agent-hub/monitor-session-bridge-race.test.ts .pi/harnesses/agent-hub/monitor-session-bridge.test.ts .pi/harnesses/agent-hub/monitor-cancel-race.test.ts .pi/harnesses/agent-hub/monitor-wait-only.test.ts .pi/harnesses/agent-hub/monitor-publisher.test.ts .pi/harnesses/agent-hub/monitor-index.integration.test.ts hermes/desktop-plugins/agent-fleet-herdr/presentation.test.js scripts/docs-links.test.mjs && npm run test:watchdog-py",
110
+ "test": "node bin/cli.js --version && node bin/cli.js --help && node bin/cli.js transform-persona --list --agent claude-code && node --test \"bin/test/*.test.js\" scripts/agent-hub-helpers.test.mjs scripts/agent-hub-spawn.test.mjs scripts/agent-hub-delegate.test.mjs scripts/agent-hub-research.test.mjs .pi/harnesses/lib/herdr-client.test.ts .pi/harnesses/lib/herdr-presence.test.ts .pi/harnesses/lib/coms-registry-entry.test.ts scripts/coms-cli.test.ts scripts/lib/codex-conductor.test.ts scripts/lib/codex-remote-control.test.ts scripts/lib/fleet-command.test.ts scripts/lib/team-project.test.ts scripts/lib/herdr-layout.test.ts scripts/lib/peer-launch.test.ts scripts/lib/spawn-stagger.test.ts scripts/lib/monitor-env.test.ts scripts/lib/fleet-extras.test.ts scripts/lib/team-snapshot.test.ts scripts/team-snapshot.command.test.ts scripts/lib/coms-envelope.test.ts scripts/lib/claude-bridge-core.test.ts scripts/lib/hermes-bridge-core.test.ts scripts/coms-hermes-bridge.test.ts .pi/harnesses/ask-user-remote/race-core.test.js .pi/harnesses/ask-user-remote/index.test.ts .pi/harnesses/agent-hub/extension-loader.test.ts .pi/extensions/btw/state.test.js .pi/harnesses/agent-hub/footer.test.ts .pi/harnesses/agent-hub/view-default.test.ts .pi/harnesses/agent-hub/safety-routing.test.ts .pi/harnesses/agent-hub/approval-routing.integration.test.ts .pi/harnesses/agent-hub/run-budget.test.js .pi/harnesses/agent-hub/assertion-ledger.test.js .pi/harnesses/agent-hub/provider-semaphore.test.js .pi/harnesses/lib/spawned-peers.test.js .pi/harnesses/agent-hub/context-window.test.js .pi/harnesses/agent-hub/drift-watchdog.test.js .pi/harnesses/agent-hub/session-health.test.js .pi/harnesses/agent-hub/return-contract.test.js .pi/harnesses/agent-hub/return-extract.test.js .pi/harnesses/agent-hub/backend-policy.test.js .pi/harnesses/agent-hub/artifacts.test.js .pi/harnesses/agent-hub/scope-gate.test.js .pi/harnesses/agent-hub/evidence-rules.test.js .pi/harnesses/agent-hub/research-retention.test.js .pi/harnesses/lib/damage-control-shared.test.ts .pi/harnesses/damage-control-continue/herdr-rules.test.js .pi/harnesses/damage-control-continue/exemptions.test.js scripts/lib/hermes-monitor-model.test.ts scripts/lib/hermes-monitor-events.test.ts scripts/lib/hermes-monitor-store.test.ts scripts/lib/hermes-monitor-retention.integration.test.ts scripts/lib/hermes-monitor-registry.test.ts scripts/lib/hermes-monitor-socket.test.ts scripts/lib/hermes-monitor-data-path.test.ts scripts/lib/hermes-monitor-slice7-9-backend.test.ts scripts/lib/hermes-monitor-control-socket.test.ts scripts/lib/hermes-monitor-e2e.test.ts scripts/lib/hermes-monitor-plugin-handshake.test.ts scripts/hermes-monitor-capability-runner.test.ts scripts/hermes-monitor-scenario.test.ts scripts/hermes-watchdog-capability-probe.test.ts .pi/harnesses/agent-hub/monitor-invoke.test.ts .pi/harnesses/agent-hub/monitor-invoke-journal.test.ts .pi/harnesses/agent-hub/monitor-control.test.ts .pi/harnesses/agent-hub/monitor-live-bridge-gaps.test.ts .pi/harnesses/agent-hub/monitor-review-live-wiring.red.test.ts .pi/harnesses/agent-hub/monitor-runtime.test.ts .pi/harnesses/agent-hub/monitor-bridge-runtime.test.ts .pi/harnesses/agent-hub/monitor-reconcile.test.ts .pi/harnesses/agent-hub/monitor-recovery.test.ts .pi/harnesses/agent-hub/monitor-lifecycle-lease.test.ts .pi/harnesses/agent-hub/monitor-session-bridge-race.test.ts .pi/harnesses/agent-hub/monitor-session-bridge.test.ts .pi/harnesses/agent-hub/monitor-cancel-race.test.ts .pi/harnesses/agent-hub/monitor-wait-only.test.ts .pi/harnesses/agent-hub/monitor-publisher.test.ts .pi/harnesses/agent-hub/monitor-index.integration.test.ts hermes/desktop-plugins/agent-fleet-herdr/presentation.test.js scripts/docs-links.test.mjs && npm run test:watchdog-py",
111
111
  "test:watchdog-py": "PYTHONDONTWRITEBYTECODE=1 python3 -m unittest discover -s hermes/watchdog-tests -p 'test_*.py'",
112
112
  "pack:dry": "npm pack --dry-run",
113
113
  "changeset": "changeset",
package/scripts/fleet.ts CHANGED
@@ -27,9 +27,25 @@ SESSION MODES
27
27
  Safe interactive Pi without Hub or a coms identity.
28
28
  Example: just fleet --model openai-codex/gpt-5.6-terra
29
29
 
30
- just fleet peer <name> [PI_ARGS...]
31
- Safe interactive Pi registered as an addressable coms peer.
32
- Example: just fleet peer architect --project af
30
+ just fleet peer <name> [--runner pi|claude-code] [--persona <p>|--no-persona]
31
+ [--model <m>] [--project <p>] [--extensions a,b]
32
+ [--browser] [--all-extensions] [--direction right|down]
33
+ [--here] [--dry-run] [-- PI_ARGS...]
34
+ ONE addressable coms peer, in a herdr pane of its own. Inside herdr it
35
+ splits the current pane; outside it creates a single-pane workspace;
36
+ --here runs it in this terminal instead.
37
+ The NAME decides the shape: a name declared in .pi/agents/peers.yaml keeps
38
+ its runner/model/extensions/env_file, a name matching agents/<name>.md
39
+ becomes that persona peer, and anything else is a plain Fleet Core peer
40
+ under that identity. --runner claude-code needs no manifest at all, and
41
+ --no-persona forces the plain shape for a name that matches a persona.
42
+ Raw pi arguments go after a "--" separator and need the plain shape.
43
+ Examples:
44
+ just fleet peer code-reviewer --project af
45
+ just fleet peer scratch-reviewer --runner claude-code --model opus --project af
46
+ just fleet peer web-debugger --browser --project af
47
+ just fleet peer nick --here --project af
48
+ just fleet peer architect --no-persona --here -- --session /path/to/session.json
33
49
 
34
50
  just fleet hub [--solo] [PI_ARGS...]
35
51
  Agent Hub dispatcher. Embedded coms is on unless --solo is supplied.
@@ -87,10 +103,13 @@ CODEX REMOTE-CONTROL CONDUCTOR
87
103
  CAPABILITY FLAGS
88
104
  --browser
89
105
  Add interactive Chrome DevTools MCP tools to the main Pi/Hub process.
106
+ On a persona peer it adds the chrome-devtools-mcp extension instead.
90
107
  Example: just fleet hub --browser --project af
91
108
 
92
109
  --all-extensions
93
110
  Also auto-load arbitrary project/global extensions outside Fleet Core.
111
+ Not available to persona peers: reusable peers load a deterministic set,
112
+ declared per peer via extensions: in .pi/agents/peers.yaml.
94
113
  Example: just fleet peer debugger --all-extensions --project af
95
114
 
96
115
  SETUP
@@ -45,10 +45,12 @@ export function parseFleetCommand(argv: string[]): FleetInvocation {
45
45
  const [mode, ...tail] = argv;
46
46
  if (mode === "install") return { recipe: "_fleet-install", args: tail };
47
47
 
48
+ // One addressable peer, in a pane of its own unless --here. peer-launch.ts
49
+ // owns the whole flag set (including `--` passthrough to pi), so the tail is
50
+ // forwarded verbatim rather than pre-chewed the way core/hub capabilities are.
48
51
  if (mode === "peer") {
49
- const name = requireValue(tail[0], "fleet peer requires a peer name");
50
- const c = capabilities(tail.slice(1));
51
- return { recipe: "_fleet-peer", args: [name, bool(c.browser), bool(c.allExtensions), ...c.rest] };
52
+ requireValue(tail[0], "fleet peer requires a peer name");
53
+ return { recipe: "_fleet-peer-launch", args: tail };
52
54
  }
53
55
 
54
56
  if (mode === "hub") {