@chankov/agent-fleet 0.0.3 → 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.
- package/.claude/commands/set-hermes-telegram.md +15 -0
- package/.claude/commands/setup-agent-fleet.md +1 -1
- package/.opencode/commands/af-set-hermes-telegram.md +15 -0
- package/.opencode/commands/af-setup-agent-fleet.md +1 -1
- package/.pi/agents/dispatch-policy.yaml +1 -1
- package/.pi/agents/peers.yaml +4 -4
- package/.pi/extensions/chrome-devtools-mcp/README.md +1 -1
- package/.pi/extensions/mcp-bridge/README.md +1 -1
- package/.pi/harnesses/agent-hub/README.md +223 -40
- package/.pi/harnesses/agent-hub/access-approval.ts +135 -0
- package/.pi/harnesses/agent-hub/delegate.ts +32 -9
- package/.pi/harnesses/agent-hub/drift-watchdog.js +165 -0
- package/.pi/harnesses/agent-hub/footer.ts +29 -0
- package/.pi/harnesses/agent-hub/helpers.ts +49 -0
- package/.pi/harnesses/agent-hub/index.ts +1037 -246
- package/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.pi/harnesses/agent-hub/monitor-session-bridge.ts +11 -0
- package/.pi/harnesses/agent-hub/package.json +5 -4
- package/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.pi/harnesses/agent-hub/run-budget.js +155 -0
- package/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
- package/.pi/harnesses/agent-hub/spawn.ts +161 -94
- package/.pi/harnesses/agent-hub/version.ts +18 -0
- package/.pi/harnesses/ask-user-remote/README.md +1 -0
- package/.pi/harnesses/ask-user-remote/index.ts +36 -8
- package/.pi/harnesses/coms/README.md +15 -5
- package/.pi/harnesses/coms/index.ts +2 -0
- package/.pi/harnesses/coms/package.json +5 -4
- package/.pi/harnesses/coms/version.ts +18 -0
- package/.pi/harnesses/damage-control-continue/README.md +36 -35
- package/.pi/harnesses/damage-control-continue/index.ts +23 -9
- package/.pi/harnesses/damage-control-continue/package.json +5 -4
- package/.pi/harnesses/damage-control-continue/version.ts +18 -0
- package/.pi/harnesses/{damage-control/shared.ts → lib/damage-control-shared.ts} +20 -6
- package/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
- package/.pi/harnesses/lib/hermes-monitor-model.ts +9 -0
- package/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
- package/.pi/harnesses/lib/hermes-monitor-socket.ts +118 -0
- package/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
- package/.pi/prompts/set-hermes-telegram.md +15 -0
- package/.pi/prompts/setup-agent-fleet.md +1 -1
- package/.versions/0.0.4/.claude/commands/build.md +44 -0
- package/.versions/0.0.4/.claude/commands/code-simplify.md +22 -0
- package/.versions/0.0.4/.claude/commands/design-agent.md +14 -0
- package/.versions/0.0.4/.claude/commands/doctor-agent-fleet.md +17 -0
- package/.versions/0.0.4/.claude/commands/orchestrate.md +112 -0
- package/.versions/0.0.4/.claude/commands/plan.md +16 -0
- package/.versions/0.0.4/.claude/commands/prime.md +22 -0
- package/.versions/0.0.4/.claude/commands/review.md +16 -0
- package/.versions/0.0.4/.claude/commands/setup-agent-fleet.md +25 -0
- package/.versions/0.0.4/.claude/commands/ship.md +72 -0
- package/.versions/0.0.4/.claude/commands/spec.md +15 -0
- package/.versions/0.0.4/.claude/commands/test.md +19 -0
- package/.versions/0.0.4/.claude/commands/webperf.md +32 -0
- package/.versions/0.0.4/.claude/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.4/.opencode/commands/af-build.md +17 -0
- package/.versions/0.0.4/.opencode/commands/af-code-simplify.md +16 -0
- package/.versions/0.0.4/.opencode/commands/af-compound.md +16 -0
- package/.versions/0.0.4/.opencode/commands/af-design-agent.md +15 -0
- package/.versions/0.0.4/.opencode/commands/af-doctor-agent-fleet.md +17 -0
- package/.versions/0.0.4/.opencode/commands/af-orchestrate.md +112 -0
- package/.versions/0.0.4/.opencode/commands/af-plan.md +16 -0
- package/.versions/0.0.4/.opencode/commands/af-prime.md +22 -0
- package/.versions/0.0.4/.opencode/commands/af-review.md +15 -0
- package/.versions/0.0.4/.opencode/commands/af-setup-agent-fleet.md +15 -0
- package/.versions/0.0.4/.opencode/commands/af-ship.md +16 -0
- package/.versions/0.0.4/.opencode/commands/af-spec.md +16 -0
- package/.versions/0.0.4/.opencode/commands/af-test.md +21 -0
- package/.versions/0.0.4/.opencode/commands/af-webperf.md +32 -0
- package/.versions/0.0.4/.opencode/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.4/.pi/agents/dispatch-policy.yaml +32 -0
- package/.versions/0.0.4/.pi/agents/model-profiles.yaml +20 -0
- package/.versions/0.0.4/.pi/agents/peers.yaml +146 -0
- package/.versions/0.0.4/.pi/agents/teams.yaml +39 -0
- package/.versions/0.0.4/.pi/damage-control-rules.yaml +297 -0
- package/.versions/0.0.4/.pi/extensions/agent-fleet-update-check/README.md +58 -0
- package/.versions/0.0.4/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
- package/{.pi/harnesses/damage-control → .versions/0.0.4/.pi/extensions/agent-fleet-update-check}/package.json +1 -1
- package/.versions/0.0.4/.pi/extensions/btw/README.md +118 -0
- package/.versions/0.0.4/.pi/extensions/btw/index.ts +917 -0
- package/.versions/0.0.4/.pi/extensions/btw/package.json +6 -0
- package/.versions/0.0.4/.pi/extensions/btw/state.js +179 -0
- package/.versions/0.0.4/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
- package/.versions/0.0.4/.pi/extensions/chrome-devtools-mcp/index.ts +92 -0
- package/.versions/0.0.4/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
- package/.versions/0.0.4/.pi/extensions/compact-and-continue/README.md +42 -0
- package/.versions/0.0.4/.pi/extensions/compact-and-continue/index.ts +120 -0
- package/.versions/0.0.4/.pi/extensions/compact-and-continue/package.json +6 -0
- package/.versions/0.0.4/.pi/extensions/mcp-bridge/README.md +46 -0
- package/.versions/0.0.4/.pi/extensions/mcp-bridge/index.ts +206 -0
- package/.versions/0.0.4/.pi/extensions/mcp-bridge/package.json +6 -0
- package/.versions/0.0.4/.pi/extensions/package-lock.json +1143 -0
- package/.versions/0.0.4/.pi/extensions/package.json +9 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/README.md +201 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/config.ts +198 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/index.ts +248 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/package.json +6 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/providers.ts +214 -0
- package/.versions/0.0.4/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/README.md +798 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/access-approval.ts +135 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/artifacts.js +92 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/backend-policy.js +153 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/delegate.ts +386 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/drift-watchdog.js +165 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/footer.ts +29 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/helpers.ts +214 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/index.ts +8045 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/monitor-session-bridge.ts +11 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/package.json +7 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/research-retention.js +34 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/return-contract.js +215 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/run-budget.js +155 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/scope-gate.js +103 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/spawn.ts +246 -0
- package/.versions/0.0.4/.pi/harnesses/agent-hub/version.ts +18 -0
- package/.versions/0.0.4/.pi/harnesses/ask-user-remote/README.md +18 -0
- package/.versions/0.0.4/.pi/harnesses/ask-user-remote/index.ts +293 -0
- package/.versions/0.0.4/.pi/harnesses/ask-user-remote/race-core.js +106 -0
- package/.versions/0.0.4/.pi/harnesses/coms/README.md +92 -0
- package/.versions/0.0.4/.pi/harnesses/coms/index.ts +1745 -0
- package/.versions/0.0.4/.pi/harnesses/coms/package.json +7 -0
- package/.versions/0.0.4/.pi/harnesses/coms/version.ts +18 -0
- package/.versions/0.0.4/.pi/harnesses/damage-control-continue/README.md +117 -0
- package/.versions/0.0.4/.pi/harnesses/damage-control-continue/index.ts +536 -0
- package/.versions/0.0.4/.pi/harnesses/damage-control-continue/package.json +7 -0
- package/.versions/0.0.4/.pi/harnesses/damage-control-continue/version.ts +18 -0
- package/.versions/0.0.4/.pi/harnesses/lib/damage-control-shared.ts +197 -0
- package/.versions/0.0.4/.pi/harnesses/lib/herdr-client.ts +458 -0
- package/.versions/0.0.4/.pi/harnesses/lib/herdr-presence.ts +288 -0
- package/.versions/0.0.4/.pi/harnesses/package-lock.json +35 -0
- package/.versions/0.0.4/.pi/harnesses/package.json +9 -0
- package/.versions/0.0.4/.pi/prompts/build.md +24 -0
- package/.versions/0.0.4/.pi/prompts/code-simplify.md +22 -0
- package/.versions/0.0.4/.pi/prompts/doctor-agent-fleet.md +15 -0
- package/.versions/0.0.4/.pi/prompts/plan.md +16 -0
- package/.versions/0.0.4/.pi/prompts/review.md +16 -0
- package/.versions/0.0.4/.pi/prompts/setup-agent-fleet.md +27 -0
- package/.versions/0.0.4/.pi/prompts/ship.md +17 -0
- package/.versions/0.0.4/.pi/prompts/spec.md +15 -0
- package/.versions/0.0.4/.pi/prompts/test.md +19 -0
- package/.versions/0.0.4/.pi/skills/bowser/SKILL.md +145 -0
- package/.versions/0.0.4/.version +1 -0
- package/.versions/0.0.4/agents/architect.md +23 -0
- package/.versions/0.0.4/agents/bowser.md +26 -0
- package/.versions/0.0.4/agents/builder.md +53 -0
- package/.versions/0.0.4/agents/code-reviewer.md +205 -0
- package/.versions/0.0.4/agents/deep-researcher.md +31 -0
- package/.versions/0.0.4/agents/documenter.md +18 -0
- package/.versions/0.0.4/agents/orchestrator.md +54 -0
- package/.versions/0.0.4/agents/plan-reviewer.md +60 -0
- package/.versions/0.0.4/agents/planner.md +69 -0
- package/.versions/0.0.4/agents/releaser.md +24 -0
- package/.versions/0.0.4/agents/researcher.md +28 -0
- package/.versions/0.0.4/agents/security-auditor.md +166 -0
- package/.versions/0.0.4/agents/test-engineer.md +151 -0
- package/.versions/0.0.4/agents/web-debugger.md +42 -0
- package/.versions/0.0.4/agents/web-performance-auditor.md +192 -0
- package/.versions/0.0.4/codex/CONDUCTOR.md +148 -0
- package/.versions/0.0.4/docs/ARCHITECTURE.md +210 -0
- package/.versions/0.0.4/docs/agent-fleet-setup.md +366 -0
- package/.versions/0.0.4/docs/claude-code-coms-bridge.md +103 -0
- package/.versions/0.0.4/docs/codex-remote-conductor.md +170 -0
- package/.versions/0.0.4/docs/coms-hermes-bridge.md +121 -0
- package/.versions/0.0.4/docs/getting-started.md +183 -0
- package/.versions/0.0.4/docs/npm-install.md +337 -0
- package/.versions/0.0.4/docs/opencode-setup.md +248 -0
- package/.versions/0.0.4/docs/pi-extensions.md +288 -0
- package/.versions/0.0.4/docs/pi-setup.md +463 -0
- package/.versions/0.0.4/docs/skill-anatomy.md +150 -0
- package/.versions/0.0.4/hermes/README.md +228 -0
- package/.versions/0.0.4/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/.versions/0.0.4/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +15 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +19 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +13 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +11 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +9 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +17 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +34 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +151 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +39 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +12 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/.versions/0.0.4/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +22 -0
- package/.versions/0.0.4/hermes/skills/hub-conductor/SKILL.md +84 -0
- package/.versions/0.0.4/hermes/skills/hub-liaison/SKILL.md +84 -0
- package/.versions/0.0.4/hooks/SIMPLIFY-IGNORE.md +90 -0
- package/.versions/0.0.4/hooks/coms-stop-hook.mjs +73 -0
- package/.versions/0.0.4/hooks/hooks.json +14 -0
- package/.versions/0.0.4/hooks/session-start.sh +74 -0
- package/.versions/0.0.4/hooks/simplify-ignore.sh +302 -0
- package/.versions/0.0.4/justfile +256 -0
- package/.versions/0.0.4/references/accessibility-checklist.md +160 -0
- package/.versions/0.0.4/references/definition-of-done.md +67 -0
- package/.versions/0.0.4/references/fleet-coordination-patterns.md +151 -0
- package/.versions/0.0.4/references/observability-checklist.md +91 -0
- package/.versions/0.0.4/references/orchestration-patterns.md +370 -0
- package/.versions/0.0.4/references/performance-checklist.md +153 -0
- package/.versions/0.0.4/references/prompting-patterns.md +380 -0
- package/.versions/0.0.4/references/security-checklist.md +179 -0
- package/.versions/0.0.4/references/testing-patterns.md +236 -0
- package/.versions/0.0.4/scripts/codex-conductor.ts +41 -0
- package/.versions/0.0.4/scripts/codex-remote-control.ts +167 -0
- package/.versions/0.0.4/scripts/coms-claude-bridge.ts +286 -0
- package/.versions/0.0.4/scripts/coms-cli.ts +484 -0
- package/.versions/0.0.4/scripts/coms-hermes-bridge.ts +403 -0
- package/.versions/0.0.4/scripts/hermes-monitor-capability-runner.ts +25 -0
- package/.versions/0.0.4/scripts/hermes-monitor-scenario.ts +7 -0
- package/.versions/0.0.4/scripts/lib/claude-bridge-core.ts +100 -0
- package/.versions/0.0.4/scripts/lib/codex-conductor.ts +88 -0
- package/.versions/0.0.4/scripts/lib/codex-remote-control.ts +480 -0
- package/.versions/0.0.4/scripts/lib/coms-envelope.ts +539 -0
- package/.versions/0.0.4/scripts/lib/fake-herdr-server.ts +88 -0
- package/.versions/0.0.4/scripts/lib/herdr-layout.ts +263 -0
- package/.versions/0.0.4/scripts/lib/hermes-bridge-core.ts +238 -0
- package/.versions/0.0.4/scripts/lib/hermes-monitor-herdr.ts +28 -0
- package/.versions/0.0.4/scripts/lib/hermes-monitor-model.ts +9 -0
- package/.versions/0.0.4/scripts/lib/hermes-monitor-registry.ts +6 -0
- package/.versions/0.0.4/scripts/lib/hermes-monitor-socket.ts +118 -0
- package/.versions/0.0.4/scripts/lib/hermes-monitor-store.ts +31 -0
- package/.versions/0.0.4/scripts/lib/persona-banner.ts +62 -0
- package/.versions/0.0.4/scripts/lib/spawn-stagger.ts +101 -0
- package/.versions/0.0.4/scripts/lib/team-project.ts +184 -0
- package/.versions/0.0.4/scripts/lib/team-snapshot.ts +147 -0
- package/.versions/0.0.4/scripts/peer-banner.ts +40 -0
- package/.versions/0.0.4/scripts/team-snapshot.ts +238 -0
- package/.versions/0.0.4/scripts/team-up.ts +333 -0
- package/.versions/0.0.4/skills/_internal/grilling.md +11 -0
- package/.versions/0.0.4/skills/browser-testing-with-devtools/SKILL.md +352 -0
- package/.versions/0.0.4/skills/code-review-and-quality/SKILL.md +381 -0
- package/.versions/0.0.4/skills/compound-learning/SKILL.md +137 -0
- package/.versions/0.0.4/skills/context-engineering/SKILL.md +291 -0
- package/.versions/0.0.4/skills/deprecation-and-migration/SKILL.md +206 -0
- package/.versions/0.0.4/skills/designing-agents/SKILL.md +394 -0
- package/.versions/0.0.4/skills/designing-agents/pi-harness-authoring.md +222 -0
- package/.versions/0.0.4/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.4/skills/git-workflow-and-versioning/SKILL.md +316 -0
- package/.versions/0.0.4/skills/guided-workspace-setup/SKILL.md +535 -0
- package/.versions/0.0.4/skills/guided-workspace-setup/companion-manifest.json +33 -0
- package/.versions/0.0.4/skills/idea-refine/SKILL.md +182 -0
- package/.versions/0.0.4/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.4/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.4/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.4/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.4/skills/incremental-implementation/SKILL.md +287 -0
- package/.versions/0.0.4/skills/interview-me/SKILL.md +226 -0
- package/.versions/0.0.4/skills/orchestration-verification/SKILL.md +181 -0
- package/.versions/0.0.4/skills/peer-coms/SKILL.md +90 -0
- package/.versions/0.0.4/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.4/skills/planning-and-task-breakdown/SKILL.md +236 -0
- package/.versions/0.0.4/skills/security-and-hardening/SKILL.md +461 -0
- package/.versions/0.0.4/skills/spec-driven-development/SKILL.md +245 -0
- package/.versions/0.0.4/skills/using-agent-skills/SKILL.md +199 -0
- package/.versions/0.0.4/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/LICENSE +21 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/README.md +11 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
- package/.versions/0.0.4/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
- package/.versions/0.0.5/.claude/commands/build.md +44 -0
- package/.versions/0.0.5/.claude/commands/code-simplify.md +22 -0
- package/.versions/0.0.5/.claude/commands/design-agent.md +14 -0
- package/.versions/0.0.5/.claude/commands/doctor-agent-fleet.md +17 -0
- package/.versions/0.0.5/.claude/commands/orchestrate.md +112 -0
- package/.versions/0.0.5/.claude/commands/plan.md +16 -0
- package/.versions/0.0.5/.claude/commands/prime.md +22 -0
- package/.versions/0.0.5/.claude/commands/review.md +16 -0
- package/.versions/0.0.5/.claude/commands/set-hermes-telegram.md +15 -0
- package/.versions/0.0.5/.claude/commands/setup-agent-fleet.md +25 -0
- package/.versions/0.0.5/.claude/commands/ship.md +72 -0
- package/.versions/0.0.5/.claude/commands/spec.md +15 -0
- package/.versions/0.0.5/.claude/commands/test.md +19 -0
- package/.versions/0.0.5/.claude/commands/webperf.md +32 -0
- package/.versions/0.0.5/.claude/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.5/.opencode/commands/af-build.md +17 -0
- package/.versions/0.0.5/.opencode/commands/af-code-simplify.md +16 -0
- package/.versions/0.0.5/.opencode/commands/af-compound.md +16 -0
- package/.versions/0.0.5/.opencode/commands/af-design-agent.md +15 -0
- package/.versions/0.0.5/.opencode/commands/af-doctor-agent-fleet.md +17 -0
- package/.versions/0.0.5/.opencode/commands/af-orchestrate.md +112 -0
- package/.versions/0.0.5/.opencode/commands/af-plan.md +16 -0
- package/.versions/0.0.5/.opencode/commands/af-prime.md +22 -0
- package/.versions/0.0.5/.opencode/commands/af-review.md +15 -0
- package/.versions/0.0.5/.opencode/commands/af-set-hermes-telegram.md +15 -0
- package/.versions/0.0.5/.opencode/commands/af-setup-agent-fleet.md +15 -0
- package/.versions/0.0.5/.opencode/commands/af-ship.md +16 -0
- package/.versions/0.0.5/.opencode/commands/af-spec.md +16 -0
- package/.versions/0.0.5/.opencode/commands/af-test.md +21 -0
- package/.versions/0.0.5/.opencode/commands/af-webperf.md +32 -0
- package/.versions/0.0.5/.opencode/orchestrate-teams.yaml +24 -0
- package/.versions/0.0.5/.pi/agents/dispatch-policy.yaml +32 -0
- package/.versions/0.0.5/.pi/agents/model-profiles.yaml +20 -0
- package/.versions/0.0.5/.pi/agents/peers.yaml +146 -0
- package/.versions/0.0.5/.pi/agents/teams.yaml +39 -0
- package/.versions/0.0.5/.pi/damage-control-rules.yaml +297 -0
- package/.versions/0.0.5/.pi/extensions/agent-fleet-update-check/README.md +58 -0
- package/.versions/0.0.5/.pi/extensions/agent-fleet-update-check/index.ts +161 -0
- package/.versions/0.0.5/.pi/extensions/agent-fleet-update-check/package.json +6 -0
- package/.versions/0.0.5/.pi/extensions/btw/README.md +118 -0
- package/.versions/0.0.5/.pi/extensions/btw/index.ts +917 -0
- package/.versions/0.0.5/.pi/extensions/btw/package.json +6 -0
- package/.versions/0.0.5/.pi/extensions/btw/state.js +179 -0
- package/.versions/0.0.5/.pi/extensions/chrome-devtools-mcp/README.md +58 -0
- package/.versions/0.0.5/.pi/extensions/chrome-devtools-mcp/index.ts +92 -0
- package/.versions/0.0.5/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
- package/.versions/0.0.5/.pi/extensions/compact-and-continue/README.md +42 -0
- package/.versions/0.0.5/.pi/extensions/compact-and-continue/index.ts +120 -0
- package/.versions/0.0.5/.pi/extensions/compact-and-continue/package.json +6 -0
- package/.versions/0.0.5/.pi/extensions/mcp-bridge/README.md +46 -0
- package/.versions/0.0.5/.pi/extensions/mcp-bridge/index.ts +206 -0
- package/.versions/0.0.5/.pi/extensions/mcp-bridge/package.json +6 -0
- package/.versions/0.0.5/.pi/extensions/package-lock.json +1143 -0
- package/.versions/0.0.5/.pi/extensions/package.json +9 -0
- package/.versions/0.0.5/.pi/extensions/pi-voice-stt/README.md +201 -0
- package/.versions/0.0.5/.pi/extensions/pi-voice-stt/config.ts +198 -0
- package/.versions/0.0.5/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
- package/.versions/0.0.5/.pi/extensions/pi-voice-stt/index.ts +248 -0
- package/.versions/0.0.5/.pi/extensions/pi-voice-stt/package.json +6 -0
- package/.versions/0.0.5/.pi/extensions/pi-voice-stt/providers.ts +214 -0
- package/.versions/0.0.5/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/README.md +798 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/access-approval.ts +135 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/artifacts.js +92 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/backend-policy.js +153 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/delegate.ts +386 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/drift-watchdog.js +165 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/footer.ts +29 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/helpers.ts +214 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/index.ts +8045 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/monitor-session-bridge.ts +11 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/package.json +7 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/research-retention.js +34 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/return-contract.js +215 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/run-budget.js +155 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/scope-gate.js +103 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/spawn.ts +246 -0
- package/.versions/0.0.5/.pi/harnesses/agent-hub/version.ts +18 -0
- package/.versions/0.0.5/.pi/harnesses/ask-user-remote/README.md +19 -0
- package/.versions/0.0.5/.pi/harnesses/ask-user-remote/index.ts +321 -0
- package/.versions/0.0.5/.pi/harnesses/ask-user-remote/race-core.js +106 -0
- package/.versions/0.0.5/.pi/harnesses/coms/README.md +92 -0
- package/.versions/0.0.5/.pi/harnesses/coms/index.ts +1745 -0
- package/.versions/0.0.5/.pi/harnesses/coms/package.json +7 -0
- package/.versions/0.0.5/.pi/harnesses/coms/version.ts +18 -0
- package/.versions/0.0.5/.pi/harnesses/damage-control-continue/README.md +117 -0
- package/.versions/0.0.5/.pi/harnesses/damage-control-continue/index.ts +536 -0
- package/.versions/0.0.5/.pi/harnesses/damage-control-continue/package.json +7 -0
- package/.versions/0.0.5/.pi/harnesses/damage-control-continue/version.ts +18 -0
- package/.versions/0.0.5/.pi/harnesses/lib/damage-control-shared.ts +197 -0
- package/.versions/0.0.5/.pi/harnesses/lib/herdr-client.ts +458 -0
- package/.versions/0.0.5/.pi/harnesses/lib/herdr-presence.ts +288 -0
- package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
- package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-model.ts +9 -0
- package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
- package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-socket.ts +118 -0
- package/.versions/0.0.5/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
- package/.versions/0.0.5/.pi/harnesses/package-lock.json +35 -0
- package/.versions/0.0.5/.pi/harnesses/package.json +9 -0
- package/.versions/0.0.5/.pi/prompts/build.md +24 -0
- package/.versions/0.0.5/.pi/prompts/code-simplify.md +22 -0
- package/.versions/0.0.5/.pi/prompts/doctor-agent-fleet.md +15 -0
- package/.versions/0.0.5/.pi/prompts/plan.md +16 -0
- package/.versions/0.0.5/.pi/prompts/review.md +16 -0
- package/.versions/0.0.5/.pi/prompts/set-hermes-telegram.md +15 -0
- package/.versions/0.0.5/.pi/prompts/setup-agent-fleet.md +27 -0
- package/.versions/0.0.5/.pi/prompts/ship.md +17 -0
- package/.versions/0.0.5/.pi/prompts/spec.md +15 -0
- package/.versions/0.0.5/.pi/prompts/test.md +19 -0
- package/.versions/0.0.5/.pi/skills/bowser/SKILL.md +145 -0
- package/.versions/0.0.5/.version +1 -0
- package/.versions/0.0.5/agents/architect.md +23 -0
- package/.versions/0.0.5/agents/bowser.md +26 -0
- package/.versions/0.0.5/agents/builder.md +53 -0
- package/.versions/0.0.5/agents/code-reviewer.md +205 -0
- package/.versions/0.0.5/agents/deep-researcher.md +31 -0
- package/.versions/0.0.5/agents/documenter.md +18 -0
- package/.versions/0.0.5/agents/orchestrator.md +54 -0
- package/.versions/0.0.5/agents/plan-reviewer.md +60 -0
- package/.versions/0.0.5/agents/planner.md +69 -0
- package/.versions/0.0.5/agents/releaser.md +24 -0
- package/.versions/0.0.5/agents/researcher.md +28 -0
- package/.versions/0.0.5/agents/security-auditor.md +166 -0
- package/.versions/0.0.5/agents/test-engineer.md +151 -0
- package/.versions/0.0.5/agents/web-debugger.md +42 -0
- package/.versions/0.0.5/agents/web-performance-auditor.md +192 -0
- package/.versions/0.0.5/codex/CONDUCTOR.md +148 -0
- package/.versions/0.0.5/docs/ARCHITECTURE.md +210 -0
- package/.versions/0.0.5/docs/agent-fleet-setup.md +366 -0
- package/.versions/0.0.5/docs/claude-code-coms-bridge.md +103 -0
- package/.versions/0.0.5/docs/codex-remote-conductor.md +170 -0
- package/.versions/0.0.5/docs/coms-hermes-bridge.md +179 -0
- package/.versions/0.0.5/docs/getting-started.md +183 -0
- package/.versions/0.0.5/docs/npm-install.md +337 -0
- package/.versions/0.0.5/docs/opencode-setup.md +249 -0
- package/.versions/0.0.5/docs/pi-extensions.md +293 -0
- package/.versions/0.0.5/docs/pi-setup.md +472 -0
- package/.versions/0.0.5/docs/skill-anatomy.md +150 -0
- package/.versions/0.0.5/hermes/README.md +231 -0
- package/.versions/0.0.5/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/.versions/0.0.5/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-cap.test.py +15 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-discovery.test.py +19 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-envelope.test.py +13 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-forged-owner.test.py +11 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-lease-list.test.py +9 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-multihub.test.py +17 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter-output.test.py +34 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +151 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/adapter.test.py +39 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/plugin-api-validation.test.py +12 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/.versions/0.0.5/hermes/plugins/agent-fleet-monitor/dashboard/review-live-wiring.red.test.py +22 -0
- package/.versions/0.0.5/hermes/skills/hub-conductor/SKILL.md +84 -0
- package/.versions/0.0.5/hermes/skills/hub-liaison/SKILL.md +84 -0
- package/.versions/0.0.5/hooks/SIMPLIFY-IGNORE.md +90 -0
- package/.versions/0.0.5/hooks/coms-stop-hook.mjs +73 -0
- package/.versions/0.0.5/hooks/hooks.json +14 -0
- package/.versions/0.0.5/hooks/session-start.sh +74 -0
- package/.versions/0.0.5/hooks/simplify-ignore.sh +302 -0
- package/.versions/0.0.5/justfile +245 -0
- package/.versions/0.0.5/references/accessibility-checklist.md +160 -0
- package/.versions/0.0.5/references/definition-of-done.md +67 -0
- package/.versions/0.0.5/references/fleet-coordination-patterns.md +151 -0
- package/.versions/0.0.5/references/observability-checklist.md +91 -0
- package/.versions/0.0.5/references/orchestration-patterns.md +370 -0
- package/.versions/0.0.5/references/performance-checklist.md +153 -0
- package/.versions/0.0.5/references/prompting-patterns.md +380 -0
- package/.versions/0.0.5/references/security-checklist.md +179 -0
- package/.versions/0.0.5/references/testing-patterns.md +236 -0
- package/.versions/0.0.5/scripts/codex-conductor.ts +41 -0
- package/.versions/0.0.5/scripts/codex-remote-control.ts +167 -0
- package/.versions/0.0.5/scripts/coms-claude-bridge.ts +286 -0
- package/.versions/0.0.5/scripts/coms-cli.ts +484 -0
- package/.versions/0.0.5/scripts/coms-hermes-bridge.ts +413 -0
- package/.versions/0.0.5/scripts/fleet.ts +141 -0
- package/.versions/0.0.5/scripts/hermes-monitor-capability-runner.ts +25 -0
- package/.versions/0.0.5/scripts/hermes-monitor-scenario.ts +7 -0
- package/.versions/0.0.5/scripts/lib/claude-bridge-core.ts +100 -0
- package/.versions/0.0.5/scripts/lib/codex-conductor.ts +88 -0
- package/.versions/0.0.5/scripts/lib/codex-remote-control.ts +480 -0
- package/.versions/0.0.5/scripts/lib/coms-envelope.ts +539 -0
- package/.versions/0.0.5/scripts/lib/fake-herdr-server.ts +88 -0
- package/.versions/0.0.5/scripts/lib/fleet-command.ts +109 -0
- package/.versions/0.0.5/scripts/lib/herdr-layout.ts +263 -0
- package/.versions/0.0.5/scripts/lib/hermes-bridge-core.ts +241 -0
- package/.versions/0.0.5/scripts/lib/hermes-monitor-herdr.ts +2 -0
- package/.versions/0.0.5/scripts/lib/hermes-monitor-model.ts +3 -0
- package/.versions/0.0.5/scripts/lib/hermes-monitor-registry.ts +2 -0
- package/.versions/0.0.5/scripts/lib/hermes-monitor-socket.ts +2 -0
- package/.versions/0.0.5/scripts/lib/hermes-monitor-store.ts +2 -0
- package/.versions/0.0.5/scripts/lib/persona-banner.ts +62 -0
- package/.versions/0.0.5/scripts/lib/spawn-stagger.ts +101 -0
- package/.versions/0.0.5/scripts/lib/team-project.ts +191 -0
- package/.versions/0.0.5/scripts/lib/team-snapshot.ts +147 -0
- package/.versions/0.0.5/scripts/peer-banner.ts +40 -0
- package/.versions/0.0.5/scripts/team-snapshot.ts +237 -0
- package/.versions/0.0.5/scripts/team-up.ts +351 -0
- package/.versions/0.0.5/skills/_internal/grilling.md +11 -0
- package/.versions/0.0.5/skills/browser-testing-with-devtools/SKILL.md +352 -0
- package/.versions/0.0.5/skills/code-review-and-quality/SKILL.md +381 -0
- package/.versions/0.0.5/skills/compound-learning/SKILL.md +137 -0
- package/.versions/0.0.5/skills/context-engineering/SKILL.md +291 -0
- package/.versions/0.0.5/skills/deprecation-and-migration/SKILL.md +206 -0
- package/.versions/0.0.5/skills/designing-agents/SKILL.md +394 -0
- package/.versions/0.0.5/skills/designing-agents/pi-harness-authoring.md +222 -0
- package/.versions/0.0.5/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.5/skills/git-workflow-and-versioning/SKILL.md +316 -0
- package/.versions/0.0.5/skills/guided-workspace-setup/SKILL.md +542 -0
- package/.versions/0.0.5/skills/guided-workspace-setup/companion-manifest.json +35 -0
- package/.versions/0.0.5/skills/idea-refine/SKILL.md +182 -0
- package/.versions/0.0.5/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.5/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.5/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.5/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.5/skills/incremental-implementation/SKILL.md +287 -0
- package/.versions/0.0.5/skills/interview-me/SKILL.md +226 -0
- package/.versions/0.0.5/skills/orchestration-verification/SKILL.md +181 -0
- package/.versions/0.0.5/skills/peer-coms/SKILL.md +90 -0
- package/.versions/0.0.5/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.5/skills/planning-and-task-breakdown/SKILL.md +236 -0
- package/.versions/0.0.5/skills/security-and-hardening/SKILL.md +461 -0
- package/.versions/0.0.5/skills/spec-driven-development/SKILL.md +245 -0
- package/.versions/0.0.5/skills/using-agent-skills/SKILL.md +199 -0
- package/.versions/0.0.5/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/LICENSE +21 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/README.md +11 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +294 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +289 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +278 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +203 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +350 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +234 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +467 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +310 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +194 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +206 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +383 -0
- package/.versions/0.0.5/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +191 -0
- package/CHANGELOG.md +62 -0
- package/README.md +17 -16
- package/agents/builder.md +1 -1
- package/agents/code-reviewer.md +1 -1
- package/agents/deep-researcher.md +3 -3
- package/agents/orchestrator.md +20 -11
- package/agents/plan-reviewer.md +3 -3
- package/agents/test-engineer.md +11 -4
- package/bin/cli.js +83 -1
- package/bin/lib/set-hermes-telegram.js +323 -0
- package/bin/lib/validate-overrides.js +19 -0
- package/bin/sync-harness-versions.js +94 -0
- package/docs/ARCHITECTURE.md +49 -4
- package/docs/agent-fleet-setup.md +11 -1
- package/docs/claude-code-coms-bridge.md +4 -4
- package/docs/codex-remote-conductor.md +12 -12
- package/docs/coms-hermes-bridge.md +62 -4
- package/docs/getting-started.md +4 -4
- package/docs/opencode-setup.md +1 -0
- package/docs/pi-extensions.md +73 -33
- package/docs/pi-setup.md +23 -8
- package/hermes/README.md +191 -8
- package/justfile +143 -158
- package/package.json +13 -5
- package/references/fleet-coordination-patterns.md +1 -1
- package/scripts/coms-hermes-bridge.ts +18 -8
- package/scripts/fleet.ts +141 -0
- package/scripts/lib/fake-herdr-server.ts +88 -0
- package/scripts/lib/fleet-command.ts +109 -0
- package/scripts/lib/hermes-bridge-core.ts +5 -2
- package/scripts/lib/hermes-monitor-herdr.ts +2 -0
- package/scripts/lib/hermes-monitor-model.ts +3 -0
- package/scripts/lib/hermes-monitor-registry.ts +2 -0
- package/scripts/lib/hermes-monitor-socket.ts +2 -0
- package/scripts/lib/hermes-monitor-store.ts +2 -0
- package/scripts/lib/team-project.ts +10 -3
- package/scripts/team-snapshot.ts +4 -5
- package/scripts/team-up.ts +24 -6
- package/skills/designing-agents/SKILL.md +2 -2
- package/skills/designing-agents/pi-harness-authoring.md +26 -13
- package/skills/guided-workspace-setup/SKILL.md +22 -12
- package/skills/guided-workspace-setup/companion-manifest.json +3 -1
- package/skills/peer-coms/SKILL.md +1 -1
- package/.pi/harnesses/damage-control/README.md +0 -65
- package/.pi/harnesses/damage-control/index.ts +0 -250
package/docs/ARCHITECTURE.md
CHANGED
|
@@ -13,6 +13,7 @@ the runtime responsibilities and where each module lives in the repository.
|
|
|
13
13
|
| **coms** | Peer communication protocol/data plane — envelope-based P2P messaging between agents | `.pi/harnesses/coms/`, `scripts/lib/coms-envelope.ts`, `scripts/coms-cli.ts` |
|
|
14
14
|
| **Claude Code bridge** | Makes an interactive Claude Code pane a bidirectional coms peer | `scripts/coms-claude-bridge.ts`, `hooks/coms-stop-hook.mjs`, `skills/peer-coms/` — see [claude-code-coms-bridge.md](claude-code-coms-bridge.md) |
|
|
15
15
|
| **Hermes bridge** | Remote human control — relays hub questions to Telegram, races phone vs. local answers, conductor/liaison skills | `scripts/coms-hermes-bridge.ts`, `.pi/harnesses/ask-user-remote/`, `hermes/skills/` — see [coms-hermes-bridge.md](coms-hermes-bridge.md) |
|
|
16
|
+
| **Hermes local monitor transport** | Local, authenticated visibility/control contract for hub-owned task generations; presentation is supplied by an external consumer | `.pi/harnesses/agent-hub/monitor-*.ts`, `.pi/harnesses/lib/hermes-monitor-{model,store,registry,socket}.ts` (with compatibility re-exports under `scripts/lib/`) — see [Hermes artifacts](../hermes/README.md#local-agent-hub-monitor-integration) |
|
|
16
17
|
| **Codex remote-control conductor** | Experimental outbound-only, user-systemd-managed Android conductor; verified on Codex CLI 0.144.x | `scripts/codex-remote-control.ts`, `scripts/codex-conductor.ts`, `codex/CONDUCTOR.md`, `systemd/user/`; runtime under `~/.local/state/agent-fleet/codex-conductor/` — see [codex-remote-conductor.md](codex-remote-conductor.md) |
|
|
17
18
|
| **Skill library** | Lifecycle workflows and quality gates every agent follows | `skills/` (native) + `vendor/agent-skills-upstream/skills/` (vendored) — see [UPSTREAM-SKILLS.md](UPSTREAM-SKILLS.md) |
|
|
18
19
|
| **Personas** | Reusable specialist definitions, transformed per harness | `agents/`, `bin/lib/transform-persona.js` |
|
|
@@ -25,7 +26,7 @@ Agent Fleet is layered on purpose. Work flows **down** (delegate); evidence and
|
|
|
25
26
|
flowchart TD
|
|
26
27
|
You(["You · Hermes inbound relay · Codex outbound conductor on your phone"])
|
|
27
28
|
|
|
28
|
-
subgraph HUBL["HUB — thin dispatcher (just hub · just
|
|
29
|
+
subgraph HUBL["HUB — thin dispatcher (just fleet hub · just fleet team)"]
|
|
29
30
|
Hub["agent-hub harness + orchestrator persona<br/>routes tasks · owns the Verification Contract on disk<br/>never swallows research dumps into its own context"]
|
|
30
31
|
end
|
|
31
32
|
|
|
@@ -74,7 +75,47 @@ hub (orchestrator)
|
|
|
74
75
|
└── Codex Remote Control (Android · outbound coms delegation)
|
|
75
76
|
```
|
|
76
77
|
|
|
77
|
-
Composition rule: **the hub (or a slash command) orchestrates; personas do not invoke other personas as peers.** Specialists may only fan out to their configured **sub-agents**. Research helpers write findings to disk; the hub resumes specialists with paths, not raw dumps.
|
|
78
|
+
Composition rule: **the hub (or a slash command) orchestrates; personas do not invoke other personas as peers.** Specialists may only fan out to their configured **sub-agents**. Research helpers write findings to disk; the hub resumes specialists with paths, not raw dumps.
|
|
79
|
+
|
|
80
|
+
### Research search supervision
|
|
81
|
+
|
|
82
|
+
The shared `spawnPiAgent` seam supervises every `read`/`grep`/`find`/`ls` call from native
|
|
83
|
+
research helpers and nested delegate children. The supervisor tracks JSONL `toolCallId` values
|
|
84
|
+
independently, with a default 120-second deadline (`recon-search-timeout-s: 1..3600|off` under
|
|
85
|
+
`## agent-hub`). It is a per-tool watchdog; the whole-run bound is separate — the execution
|
|
86
|
+
mode's per-run deadline (`agent-turn-timeout-s`), which terminates a hung run as `turn_timeout`.
|
|
87
|
+
On timeout or caller cancellation it owns and terminates the child's process group (SIGTERM,
|
|
88
|
+
then SIGKILL after a bounded grace), has a separate settlement timer for missing `close`/pipe
|
|
89
|
+
drain, and reports timeout separately from cancellation. Research helpers and nested delegates
|
|
90
|
+
are each given safe process-group ownership; delegates forward parent termination so no detached
|
|
91
|
+
child is orphaned. Full pattern catalog: [references/orchestration-patterns.md](../references/orchestration-patterns.md).
|
|
92
|
+
|
|
93
|
+
### Execution modes & turn budgets
|
|
94
|
+
|
|
95
|
+
The hub enforces per-user-turn budgets in code (`run-budget.js`): `fast`/`standard`/`strict`
|
|
96
|
+
modes cap `dispatch_agent` calls, `spawn_research` calls, and wall clock per turn, set the
|
|
97
|
+
per-run deadline above, and control nested delegation. Exhausted budgets make the dispatch
|
|
98
|
+
tools refuse with "summarize and ask the user"; a new user message opens a fresh window.
|
|
99
|
+
Specialist context pressure is measured over input + cacheRead + cacheWrite, and specialist
|
|
100
|
+
sessions are recycled (fresh spawn instead of `-c` resume) after `session-recycle-runs` runs
|
|
101
|
+
or ≥60% measured context — resumed sessions otherwise re-bill their accumulated context on
|
|
102
|
+
every model call. Configured under `## agent-hub` (`mode`, `max-dispatches-per-turn`,
|
|
103
|
+
`max-research-per-turn`, `turn-wall-time-s`, `agent-turn-timeout-s`, `session-recycle-runs`);
|
|
104
|
+
switched live with `/hub-mode`.
|
|
105
|
+
|
|
106
|
+
On top of the mode sit three qualitative guardrails. **Task triage**: the dispatcher
|
|
107
|
+
classifies each turn via the `set_task_tier` tool (`trivial`/`small`/`feature`/`project`)
|
|
108
|
+
and the caps drop to min(mode, tier); a duplicate-dispatch guard refuses near-identical
|
|
109
|
+
re-dispatches within a turn. **Drift watchdog** (`drift-watchdog.js`): armed dispatches are
|
|
110
|
+
observed in-flight from the JSON event stream — deterministic rules (out-of-scope writes
|
|
111
|
+
against the declared `scope` globs, tool-call loops, consecutive failures, tool-call cap)
|
|
112
|
+
escalate to a one-shot cheap LLM judge whose DRIFTING/STUCK verdict terminates the run as
|
|
113
|
+
`drift_stop` (exit 125, partial output preserved); enabled per hub/agent/dispatch
|
|
114
|
+
(`watchdog` key, `/watchdog`, `watchdog` param). **Dynamic teams**: `/agents-add`,
|
|
115
|
+
`/agents-drop`, `/agents-save` restructure the roster live (the system prompt rebuilds
|
|
116
|
+
every turn), and the gated `team_adjust` tool lets the dispatcher itself adjust the roster
|
|
117
|
+
outside fast mode, with user notification. `/hub-report` accounts each turn's dispatches,
|
|
118
|
+
tokens (billed = input + cacheRead + cacheWrite), recycles, drift stops, and refusals.
|
|
78
119
|
|
|
79
120
|
## Runtime stack (tools the fleet sits on)
|
|
80
121
|
|
|
@@ -95,8 +136,8 @@ These are the external systems Agent Fleet assumes or integrates with — not np
|
|
|
95
136
|
|
|
96
137
|
| Dependency | Role | Required? |
|
|
97
138
|
| --- | --- | --- |
|
|
98
|
-
| **[pi](https://github.com/badlogic/pi-mono)** (or your pi install) | Primary coding-agent runtime; loads harnesses, extensions, prompts, and personas | Yes for full fleet mode (`just hub`) |
|
|
99
|
-
| **[herdr](https://herdr.dev)** | Workspace control plane: tiled peer panes, presence push events, team snapshot/resume | Yes for
|
|
139
|
+
| **[pi](https://github.com/badlogic/pi-mono)** (or your pi install) | Primary coding-agent runtime; loads harnesses, extensions, prompts, and personas | Yes for full fleet mode (`just fleet hub`) |
|
|
140
|
+
| **[herdr](https://herdr.dev)** | Workspace control plane: tiled peer panes, presence push events, team snapshot/resume | Yes for team mode (`just fleet team`); optional for `just fleet hub` |
|
|
100
141
|
| **[Claude Code](https://docs.anthropic.com/en/docs/claude-code)** | First-class peer via the [coms bridge](claude-code-coms-bridge.md); also a supported install target for skills/personas | Optional peer / alternate harness |
|
|
101
142
|
| **[OpenCode](https://opencode.ai)** | Skill-driven execution target (`AGENTS.md` + `skill` tool); `af-*` slash commands | Optional alternate harness |
|
|
102
143
|
| **Hermes** | Remote human-in-the-loop (Telegram relay for hub questions) — [coms-hermes-bridge](coms-hermes-bridge.md) | Optional |
|
|
@@ -146,6 +187,10 @@ packages/hermes-bridge/ # future Hermes integration package
|
|
|
146
187
|
the fleet core stays agent-agnostic. Hermes remains the inbound `ask_user`/
|
|
147
188
|
Telegram route; the experimental Codex conductor is outbound-initiated only,
|
|
148
189
|
approval-gated, and restricted to listed peers through the validated wrapper.
|
|
190
|
+
- **Hermes monitor presentation is outside the fleet core.** Agent Fleet owns task state,
|
|
191
|
+
bounded output, leases, and generation-safe cancellation, and exposes them only through
|
|
192
|
+
owner-only discovery and a local Unix socket. A Hermes-facing consumer owns its UI and
|
|
193
|
+
reconnect behavior; no Hermes backend/Desktop plugin is bundled or installed.
|
|
149
194
|
- **External conductor contracts are advisory.** Pi damage-control wraps Pi
|
|
150
195
|
tool calls, not Hermes or Codex processes; human approvals and their
|
|
151
196
|
contracts reduce risk but do not provide an OS command allowlist.
|
|
@@ -106,6 +106,15 @@ targets an end-of-session compound pass writes lessons to.
|
|
|
106
106
|
| `rules` | none | Comma-separated repo-relative folders holding the project's own rule files (HOW — implementation patterns the work must comply with). Resolution is **index-first**: when a folder has a top-level `README.md`/`index.md`, personas read it first and follow its loading manifest (session bundles, conditional-load lists) instead of bulk-reading the tree; a folder without an index is searched **recursively** through all subfolders. The harness tells every dispatched specialist where the rules live and how to resolve them; the planner and code-reviewer personas read the relevant rules, validate their subject against them, and pass them on (cited in plan acceptance criteria / handed to delegate sub-reviewers). Missing folders produce a session-start warning. |
|
|
107
107
|
| `docs` | none | Comma-separated repo-relative documentation **entry points** (WHAT/WHY — architecture, standards, decisions): canonical files (e.g. `Docs/AGENTS.md`) or doc folders (personas start from a folder's `README.md`/index). Unlike `rules`, docs orient rather than bind: every dispatched specialist and research helper is told to read the entry points relevant to its task and follow their links instead of bulk-reading doc trees; the code-reviewer flags changes that alter documented behavior without a doc update; the documenter treats the entry points and the trees they link as the docs it maintains. Missing paths produce a session-start warning. |
|
|
108
108
|
| `research-keep` | `4` | How many **finished** manual/persona research helpers the hub retains (LRU by finish time) so they stay resumable via `/agents-cont rN`; older ones are pruned along with their session files. `all` disables the cap. Auto-research pipe helpers (spawned for `NEEDS_RESEARCH:` pauses) are always pruned as soon as they finish — their findings persist as files under `.pi/agent-sessions/findings/`. Running helpers are never pruned. An invalid value is ignored with a session-start warning. |
|
|
109
|
+
| `recon-search-timeout-s` | `120` | Parent-side deadline, in seconds, for each `read`, `grep`, `find`, or `ls` call made by a native research helper or nested delegate child. Accepts an integer `1`–`3600` or `off`; invalid input warns and falls back to `120`. This is **not** an agent/turn deadline: non-tool work can run indefinitely. On timeout the hub returns `tool_timeout` with call metadata, sends SIGTERM to its owned process group, escalates to SIGKILL after a finite grace period, and settles even if the child never closes or a descendant holds a pipe. If that bounded cleanup cannot confirm child/process-group death, the metadata reports `terminationConfirmed: false`; this prevents a parent hang but may indicate an uninterruptible OS-level process needing operator attention. |
|
|
110
|
+
| `mode` | `standard` | Execution mode for the hub's per-turn budgets: `fast` (single-specialist path, no nested delegation, assertion ledger optional), `standard` (batched execution with moderate budgets), or `strict` (full Verification Contract with wide budgets). Budgets are per **user turn** — exhausted budgets make `dispatch_agent`/`spawn_research` refuse with "summarize and ask the user"; the next user message opens a fresh window. Switchable live with `/hub-mode`. |
|
|
111
|
+
| `max-dispatches-per-turn` | mode default (2/8/24) | `dispatch_agent` calls allowed per user turn. Positive integer or `off` (unlimited). |
|
|
112
|
+
| `max-research-per-turn` | mode default (1/4/12) | `spawn_research` calls allowed per user turn (the auto-research pipe and the `/research` command are exempt). Positive integer or `off`. |
|
|
113
|
+
| `turn-wall-time-s` | mode default (900/3600/14400) | Wall-clock budget, in seconds, per user turn; once exceeded, further dispatch/research calls refuse. Positive integer or `off`. |
|
|
114
|
+
| `agent-turn-timeout-s` | mode default (600/1800/off) | Whole-run deadline, in seconds, for each spawned specialist, research helper, and nested delegate child (unlike `recon-search-timeout-s`, this bounds the entire run). On expiry the run terminates as `turn_timeout` (exit 124) with partial output preserved. Positive integer or `off`. |
|
|
115
|
+
| `session-recycle-runs` | mode default (3/5/5) | Recycle a specialist's accumulated session (fresh spawn instead of `-c` resume) after this many resumed runs. Context is also always recycled at ≥60% measured context (input + cacheRead + cacheWrite). Positive integer or `off` (context threshold still applies). |
|
|
116
|
+
| `watchdog` | `auto` | Drift watchdog default for dispatched specialists: `auto`/`on` arm the in-flight rules (out-of-scope writes, tool-call loops, repeated failures, tool-call cap) with LLM-judge escalation; `off` disarms. Overridable live per hub (`/watchdog on\|off\|auto`), per agent (`/watchdog <agent> on\|off\|clear`), and per dispatch (the `watchdog` param). A DRIFTING/STUCK verdict terminates the run as `drift_stop` (exit 125) with partial output preserved. |
|
|
117
|
+
| `watchdog-judge-model` | researcher persona's model | pi model spec for the one-shot drift judge (e.g. `openai-codex/gpt-5.3-codex-spark`). Falls back to the researcher persona's resolved model, then the dispatcher's. |
|
|
109
118
|
|
|
110
119
|
Example — switch the dispatcher to Bulgarian, pin the builder to sonnet, raise the
|
|
111
120
|
code-reviewer's thinking level, move the code-reviewer's docs sub-reviewer to a
|
|
@@ -120,6 +129,7 @@ models.builder: github-copilot/claude-sonnet-4.6, github-copilot/claude-haiku-4.
|
|
|
120
129
|
thinking.code-reviewer: xhigh
|
|
121
130
|
subagents.code-reviewer.docs: github-copilot/claude-sonnet-4.6, tools=read,grep
|
|
122
131
|
delegate-depth.code-reviewer: 1
|
|
132
|
+
recon-search-timeout-s: 120 # or off to disable the per-tool watchdog
|
|
123
133
|
rules: docs/rules, .ai/rules
|
|
124
134
|
docs: Docs/AGENTS.md, Docs/architecture/ARCHITECTURE_OVERVIEW.md
|
|
125
135
|
```
|
|
@@ -147,7 +157,7 @@ the environment nor declared in the workspace root `.env`.
|
|
|
147
157
|
|
|
148
158
|
### Per-peer env files (`env_file:` in peers.yaml)
|
|
149
159
|
|
|
150
|
-
Fleet peers spawned by `just
|
|
160
|
+
Fleet peers spawned by `just fleet team` can carry their own
|
|
151
161
|
environment: an `env_file:` entry in `.pi/agents/peers.yaml` names a
|
|
152
162
|
**repo-relative** KEY=VALUE file (same format as `.env`, no shell evaluation)
|
|
153
163
|
that herdr injects into the peer's pane before the command runs — no `source`,
|
|
@@ -20,7 +20,7 @@ Claude Code ── Bash: coms-cli send/await ──▶ any pi peer (o
|
|
|
20
20
|
| Envelope CLI | `scripts/coms-cli.ts` | `list` / `send` / `await` / `reply` — any process becomes a coms participant. `send --await` is a blocking round trip; plain `send` prints a `msg_id` and a detached waiter holds the reply for `await`. |
|
|
21
21
|
| Stop hook | `hooks/coms-stop-hook.mjs` | PRIMARY completion path: writes each turn's final assistant message to `~/.pi/coms/claude-bridge/<pane>/last-message.json` (keyed by `HERDR_PANE_ID`). Exact text, no scraping. |
|
|
22
22
|
| Skill | `skills/peer-coms/SKILL.md` | Teaches Claude Code its peer role: discover with `coms-cli list`, ask with `send --await`, answer inbound prompts normally, never drive panes itself. |
|
|
23
|
-
| Runner | `runner: claude-code` in `.pi/agents/peers.yaml` | `just team
|
|
23
|
+
| Runner | `runner: claude-code` in `.pi/agents/peers.yaml` | `just fleet team` spawns the Claude CLI + its bridge in one pane (`_claude-peer` internally); `model:` maps to `claude --model`, and `just fleet resume` maps the Herdr-captured session id to `claude --resume`. |
|
|
24
24
|
|
|
25
25
|
## Setup
|
|
26
26
|
|
|
@@ -43,7 +43,7 @@ Claude Code ── Bash: coms-cli send/await ──▶ any pi peer (o
|
|
|
43
43
|
is a peer and how to use `coms-cli`.
|
|
44
44
|
|
|
45
45
|
3. **Spawn:** either add a `runner: claude-code` peer to a peers.yaml team and
|
|
46
|
-
`just team
|
|
46
|
+
`just fleet team <team> --no-hub`, or attach a bridge to an existing Herdr Claude pane:
|
|
47
47
|
|
|
48
48
|
```bash
|
|
49
49
|
node --experimental-strip-types scripts/coms-claude-bridge.ts --name claude-main
|
|
@@ -53,9 +53,9 @@ Claude Code ── Bash: coms-cli send/await ──▶ any pi peer (o
|
|
|
53
53
|
## Demo scenario (verified live)
|
|
54
54
|
|
|
55
55
|
```bash
|
|
56
|
-
just team
|
|
56
|
+
just fleet team docs --no-hub # Pi peers up
|
|
57
57
|
# pane with: bridge (claude-main) + claude
|
|
58
|
-
just hub
|
|
58
|
+
just fleet hub # in another pane: the orchestrator
|
|
59
59
|
# from the hub (or any shell):
|
|
60
60
|
node --experimental-strip-types scripts/coms-cli.ts send claude-main \
|
|
61
61
|
"Summarize the failing test output in artifacts/test.log" --await --timeout 300000
|
|
@@ -45,7 +45,7 @@ The loading mechanism uses a managed runtime contract at `$HOME/.local/state/age
|
|
|
45
45
|
Run these recipes from the repository root. The helper rejects unsafe scope, invalid paths, unsupported Codex versions, and mismatched singleton configuration.
|
|
46
46
|
|
|
47
47
|
```bash
|
|
48
|
-
just conductor
|
|
48
|
+
just fleet conductor codex setup docs --project af
|
|
49
49
|
```
|
|
50
50
|
|
|
51
51
|
The recipe resolves `codex`, the real repository root, and `$HOME/.pi/coms`, derives the isolated identity `codex-docs-conductor`, creates `$HOME/.local/state/agent-fleet/codex-conductor/workspace` outside the checkout and refreshes its owned contract copy with the absolute validated wrapper path. The lower-level `scripts/codex-remote-control.ts setup` command remains available for explicit integrations.
|
|
@@ -63,7 +63,7 @@ The unit is `Type=oneshot` with `RemainAfterExit=yes`, has no `Restart=` policy,
|
|
|
63
63
|
Pair the mobile client manually in an interactive operator TTY, after setup. Any displayed pairing code is short-lived secret material:
|
|
64
64
|
|
|
65
65
|
```bash
|
|
66
|
-
just conductor
|
|
66
|
+
just fleet conductor codex pair
|
|
67
67
|
```
|
|
68
68
|
|
|
69
69
|
Do not pipe, tee, capture, transcribe, screenshot, or commit the output. Never put pairing material or Codex credentials in the unit or config.
|
|
@@ -71,22 +71,22 @@ Do not pipe, tee, capture, transcribe, screenshot, or commit the output. Never p
|
|
|
71
71
|
### Start, status, and conductor launch
|
|
72
72
|
|
|
73
73
|
```bash
|
|
74
|
-
just conductor
|
|
75
|
-
just conductor
|
|
76
|
-
just conductor
|
|
74
|
+
just fleet conductor codex start
|
|
75
|
+
just fleet conductor codex status
|
|
76
|
+
just fleet conductor codex docs --project af
|
|
77
77
|
```
|
|
78
78
|
|
|
79
79
|
`status` reports only requested systemd state. Actual usability must be checked from the paired client, without inventing a network probe. The control pane similarly reports requested state only. Legacy `conductor-codex-pilot*` aliases remain available for the initial 0.144.x rollout.
|
|
80
80
|
|
|
81
|
-
### Use with `
|
|
81
|
+
### Use with `just fleet team` and Android
|
|
82
82
|
|
|
83
83
|
The service does not start peers. Launch a hub/team in the exact project stored by setup:
|
|
84
84
|
|
|
85
85
|
```bash
|
|
86
|
-
just
|
|
86
|
+
just fleet team docs --project af
|
|
87
87
|
```
|
|
88
88
|
|
|
89
|
-
Do not also run `just conductor
|
|
89
|
+
Do not also run `just fleet conductor codex docs --project af` for the same team unless a second peer set is intentional. The conductor mode is the alternative control-pane-plus-team layout when no Hub is needed.
|
|
90
90
|
|
|
91
91
|
In ChatGPT Android, open the paired Remote Control host and create a fresh thread using:
|
|
92
92
|
|
|
@@ -107,8 +107,8 @@ After confirmation, request approval for the exact wrapper send once.
|
|
|
107
107
|
### Stop, recovery, and reconfiguration
|
|
108
108
|
|
|
109
109
|
```bash
|
|
110
|
-
just conductor
|
|
111
|
-
just conductor
|
|
110
|
+
just fleet conductor codex stop
|
|
111
|
+
just fleet conductor codex recover
|
|
112
112
|
```
|
|
113
113
|
|
|
114
114
|
Use recovery when the unit says `active (exited)` but the paired client is unavailable, or when an `ExecStart` failure left the unit in `failed`. It is an explicit operator-confirmed systemd stop/reset/preflight/start path, not a health probe. Plain `start` still refuses `failed` and directs the operator to recovery or uninstall. Stop and emergency stop safely clear a confirmed `failed` state; other ambiguous states refuse rather than guessing.
|
|
@@ -116,7 +116,7 @@ Use recovery when the unit says `active (exited)` but the paired client is unava
|
|
|
116
116
|
To change the configured scope—or to upgrade an earlier in-checkout pilot runtime to the external user-state boundary—use `reconfigure` with the complete validated setup arguments, then explicitly stop/start as required. Do not edit the unit or config by hand:
|
|
117
117
|
|
|
118
118
|
```bash
|
|
119
|
-
just conductor
|
|
119
|
+
just fleet conductor codex reconfigure docs --project af
|
|
120
120
|
```
|
|
121
121
|
|
|
122
122
|
### Stale Codex send lock
|
|
@@ -145,7 +145,7 @@ If that capability is absent, restore a supported `0.144.x` CLI before stopping
|
|
|
145
145
|
Uninstall is explicit, operates only on the owned unit/config, accepts and clears a confirmed `failed` state, resets the loaded unit before deleting it, disables the service, reloads user systemd, and leaves Codex authentication and pairing state untouched:
|
|
146
146
|
|
|
147
147
|
```bash
|
|
148
|
-
just conductor
|
|
148
|
+
just fleet conductor codex uninstall
|
|
149
149
|
# After version drift, use the lower-level helper only if the exact current
|
|
150
150
|
# stop capability is proved:
|
|
151
151
|
node --experimental-strip-types scripts/codex-remote-control.ts uninstall \
|
|
@@ -15,7 +15,7 @@ Protocol contract for the Hermes ⇄ pi `coms` bridge. The first implemented dae
|
|
|
15
15
|
## user-remote topology
|
|
16
16
|
|
|
17
17
|
1. A pi peer sends a coms `prompt` envelope to `user-remote`.
|
|
18
|
-
2. The bridge derives `qid` from `prompt.msg_id`, formats the question, and runs `hermes send --to <target> <message>` (`<target>` defaults to `telegram`).
|
|
18
|
+
2. The bridge derives `qid` from `prompt.msg_id`, formats the question, and runs `hermes send --to <target> <message>` (`<target>` defaults to `telegram`). For a topic, copy the target accepted by `hermes send --list telegram`; depending on the Hermes output format, its `id` may already contain the `:<thread_id>` suffix, so do not append the thread twice.
|
|
19
19
|
3. The human replies in Telegram; the Hermes gateway/liaison writes the answer file.
|
|
20
20
|
4. The bridge polls the questions directory, validates the file, maps the answer, sends a coms `response` envelope, and removes the answer file.
|
|
21
21
|
|
|
@@ -32,6 +32,8 @@ Protocol contract for the Hermes ⇄ pi `coms` bridge. The first implemented dae
|
|
|
32
32
|
```text
|
|
33
33
|
❓ [HUB-Q:<qid>] <question>
|
|
34
34
|
|
|
35
|
+
📁 Project: <coms-project>
|
|
36
|
+
|
|
35
37
|
Context: <context, truncated if needed>
|
|
36
38
|
|
|
37
39
|
Options:
|
|
@@ -41,7 +43,7 @@ Options:
|
|
|
41
43
|
↩ Reply to this message, or type: HUB-Q:<qid>: <answer>
|
|
42
44
|
```
|
|
43
45
|
|
|
44
|
-
`Context:` is omitted when absent. `Options:` is omitted when no options are supplied. Context receives the remaining budget after the header, options, and reply instruction.
|
|
46
|
+
`Project:` is always present and comes from the bridge's validated `--project` scope, making simultaneous questions from different pools distinguishable. `Context:` is omitted when absent. `Options:` is omitted when no options are supplied. Context receives the remaining budget after the header, project, options, and reply instruction.
|
|
45
47
|
|
|
46
48
|
### Answer-file path, schema, and validation
|
|
47
49
|
|
|
@@ -93,12 +95,68 @@ Hermes can also act as the conductor without this daemon: use `coms-cli list` to
|
|
|
93
95
|
Launch a visible conductor workspace with:
|
|
94
96
|
|
|
95
97
|
```bash
|
|
96
|
-
just conductor docs
|
|
97
|
-
just conductor
|
|
98
|
+
just fleet conductor hermes docs # live conductor + team workspace
|
|
99
|
+
just fleet conductor hermes docs --dry-run # preview; no Herdr calls
|
|
98
100
|
```
|
|
99
101
|
|
|
100
102
|
The live recipe reuses `scripts/team-up.ts --conductor`: it creates a normal herdr workspace labeled `<worktree-tag>-conductor-<team>` (the tag is the last dot-segment of the checkout's basename, so the same team from a different worktree gets its own workspace), places a `conductor` pane running `hermes -p dev`, and tiles the chosen team beside it. Team peers keep their normal coms harness and herdr presence reporting, so they continue to show agent state in the sidebar; Hermes' own herdr-agent-state plugin is responsible for the conductor pane's state.
|
|
101
103
|
|
|
104
|
+
### `/set-hermes-telegram` bridge control
|
|
105
|
+
|
|
106
|
+
The outbound `hermes send` path needs a configured Telegram channel but no skill. Full reply round-trip additionally needs Agent Fleet's `hub-liaison` skill in the profile that owns the running Telegram gateway. From Pi or Claude Code use:
|
|
107
|
+
|
|
108
|
+
```text
|
|
109
|
+
/set-hermes-telegram status --profile default
|
|
110
|
+
/set-hermes-telegram install --profile default
|
|
111
|
+
/set-hermes-telegram install --profile default --force --restart
|
|
112
|
+
/set-hermes-telegram on 7883056502:1735 --profile default
|
|
113
|
+
/set-hermes-telegram off 7883056502:1735
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
OpenCode exposes `/af-set-hermes-telegram`; the arguments and backend are identical. The deterministic CLI can also be called directly with `agent-fleet set-hermes-telegram ...`.
|
|
117
|
+
|
|
118
|
+
#### `status` and profile resolution
|
|
119
|
+
|
|
120
|
+
`status` is read-only. It verifies the Hermes executable/profile, compares the complete installed `hub-liaison` tree to the version packaged with Agent Fleet, asks Hermes whether the skill is enabled, checks `terminal` and `file` toolsets for the `telegram` platform, and reports gateway state. `--profile <name>` is recommended. Without it the controller selects a profile only when `hermes gateway list` reports exactly one running gateway; zero or multiple running gateways fail closed and require an explicit profile.
|
|
121
|
+
|
|
122
|
+
#### `install`
|
|
123
|
+
|
|
124
|
+
`install` writes to `<Hermes-profile-path>/skills/hub-liaison`, where the profile path comes from `hermes profile show <name>` (important because the `default` profile is normally `~/.hermes`, while named profiles normally live below `~/.hermes/profiles/`). Installation behavior is:
|
|
125
|
+
|
|
126
|
+
- missing skill: copied atomically from the packaged Agent Fleet source;
|
|
127
|
+
- byte-identical tree: no-op;
|
|
128
|
+
- differing tree: refused unless `--force` is explicit;
|
|
129
|
+
- forced replacement: the previous tree is moved first to `<profile>/backups/agent-fleet/hub-liaison-<timestamp>`;
|
|
130
|
+
- symlinks or unsupported filesystem entries in either skill tree are refused;
|
|
131
|
+
- the installed tree is fingerprinted again, then `hermes --profile <name> skills list --enabled-only` and `tools list --platform telegram` are run for verification.
|
|
132
|
+
|
|
133
|
+
The command does not silently broaden Telegram tool permissions. If `terminal` or `file` is disabled, it prints the explicit remediation:
|
|
134
|
+
|
|
135
|
+
```bash
|
|
136
|
+
hermes --profile <name> tools enable --platform telegram terminal file
|
|
137
|
+
```
|
|
138
|
+
|
|
139
|
+
If the skill itself is disabled, use `hermes --profile <name> skills config`. A running gateway is restarted only with explicit `--restart`; otherwise the command prints the required restart command. A stopped gateway is never started as a side effect. No install/status/on/off action sends a test Telegram message.
|
|
140
|
+
|
|
141
|
+
#### `on` and `off`
|
|
142
|
+
|
|
143
|
+
`on` fails before touching Herdr unless the selected gateway is running, `hub-liaison` is current and enabled, and both required Telegram toolsets are enabled. It then closes any existing pane labeled `hermes-bridge` in the current workspace, creates a new right-hand pane in that **same Herdr workspace**, labels it `hermes-bridge`, and starts the daemon with `telegram:<id>` as its exact target. The selected profile is forwarded as `--hermes-profile`, so every question, timeout, cancel, and late-answer send executes as `hermes --profile <name> send ...` rather than silently falling back to Hermes' sticky default. `off` remains available even when Hermes readiness is broken, closes the bridge pane, creates nothing, and is idempotent.
|
|
144
|
+
|
|
145
|
+
The Telegram destination must contain digits only (`<chat_id>`) or two digit groups separated by one colon (`<chat_id>:<topic_id>`). Values such as `telegram:123`, `123:`, `123:456:789`, spaces, signs, and letters are rejected. The controller infers the coms project independently from the current hub process's explicit `--project`, then `PI_COMS_PROJECT`, then `default`.
|
|
146
|
+
|
|
147
|
+
The manual equivalent is:
|
|
148
|
+
|
|
149
|
+
```bash
|
|
150
|
+
node --experimental-strip-types scripts/coms-hermes-bridge.ts \
|
|
151
|
+
--project af \
|
|
152
|
+
--hermes-profile default \
|
|
153
|
+
--timeout 1800000 \
|
|
154
|
+
--to 'telegram:<chat_id>:<thread_id>'
|
|
155
|
+
just fleet team docs --project af
|
|
156
|
+
```
|
|
157
|
+
|
|
158
|
+
Repeated value flags such as two `--to` arguments are rejected at startup rather than silently selecting one destination. The `ask-user-remote` wrapper resolves the explicit Pi `--project` flag when the tool executes, so non-default hubs discover `user-remote` in their own pool.
|
|
159
|
+
|
|
102
160
|
Hard boundary: the Hermes conductor must not run `herdr` commands, drive panes, create/kill workspaces, or manage fleet lifecycle. Herdr driving stays with the human/orchestrator so the damage-control model remains intact; see `.pi/damage-control-rules.yaml` for the authoritative no-herdr boundary. Hermes may only operate inside the project coms pool through the documented coms CLI commands.
|
|
103
161
|
|
|
104
162
|
## Hermes and the experimental Codex conductor
|
package/docs/getting-started.md
CHANGED
|
@@ -24,10 +24,10 @@ Linux/pi fleet users can pair Codex Remote Control with ChatGPT Android and dele
|
|
|
24
24
|
|
|
25
25
|
```bash
|
|
26
26
|
cd /path/to/agent-fleet
|
|
27
|
-
just conductor
|
|
28
|
-
just conductor
|
|
29
|
-
just conductor
|
|
30
|
-
just
|
|
27
|
+
just fleet conductor codex setup docs --project af
|
|
28
|
+
just fleet conductor codex pair
|
|
29
|
+
just fleet conductor codex start
|
|
30
|
+
just fleet team docs --project af
|
|
31
31
|
```
|
|
32
32
|
|
|
33
33
|
The runtime contract is generated under `$HOME/.local/state/agent-fleet/codex-conductor/`, outside the checkout. Pairing is interactive secret-bearing output and must never be captured. Read the complete [Codex conductor runbook](codex-remote-conductor.md) before enabling the service.
|
package/docs/opencode-setup.md
CHANGED
|
@@ -101,6 +101,7 @@ This repo ships OpenCode-native commands with an `af-` prefix so they are easy t
|
|
|
101
101
|
- `/af-prime`
|
|
102
102
|
- `/af-setup-agent-fleet`
|
|
103
103
|
- `/af-doctor-agent-fleet`
|
|
104
|
+
- `/af-set-hermes-telegram install|status|on|off …` — profile-aware Hermes liaison setup and bridge control
|
|
104
105
|
|
|
105
106
|
These commands are optional shortcuts. The agent can still invoke the correct skills automatically from plain natural-language requests.
|
|
106
107
|
|
package/docs/pi-extensions.md
CHANGED
|
@@ -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
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
**`.pi/harnesses/`** — a directory pi does
|
|
50
|
-
run
|
|
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,13 +57,13 @@ 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
|
|
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
|
|
65
65
|
into `.pi/extensions/`, and never load all of them at once. The supported multi-harness
|
|
66
|
-
exception is loading
|
|
66
|
+
exception is loading `damage-control-continue` and `ask-user-remote` before `agent-hub` for a guarded hub session (see
|
|
67
67
|
[pi-setup.md](pi-setup.md#optional-pi-extensions)).
|
|
68
68
|
|
|
69
69
|
---
|
|
@@ -71,15 +71,20 @@ exception is loading a damage-control variant before `agent-hub` for a guarded h
|
|
|
71
71
|
## Setup
|
|
72
72
|
|
|
73
73
|
```bash
|
|
74
|
-
just install
|
|
75
|
-
just
|
|
76
|
-
just
|
|
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
|
|
82
|
-
|
|
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,15 +92,44 @@ 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:
|
|
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 |
|
|
92
|
-
| [damage-control](../.pi/harnesses/damage-control/README.md) | Safety |
|
|
93
|
-
| [
|
|
94
|
-
| [
|
|
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
|
|
|
104
|
+
### Migration: retired hard-stop harness
|
|
105
|
+
|
|
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,
|
|
108
|
+
setup-recorded copy (or an agent-fleet source symlink), preserves user-modified/unowned copies,
|
|
109
|
+
and refreshes the managed `justfile` region. Use `damage-control-continue` for standalone and
|
|
110
|
+
Agent Hub safety; missing child safety now fails closed instead of falling back or spawning
|
|
111
|
+
unguarded.
|
|
112
|
+
|
|
113
|
+
### Harness version footer and provenance
|
|
114
|
+
|
|
115
|
+
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
|
+
default status footer, that shared key gives a supported stack exactly one version instead of one
|
|
118
|
+
copy per harness. `agent-hub` replaces the default footer: it does **not** consume that status
|
|
119
|
+
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
|
+
version exactly once.
|
|
122
|
+
|
|
123
|
+
The shared version status is independent of mutable owner status: for example, a
|
|
124
|
+
Damage-Control violation can replace its own safety message without overwriting the version
|
|
125
|
+
entry. The canonical value is the root `package.json` version. During a release,
|
|
126
|
+
`bin/sync-harness-versions.js` stamps that value into each adjacent persistent-harness
|
|
127
|
+
`package.json` after the root bump and before lockfile finalization and snapshotting. Each
|
|
128
|
+
harness keeps a local `version.ts` provenance reader so copied or symlinked harness directories
|
|
129
|
+
resolve their adjacent stamp rather than the launch directory. That local provenance does not
|
|
130
|
+
make a harness self-contained: copied target harnesses still require the existing full
|
|
131
|
+
`.pi/harnesses/` dependency installation described in [Setup](#setup).
|
|
132
|
+
|
|
99
133
|
### `agent-hub` components
|
|
100
134
|
|
|
101
135
|
`agent-hub` is the consolidated orchestration harness. It replaces the retired standalone
|
|
@@ -119,22 +153,28 @@ harnesses:
|
|
|
119
153
|
- **Persona gate** — requires an orchestrator persona at startup unless disabled in the local
|
|
120
154
|
override file; the chosen persona also feeds the coms purpose when no explicit `--purpose` is set.
|
|
121
155
|
- **Operator controls** — `/zoom` timeline inspection plus child-agent kill/restart controls.
|
|
122
|
-
- **Damage-control + ask_user by default** — `just hub`
|
|
156
|
+
- **Damage-control + ask_user by default** — `just fleet hub` and `just fleet hub --solo` load the
|
|
123
157
|
`damage-control-continue` safety harness and `ask-user-remote` before `agent-hub`, so the
|
|
124
158
|
dispatcher's tool calls are checked against the rules file and the `askUserAvailable` probe sees
|
|
125
159
|
`ask_user`. A blocked call feeds back and the turn keeps going rather than aborting. `agent-hub` also
|
|
126
|
-
re-loads
|
|
127
|
-
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
decides — deny / once / this agent / all agents. Destructive bash patterns are never exemptible.
|
|
160
|
+
re-loads `damage-control-continue` into every native specialist, research helper, and nested
|
|
161
|
+
delegate (via an explicit `-e` that survives `--no-extensions`). Protected-path access can be
|
|
162
|
+
granted at runtime: `/allow <pattern> [turn|session]` in the hub pre-authorizes, a parent-session
|
|
163
|
+
block opens an approval dialog, and a headless child escalates to the hub. Protected deletion
|
|
164
|
+
offers only deny/once; other protected paths may be scoped to an agent or session. Denial and
|
|
165
|
+
timeout fail closed without aborting the child turn. Destructive bash patterns are never exemptible,
|
|
166
|
+
and a missing continue harness refuses child dispatch.
|
|
134
167
|
- **Embedded coms** — peer discovery, `coms_list` / `coms_send` / `coms_get` / `coms_await`,
|
|
135
168
|
`/handoff`, and peer-as-subagent flows.
|
|
136
|
-
- **Solo mode** — `just hub
|
|
169
|
+
- **Solo mode** — `just fleet hub --solo` keeps the dispatcher grid, delegation, research helpers, persona
|
|
137
170
|
gate, and controls, but starts without the embedded coms layer.
|
|
171
|
+
- **Optional Hermes local monitor transport** — uses `AGENT_FLEET_PROFILE_ID`, the absolute
|
|
172
|
+
`AGENT_FLEET_MONITOR_RUNTIME_DIR`, and the Herdr `HERDR_WORKSPACE_ID` and `HERDR_PANE_ID`
|
|
173
|
+
required to establish its stable hub identity. It is a source-owned, local-only transport—not a
|
|
174
|
+
Hermes SDK task/lifecycle RPC or a bundled plugin—and fails closed without validated owner-only
|
|
175
|
+
discovery, lease, token, and socket state. Follow the
|
|
176
|
+
[Hermes integration guide](../hermes/README.md#local-agent-hub-monitor-integration) for startup,
|
|
177
|
+
wire examples, cancellation semantics, and reconnect behavior.
|
|
138
178
|
|
|
139
179
|
---
|
|
140
180
|
|
|
@@ -173,7 +213,7 @@ The `justfile` sets `dotenv-load`, so a `.env` file at the repo root is auto-loa
|
|
|
173
213
|
| `AZURE_SPEECH_KEY` | `pi-voice-stt` (azure backend) | Azure Speech resource key |
|
|
174
214
|
| `AZURE_SPEECH_ENDPOINT` | `pi-voice-stt` (azure backend) | Azure resource endpoint, used when `provider.endpoint` is unset |
|
|
175
215
|
| `PI_STT_CONFIG` / `PI_STT_KEYBIND` | `pi-voice-stt` | Override config (inline JSON or path) / the record hotkey (default `alt+s`) |
|
|
176
|
-
| `AGENT_FLEET_SPAWN_DELAY` | `_peer` / `_peer-plus` recipes | Seconds to sleep before launching pi in a fleet pane (set per pane by `team
|
|
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) |
|
|
177
217
|
|
|
178
218
|
The `chrome-devtools-mcp` server starts once at extension load, so changing its vars needs a pi
|
|
179
219
|
restart / `/reload` to take effect.
|
|
@@ -183,7 +223,7 @@ restart / `/reload` to take effect.
|
|
|
183
223
|
pi loads its credential store (`~/.pi/agent/auth.json`) once at boot under a short-retry
|
|
184
224
|
file lock. When the stored OAuth token is stale, the first pi to boot refreshes it over
|
|
185
225
|
the network *while holding that lock*; sibling panes spawned in the same instant (as
|
|
186
|
-
`just team
|
|
226
|
+
`just fleet team` / `just fleet resume` do) lose the lock race and come up
|
|
187
227
|
with every provider showing **unconfigured**. To dodge this, the team scripts check
|
|
188
228
|
`auth.json` before spawning (only `type`/`expires` are read — values never leave the
|
|
189
229
|
process): if any OAuth credential is expired or about to expire, one pi pane (the hub
|
|
@@ -205,11 +245,11 @@ These ported files are runtime dependencies of the extensions above:
|
|
|
205
245
|
The earlier `reviewer` and `red-team` personas were folded into `code-reviewer` and
|
|
206
246
|
`security-auditor`; the remaining team/peer configs already reference the canonical names.
|
|
207
247
|
A peer entry may carry an optional `extensions:` field (comma-separated names under
|
|
208
|
-
`.pi/extensions/`) —
|
|
248
|
+
`.pi/extensions/`) — Fleet's team launcher then routes it through the `_peer-plus` recipe so those
|
|
209
249
|
extensions load into the peer process. The `web-debugger` peer uses this to get
|
|
210
250
|
`chrome-devtools-mcp`'s `chrome_devtools__*` tools (see the two-browser-stacks section above).
|
|
211
251
|
- **`.pi/damage-control-rules.yaml`** — the destructive-command / protected-path rule set
|
|
212
|
-
for `damage-control`.
|
|
252
|
+
for `damage-control-continue`.
|
|
213
253
|
- **`.pi/skills/bowser/`** — a pi-runtime skill for headless Playwright browser
|
|
214
254
|
automation, used by the `bowser` agent persona. Kept separate from the core
|
|
215
255
|
engineering `skills/`. It drives the external **Playwright Agent CLI**
|