@chankov/agent-fleet 2.0.21 → 2.0.22
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/.pi/harnesses/agent-hub/README.md +10 -0
- package/.pi/harnesses/agent-hub/acceptance.ts +2 -1
- package/.pi/harnesses/agent-hub/damage-guard-hub.ts +7 -2
- package/.pi/harnesses/agent-hub/dispatch-native-spawn.ts +3 -1
- package/.pi/harnesses/agent-hub/external-blocker.js +9 -2
- package/.pi/harnesses/agent-hub/no-progress.ts +4 -2
- package/.pi/harnesses/agent-hub/package.json +1 -1
- package/.pi/harnesses/agent-hub/runtime-test-check.ts +16 -2
- package/.pi/harnesses/agent-hub/tools/dispatch-execution.ts +3 -2
- package/.pi/harnesses/coms/package.json +1 -1
- package/.pi/harnesses/damage-control-continue/index.ts +2 -2
- package/.pi/harnesses/damage-control-continue/package.json +1 -1
- package/.pi/harnesses/damage-control-continue/system1-child.ts +16 -6
- package/.pi/harnesses/lib/bash-policy-analysis.ts +31 -1
- package/.versions/2.0.22/.pi/agent-fleet/hermes/README.md +347 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-herdr/plugin.js +1291 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-herdr/presentation.js +672 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-monitor/plugin.js +19 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/desktop-plugins/agent-fleet-monitor/state.js +10 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/gates/gate-o-capability.md +8 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/gates/gate-o-validator-fixtures.json +1 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/activity.py +773 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/coms_registry.py +134 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/coms_send.py +350 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/herdr_source.py +193 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/manifest.json +4 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/plugin_api.py +444 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/sessions.py +205 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/tasks.py +300 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/dashboard/watch.py +819 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/plugins/agent-fleet-herdr/plugin.yaml +8 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/plugins/agent-fleet-monitor/dashboard/adapter.py +139 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/plugins/agent-fleet-monitor/dashboard/manifest.json +11 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/plugins/agent-fleet-monitor/dashboard/plugin_api.py +50 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/skills/hub-conductor/SKILL.md +84 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/skills/hub-liaison/SKILL.md +84 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/skills/hub-watchdog/SKILL.md +76 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/skills/hub-watchdog/manifest.json +1 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog.py +249 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_actions.py +124 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_contract.py +76 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_delivery.py +10 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_engine.py +128 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_judgment.py +41 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_recovery.py +103 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_state.py +163 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/skills/hub-watchdog/scripts/watchdog_transport.py +138 -0
- package/.versions/2.0.22/.pi/agent-fleet/hermes/watchdog-tests/__init__.py +0 -0
- package/.versions/2.0.22/.pi/agent-fleet/hooks/coms-stop-hook.mjs +84 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/claude-code-preflight.ts +70 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/coms-claude-bridge.ts +437 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/coms-cli.ts +425 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/coms-hermes-bridge.ts +413 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/fleet-codex-client.ts +69 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/fleet-codex-read.py +148 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/fleet.ts +217 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/flow.ts +157 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/hermes-monitor-capability-runner.ts +25 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/hermes-monitor-scenario.ts +474 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/hermes-watchdog-capability-probe.ts +45 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/install-hermes-plugin.sh +180 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/claude-bridge-core.ts +208 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/coms-envelope.ts +582 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/fake-herdr-server.ts +88 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/fleet-codex-catalog.ts +63 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/fleet-codex-operations.ts +190 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/fleet-codex-session.ts +166 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/fleet-codex-transport.ts +124 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/fleet-command.ts +252 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/flow-command.ts +98 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/flow-maintenance.ts +230 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/herdr-layout.ts +281 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/hermes-bridge-core.ts +241 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/hermes-monitor-events.ts +1 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/hermes-monitor-herdr.ts +2 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/hermes-monitor-model.ts +3 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/hermes-monitor-registry.ts +2 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/hermes-monitor-socket.ts +2 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/hermes-monitor-store.ts +2 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/monitor-env.ts +146 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/peer-launch.ts +318 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/persona-banner.ts +62 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/persona-dirs.ts +25 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/runtime-dependencies.js +124 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/spawn-stagger.ts +101 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/team-project.ts +178 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/lib/team-snapshot.ts +147 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/package-lock.json +35 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/package.json +9 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/peer-banner.ts +41 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/peer-launch.ts +283 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/team-snapshot.ts +237 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/team-up.ts +378 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/agent-phase.ts +179 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/changes.ts +61 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/debate.ts +149 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/env.ts +34 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/envelopes.ts +169 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/gates.ts +81 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/git.ts +96 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/isolated-snapshot.ts +125 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/merge.ts +95 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/model-profile.ts +22 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/model-visibility.ts +92 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/permissions.ts +130 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/personas.ts +57 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/poll.ts +86 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/project-policy.ts +36 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/quality.ts +64 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/run.ts +108 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/scout-data-boundary.ts +55 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/trace.ts +34 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/voices.ts +128 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/lib/writer-lease.ts +112 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/tsconfig.json +22 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/wf-build-test.ts +61 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/wf-debate.ts +87 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/wf-document.ts +50 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/wf-poll.ts +95 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/wf-quality.ts +20 -0
- package/.versions/2.0.22/.pi/agent-fleet/scripts/workflows/wf-scout.ts +40 -0
- package/.versions/2.0.22/.pi/agents/dispatch-policy.yaml +32 -0
- package/.versions/2.0.22/.pi/agents/model-profiles.yaml +134 -0
- package/.versions/2.0.22/.pi/agents/peers.yaml +147 -0
- package/.versions/2.0.22/.pi/agents/teams.yaml +41 -0
- package/.versions/2.0.22/.pi/agents/voices.yaml +13 -0
- package/.versions/2.0.22/.pi/damage-control-rules.yaml +297 -0
- package/.versions/2.0.22/.pi/extensions/btw/README.md +120 -0
- package/.versions/2.0.22/.pi/extensions/btw/index.ts +914 -0
- package/.versions/2.0.22/.pi/extensions/btw/package.json +6 -0
- package/.versions/2.0.22/.pi/extensions/btw/state.js +179 -0
- package/.versions/2.0.22/.pi/extensions/chrome-devtools-mcp/README.md +55 -0
- package/.versions/2.0.22/.pi/extensions/chrome-devtools-mcp/index.ts +93 -0
- package/.versions/2.0.22/.pi/extensions/chrome-devtools-mcp/package.json +6 -0
- package/.versions/2.0.22/.pi/extensions/compact-and-continue/README.md +42 -0
- package/.versions/2.0.22/.pi/extensions/compact-and-continue/index.ts +136 -0
- package/.versions/2.0.22/.pi/extensions/compact-and-continue/package.json +6 -0
- package/.versions/2.0.22/.pi/extensions/mcp-bridge/README.md +46 -0
- package/.versions/2.0.22/.pi/extensions/mcp-bridge/index.ts +206 -0
- package/.versions/2.0.22/.pi/extensions/mcp-bridge/package.json +6 -0
- package/.versions/2.0.22/.pi/extensions/package-lock.json +1175 -0
- package/.versions/2.0.22/.pi/extensions/package.json +9 -0
- package/.versions/2.0.22/.pi/extensions/pi-voice-stt/README.md +224 -0
- package/.versions/2.0.22/.pi/extensions/pi-voice-stt/config.ts +198 -0
- package/.versions/2.0.22/.pi/extensions/pi-voice-stt/examples/stt.json +35 -0
- package/.versions/2.0.22/.pi/extensions/pi-voice-stt/index.ts +248 -0
- package/.versions/2.0.22/.pi/extensions/pi-voice-stt/package.json +6 -0
- package/.versions/2.0.22/.pi/extensions/pi-voice-stt/providers.ts +214 -0
- package/.versions/2.0.22/.pi/extensions/pi-voice-stt/recorder.ts +158 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/README.md +1527 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/acceptance.ts +200 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/access-approval.ts +141 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/action-authorization.ts +10 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/agentic-contract.ts +43 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/agentic-evidence.ts +64 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/agentic-hub.ts +54 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/agentic-runtime.ts +56 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/agentic-sources-worker.mjs +4 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/agentic-sources.ts +74 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/agentic-state.ts +23 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/approval-wait.ts +1 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/artifacts.js +146 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/assertion-ledger.js +67 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/assist-profile.ts +19 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/backend-policy.js +174 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/bounded-output.ts +26 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/budget-recovery.ts +123 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/capability-confirmation.ts +47 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/capability-packs.ts +184 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/agent-model-thinking.ts +10 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/agent-model.ts +10 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/agent-models-substitute.ts +10 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/agents-add.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/agents-drop.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/agents-history.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/agents-kill.ts +10 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/agents-list.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/agents-restart.ts +10 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/agents-save.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/agents-team.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/audit.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/compound.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/coms.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/context-command.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/context.ts +46 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/debate.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/dispatch-policy.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/handoff.ts +10 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/hub-report.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/models.ts +10 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/poll.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/recover.ts +61 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/retry.ts +10 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/task-triage-recover.ts +12 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/task-triage-waive.ts +12 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/watchdog.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/work-mode.ts +29 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/commands/zoom.ts +10 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/config/agents.ts +178 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/config/model-profiles.ts +237 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/config/overrides.ts +165 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context/agent-state.ts +30 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context/assertions-artifacts.ts +221 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context/budgets.ts +152 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context/hub-state.ts +40 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context-budget-snapshot.ts +105 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context-compaction-monitor.ts +35 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context-compaction-preflight.ts +21 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context-compaction-runtime.ts +69 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context-compaction.ts +34 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context-continuity-broker.ts +42 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context-continuity-child.ts +83 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context-continuity-client.ts +19 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context-continuity-compat.ts +30 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context-continuity-owners.ts +15 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context-continuity-registry.ts +8 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context-continuity.ts +82 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context-pressure.ts +222 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/context-window.js +108 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/damage-guard-approval.ts +59 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/damage-guard-broker.ts +125 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/damage-guard-contract.ts +22 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/damage-guard-descendant.ts +76 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/damage-guard-hub.ts +254 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/damage-guard-identity.ts +12 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/damage-guard-owners.ts +54 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/damage-guard-state.ts +43 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/damage-guard-test-tsconfig.json +19 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/debate-command.ts +176 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/delegate.ts +478 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/deterministic-fs.ts +195 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/diagnostic-probe-extension.ts +26 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/diagnostic-series-budget.ts +178 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/dispatch-coms.ts +253 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/dispatch-core.ts +27 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/dispatch-native-complete.ts +173 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/dispatch-native-prepare.ts +295 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/dispatch-native-spawn.ts +255 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/dispatch-native-types.ts +293 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/dispatch-native.ts +236 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/dispatch-observability.ts +225 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/dispatch-triage-contract.ts +27 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/dispatch-triage-eval.ts +77 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/dispatch-triage-policy.ts +29 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/dispatch-triage-runtime.ts +55 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/dispatch-triage-state.ts +33 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/docs-lane.js +123 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/drift-judge.ts +352 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/drift-runtime.ts +480 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/drift-system1-policy.ts +39 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/drift-system1.ts +469 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/drift-watchdog.js +349 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/evidence-manifest.ts +51 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/evidence-rules.js +96 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/execution-evidence.ts +80 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/execution-trace.ts +241 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/external-blocker.js +92 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/adapters.ts +88 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/broker-client.ts +62 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/broker.ts +128 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/child-extension.ts +42 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/descendant.ts +67 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/discovery-worker.mjs +15 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/discovery.ts +126 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/evaluate.ts +57 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/hub.ts +169 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/native-context.ts +8 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/native-fixture.test-support.ts +108 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/owners.ts +96 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/results.ts +55 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/runtime.ts +130 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/semantic-profiles.ts +18 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/sources.ts +69 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/file-discovery/state.ts +22 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/filesystem-tool.ts +166 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/fixtures/registration-surface.json +66 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/fixtures/t0a-synthetic/catalog.ts +189 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/footer.ts +30 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/helpers.ts +270 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/history-projection.ts +116 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/hub-state-audit.js +41 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/index.ts +2616 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/input/completions.ts +82 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/input/shortcuts.ts +20 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/lifecycle/context-pressure.ts +231 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/lifecycle/monitor-session.ts +104 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/lifecycle/session-orchestration.ts +144 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/lifecycle/turn-handlers.ts +90 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/monitor-control.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/monitor-invoke-journal.ts +131 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/monitor-invoke.ts +92 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/monitor-lifecycle.ts +13 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/monitor-publisher.ts +59 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/monitor-recovery.ts +3 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/monitor-runtime.ts +3 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/monitor-session-bridge.ts +266 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/no-progress.ts +622 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/operator-watchdog.ts +97 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/orchestration-activation.ts +109 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/orchestration-metrics.ts +78 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/orchestration-route.ts +68 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/package.json +7 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/peer-spawn-plan.ts +116 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/policy/models.ts +153 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/policy/profile-activation.ts +62 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/policy/profile-runtime.ts +120 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/policy/roster.ts +94 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/policy/work-mode.ts +142 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/poll-command.ts +176 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/presentation.ts +48 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/proactive-config.ts +21 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/proactive-evaluate.ts +138 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/proactive-external-git.ts +82 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/proactive-external.ts +142 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/proactive-feedback.ts +104 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/proactive-findings.ts +115 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/proactive-local.ts +89 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/proactive-observer.ts +106 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/proactive-rules.ts +171 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/proactive-runtime.ts +318 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/proactive-selection.ts +68 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/proactive-snapshot-worker.mjs +12 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/proactive-snapshot.ts +271 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/proactive-types.ts +67 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/process-obligations.ts +159 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/prompts/context.ts +55 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/prompts/fragments.ts +86 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/prompts/session-start.ts +90 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/prompts/system-prompt.ts +125 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/provider-semaphore.js +138 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/reconcile.ts +26 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/recover-policy.ts +44 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/recover-state.ts +104 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/recovery-contract.ts +151 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/rerun-policy.ts +40 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/research/controls.ts +74 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/research/runtime.ts +215 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/research/spawn-run.ts +221 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/research-watchdog.ts +40 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/return-contract.js +349 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/return-extract.js +77 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/review-closure.ts +43 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/review-continuity.ts +73 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/review-findings.js +96 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/review-reuse.ts +47 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/routing-observation.ts +41 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/routing-proposal.ts +46 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/run-budget.js +342 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/run-namespace.js +93 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/runtime-test-check.ts +68 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/safety-routing.ts +22 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/scope-gate.js +228 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/session-audit.ts +331 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/session-health.js +110 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/session-start.ts +42 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/spawn.ts +639 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/specialist-result-receipt.ts +13 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/specialist-result.ts +69 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/system1-activity.ts +625 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/system1-communication-store.ts +217 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/system1-report.ts +275 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/system1-runtime.ts +265 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/task-continuation.ts +4 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/task-resume-contract.ts +70 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/task-triage-authorization.ts +151 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/task-triage-config.ts +20 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/task-triage-contract.ts +14 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/task-triage-live-stage-boundary.mjs +49 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/task-triage-obligations.ts +120 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/task-triage-policy.ts +16 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/task-triage-review-contract.mjs +43 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/task-triage-reviewer-only-contract.mjs +156 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/task-triage-reviewer-only-diagnostics.mjs +112 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/task-triage-runtime.ts +130 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/task-triage-stage-guard.ts +21 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/task-triage-state.ts +46 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/timeline.ts +72 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tool-catalog-runtime.ts +79 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tool-catalog-state.ts +123 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tool-protocol.ts +134 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tools/action-executors.ts +214 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tools/ask-system1-files.ts +15 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tools/ask-system1.ts +25 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tools/coms-tools.ts +139 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tools/context.ts +144 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tools/dispatch-agent.ts +88 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tools/dispatch-execution.ts +641 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tools/dispatch-triage.ts +16 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tools/execution-orchestration.ts +22 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tools/fleet-tools.ts +200 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tools/herdr-executors.ts +95 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tools/run-flow.ts +136 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tools/set-task-tier.ts +31 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tools/spawn-research.ts +67 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tools/team-adjust.ts +29 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tools/verification-contract.ts +80 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/tsconfig.json +22 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/types.ts +66 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/ui/activity-dots.ts +25 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/ui/context-budget.ts +89 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/ui/detail-panel.ts +192 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/ui/fleet-actions.ts +78 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/ui/fleet-dashboard.ts +155 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/ui/fleet-editor.ts +44 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/ui/fleet-source.ts +179 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/ui/grid.ts +159 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/ui/history-store.ts +137 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/ui/history.ts +234 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/ui/pool.ts +103 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/ui/running-strip.ts +2 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/ui/system1-communication.ts +59 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/ui/zoom.ts +206 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/unknown-tool-counter.ts +116 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/version.ts +42 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/watchdog-evaluation.ts +110 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/work-mode-controls.ts +56 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/work-mode.ts +186 -0
- package/.versions/2.0.22/.pi/harnesses/agent-hub/write-isolation.ts +187 -0
- package/.versions/2.0.22/.pi/harnesses/ask-user-remote/README.md +59 -0
- package/.versions/2.0.22/.pi/harnesses/ask-user-remote/index.ts +569 -0
- package/.versions/2.0.22/.pi/harnesses/ask-user-remote/questions.ts +159 -0
- package/.versions/2.0.22/.pi/harnesses/ask-user-remote/race-core.js +124 -0
- package/.versions/2.0.22/.pi/harnesses/ask-user-remote/runtime-ask.ts +83 -0
- package/.versions/2.0.22/.pi/harnesses/coms/README.md +100 -0
- package/.versions/2.0.22/.pi/harnesses/coms/index.ts +285 -0
- package/.versions/2.0.22/.pi/harnesses/coms/package.json +7 -0
- package/.versions/2.0.22/.pi/harnesses/coms/version.ts +42 -0
- package/.versions/2.0.22/.pi/harnesses/damage-control-continue/README.md +161 -0
- package/.versions/2.0.22/.pi/harnesses/damage-control-continue/index.ts +600 -0
- package/.versions/2.0.22/.pi/harnesses/damage-control-continue/package.json +7 -0
- package/.versions/2.0.22/.pi/harnesses/damage-control-continue/result-screen.ts +98 -0
- package/.versions/2.0.22/.pi/harnesses/damage-control-continue/system1-child.ts +45 -0
- package/.versions/2.0.22/.pi/harnesses/damage-control-continue/system1-client.ts +85 -0
- package/.versions/2.0.22/.pi/harnesses/damage-control-continue/system1-guard.ts +65 -0
- package/.versions/2.0.22/.pi/harnesses/damage-control-continue/version.ts +42 -0
- package/.versions/2.0.22/.pi/harnesses/lib/approval-wait.ts +17 -0
- package/.versions/2.0.22/.pi/harnesses/lib/bash-policy-analysis.ts +185 -0
- package/.versions/2.0.22/.pi/harnesses/lib/changed-file-diagnostics.ts +642 -0
- package/.versions/2.0.22/.pi/harnesses/lib/clarification-policy.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/lib/coms-core-io.ts +413 -0
- package/.versions/2.0.22/.pi/harnesses/lib/coms-core.ts +680 -0
- package/.versions/2.0.22/.pi/harnesses/lib/coms-registry-entry.ts +96 -0
- package/.versions/2.0.22/.pi/harnesses/lib/context-budget-child-prompt.ts +214 -0
- package/.versions/2.0.22/.pi/harnesses/lib/context-budget-hub-prompt.ts +121 -0
- package/.versions/2.0.22/.pi/harnesses/lib/context-budget-view.ts +112 -0
- package/.versions/2.0.22/.pi/harnesses/lib/context-budget.ts +114 -0
- package/.versions/2.0.22/.pi/harnesses/lib/context-compaction-policy.js +35 -0
- package/.versions/2.0.22/.pi/harnesses/lib/damage-action-hash.ts +28 -0
- package/.versions/2.0.22/.pi/harnesses/lib/damage-control-shared.ts +229 -0
- package/.versions/2.0.22/.pi/harnesses/lib/damage-guard-port.ts +25 -0
- package/.versions/2.0.22/.pi/harnesses/lib/damage-result-evidence.ts +25 -0
- package/.versions/2.0.22/.pi/harnesses/lib/damage-result-view.ts +16 -0
- package/.versions/2.0.22/.pi/harnesses/lib/deterministic-handle-path.ts +25 -0
- package/.versions/2.0.22/.pi/harnesses/lib/execution-trace.ts +45 -0
- package/.versions/2.0.22/.pi/harnesses/lib/fixtures/context-budget-profiles.json +11 -0
- package/.versions/2.0.22/.pi/harnesses/lib/fixtures/hub-prompt-operator.legacy.txt +73 -0
- package/.versions/2.0.22/.pi/harnesses/lib/fixtures/hub-prompt-orchestrator.legacy.txt +73 -0
- package/.versions/2.0.22/.pi/harnesses/lib/fleet-dashboard-ops.ts +178 -0
- package/.versions/2.0.22/.pi/harnesses/lib/fleet-dashboard-view.ts +172 -0
- package/.versions/2.0.22/.pi/harnesses/lib/fleet-detail-view.ts +339 -0
- package/.versions/2.0.22/.pi/harnesses/lib/fleet-overlay.ts +26 -0
- package/.versions/2.0.22/.pi/harnesses/lib/fleet-panel.ts +34 -0
- package/.versions/2.0.22/.pi/harnesses/lib/fleet-read-model.ts +609 -0
- package/.versions/2.0.22/.pi/harnesses/lib/fleet-selection.ts +24 -0
- package/.versions/2.0.22/.pi/harnesses/lib/fleet-strip-controller.ts +75 -0
- package/.versions/2.0.22/.pi/harnesses/lib/fleet-strip-view.ts +179 -0
- package/.versions/2.0.22/.pi/harnesses/lib/fleet-transcript-store.ts +244 -0
- package/.versions/2.0.22/.pi/harnesses/lib/herdr-client.ts +472 -0
- package/.versions/2.0.22/.pi/harnesses/lib/herdr-presence.ts +399 -0
- package/.versions/2.0.22/.pi/harnesses/lib/hermes-monitor-events.ts +136 -0
- package/.versions/2.0.22/.pi/harnesses/lib/hermes-monitor-herdr.ts +28 -0
- package/.versions/2.0.22/.pi/harnesses/lib/hermes-monitor-model.ts +18 -0
- package/.versions/2.0.22/.pi/harnesses/lib/hermes-monitor-registry.ts +6 -0
- package/.versions/2.0.22/.pi/harnesses/lib/hermes-monitor-socket.ts +163 -0
- package/.versions/2.0.22/.pi/harnesses/lib/hermes-monitor-store.ts +31 -0
- package/.versions/2.0.22/.pi/harnesses/lib/identical-dialog.ts +27 -0
- package/.versions/2.0.22/.pi/harnesses/lib/installation-state.js +62 -0
- package/.versions/2.0.22/.pi/harnesses/lib/policy-roots.js +106 -0
- package/.versions/2.0.22/.pi/harnesses/lib/policy-roots.ts +31 -0
- package/.versions/2.0.22/.pi/harnesses/lib/process-shared.ts +9 -0
- package/.versions/2.0.22/.pi/harnesses/lib/safe-source-read.js +29 -0
- package/.versions/2.0.22/.pi/harnesses/lib/semantic-approval.ts +80 -0
- package/.versions/2.0.22/.pi/harnesses/lib/spawned-peers.js +191 -0
- package/.versions/2.0.22/.pi/harnesses/lib/system1/config-agentic.js +15 -0
- package/.versions/2.0.22/.pi/harnesses/lib/system1/config-context-compaction.js +16 -0
- package/.versions/2.0.22/.pi/harnesses/lib/system1/config-damage-guard.js +24 -0
- package/.versions/2.0.22/.pi/harnesses/lib/system1/config-file-discovery.js +23 -0
- package/.versions/2.0.22/.pi/harnesses/lib/system1/config-json.js +37 -0
- package/.versions/2.0.22/.pi/harnesses/lib/system1/config-loader.js +44 -0
- package/.versions/2.0.22/.pi/harnesses/lib/system1/config-proactive.js +68 -0
- package/.versions/2.0.22/.pi/harnesses/lib/system1/config-triage.js +42 -0
- package/.versions/2.0.22/.pi/harnesses/lib/system1/config-v2.js +112 -0
- package/.versions/2.0.22/.pi/harnesses/lib/system1/config.js +50 -0
- package/.versions/2.0.22/.pi/harnesses/lib/system1/contracts.ts +154 -0
- package/.versions/2.0.22/.pi/harnesses/lib/system1/demo.ts +95 -0
- package/.versions/2.0.22/.pi/harnesses/lib/system1/jev.ts +503 -0
- package/.versions/2.0.22/.pi/harnesses/lib/system1/payload-screen.ts +65 -0
- package/.versions/2.0.22/.pi/harnesses/lib/system1/selection.js +11 -0
- package/.versions/2.0.22/.pi/harnesses/lib/system1/service.ts +245 -0
- package/.versions/2.0.22/.pi/harnesses/lib/update-check.ts +222 -0
- package/.versions/2.0.22/.pi/harnesses/package-lock.json +2121 -0
- package/.versions/2.0.22/.pi/harnesses/package.json +13 -0
- package/.versions/2.0.22/.pi/prompts/af-build.md +27 -0
- package/.versions/2.0.22/.pi/prompts/af-code-simplify.md +22 -0
- package/.versions/2.0.22/.pi/prompts/af-constraints.md +31 -0
- package/.versions/2.0.22/.pi/prompts/af-plan.md +17 -0
- package/.versions/2.0.22/.pi/prompts/af-review.md +16 -0
- package/.versions/2.0.22/.pi/prompts/af-set-hermes-telegram.md +15 -0
- package/.versions/2.0.22/.pi/prompts/af-set-hermes-watchdog.md +6 -0
- package/.versions/2.0.22/.pi/prompts/af-setup-rules.md +20 -0
- package/.versions/2.0.22/.pi/prompts/af-ship.md +17 -0
- package/.versions/2.0.22/.pi/prompts/af-spec.md +15 -0
- package/.versions/2.0.22/.pi/prompts/af-test.md +19 -0
- package/.versions/2.0.22/.pi/skills/bowser/SKILL.md +145 -0
- package/.versions/2.0.22/.version +1 -0
- package/.versions/2.0.22/agents/architect.md +24 -0
- package/.versions/2.0.22/agents/bowser.md +28 -0
- package/.versions/2.0.22/agents/builder.md +55 -0
- package/.versions/2.0.22/agents/code-reviewer.md +209 -0
- package/.versions/2.0.22/agents/deep-researcher.md +32 -0
- package/.versions/2.0.22/agents/documenter.md +22 -0
- package/.versions/2.0.22/agents/orchestrator.md +22 -0
- package/.versions/2.0.22/agents/plan-reviewer.md +83 -0
- package/.versions/2.0.22/agents/planner.md +107 -0
- package/.versions/2.0.22/agents/releaser.md +24 -0
- package/.versions/2.0.22/agents/researcher.md +30 -0
- package/.versions/2.0.22/agents/security-auditor.md +167 -0
- package/.versions/2.0.22/agents/test-engineer.md +153 -0
- package/.versions/2.0.22/agents/web-debugger.md +44 -0
- package/.versions/2.0.22/agents/web-performance-auditor.md +194 -0
- package/.versions/2.0.22/bin/catalog/harness-runtime-closure.json +73 -0
- package/.versions/2.0.22/codex/fleet-session-client/SKILL.md +34 -0
- package/.versions/2.0.22/codex/fleet-session-client.zip +0 -0
- package/.versions/2.0.22/docs/ARCHITECTURE.md +982 -0
- package/.versions/2.0.22/docs/agent-fleet-setup.md +1103 -0
- package/.versions/2.0.22/docs/claude-code-coms-bridge.md +147 -0
- package/.versions/2.0.22/docs/codex-session-bridge.md +219 -0
- package/.versions/2.0.22/docs/coms-hermes-bridge.md +188 -0
- package/.versions/2.0.22/docs/getting-started.md +126 -0
- package/.versions/2.0.22/docs/npm-install.md +535 -0
- package/.versions/2.0.22/docs/pi-extensions.md +455 -0
- package/.versions/2.0.22/docs/pi-setup.md +92 -0
- package/.versions/2.0.22/docs/skill-anatomy.md +150 -0
- package/.versions/2.0.22/install-manifest.json +3210 -0
- package/.versions/2.0.22/justfile +247 -0
- package/.versions/2.0.22/manifest-meta.json +1088 -0
- package/.versions/2.0.22/references/accessibility-checklist.md +160 -0
- package/.versions/2.0.22/references/communication-contract.md +26 -0
- package/.versions/2.0.22/references/definition-of-done.md +67 -0
- package/.versions/2.0.22/references/fleet-coordination-patterns.md +171 -0
- package/.versions/2.0.22/references/observability-checklist.md +92 -0
- package/.versions/2.0.22/references/orchestration-patterns.md +370 -0
- package/.versions/2.0.22/references/performance-checklist.md +236 -0
- package/.versions/2.0.22/references/prompting-patterns.md +380 -0
- package/.versions/2.0.22/references/security-checklist.md +245 -0
- package/.versions/2.0.22/references/testing-patterns.md +235 -0
- package/.versions/2.0.22/references/workflow-authoring.md +304 -0
- package/.versions/2.0.22/skills/_internal/grilling.md +59 -0
- package/.versions/2.0.22/skills/browser-testing-with-devtools/SKILL.md +351 -0
- package/.versions/2.0.22/skills/code-review-and-quality/SKILL.md +396 -0
- package/.versions/2.0.22/skills/compound-learning/SKILL.md +137 -0
- package/.versions/2.0.22/skills/constraint-driven-development/SKILL.md +338 -0
- package/.versions/2.0.22/skills/constraint-driven-development/references/floor-guard.md +99 -0
- package/.versions/2.0.22/skills/context-engineering/SKILL.md +341 -0
- package/.versions/2.0.22/skills/deprecation-and-migration/SKILL.md +247 -0
- package/.versions/2.0.22/skills/designing-agents/SKILL.md +394 -0
- package/.versions/2.0.22/skills/designing-agents/pi-harness-authoring.md +222 -0
- package/.versions/2.0.22/skills/drafting-workflows/SKILL.md +143 -0
- package/.versions/2.0.22/skills/drafting-workflows/scripts/make-workflow.ts +177 -0
- package/.versions/2.0.22/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/2.0.22/skills/git-workflow-and-versioning/SKILL.md +316 -0
- package/.versions/2.0.22/skills/idea-refine/SKILL.md +182 -0
- package/.versions/2.0.22/skills/idea-refine/examples.md +238 -0
- package/.versions/2.0.22/skills/idea-refine/frameworks.md +99 -0
- package/.versions/2.0.22/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/2.0.22/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/2.0.22/skills/incremental-implementation/SKILL.md +353 -0
- package/.versions/2.0.22/skills/incremental-implementation.zip +0 -0
- package/.versions/2.0.22/skills/interview-me/SKILL.md +226 -0
- package/.versions/2.0.22/skills/orchestration-verification/SKILL.md +182 -0
- package/.versions/2.0.22/skills/peer-coms/SKILL.md +90 -0
- package/.versions/2.0.22/skills/performance-optimization/SKILL.md +496 -0
- package/.versions/2.0.22/skills/planning-and-task-breakdown/SKILL.md +318 -0
- package/.versions/2.0.22/skills/planning-and-task-breakdown.zip +0 -0
- package/.versions/2.0.22/skills/repository-ai-setup/SKILL.md +135 -0
- package/.versions/2.0.22/skills/repository-ai-setup/references/agent-fleet-ai-state.template.json +4 -0
- package/.versions/2.0.22/skills/repository-ai-setup/references/apply-contract.md +74 -0
- package/.versions/2.0.22/skills/repository-ai-setup/references/provenance-template.md +16 -0
- package/.versions/2.0.22/skills/repository-ai-setup/references/setup-flow.md +108 -0
- package/.versions/2.0.22/skills/repository-ai-setup/references/verify-setup.md +20 -0
- package/.versions/2.0.22/skills/repository-ai-setup.zip +0 -0
- package/.versions/2.0.22/skills/security-and-hardening/SKILL.md +524 -0
- package/.versions/2.0.22/skills/spec-driven-development/SKILL.md +295 -0
- package/.versions/2.0.22/skills/spec-driven-development.zip +0 -0
- package/.versions/2.0.22/skills/using-agent-skills/SKILL.md +198 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/LICENSE +21 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/README.md +430 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/api-and-interface-design/SKILL.md +367 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/browser-testing-with-devtools/SKILL.md +317 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/ci-cd-and-automation/SKILL.md +390 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/code-review-and-quality/SKILL.md +396 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/code-simplification/SKILL.md +331 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/constraint-driven-development/SKILL.md +311 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/constraint-driven-development/references/floor-guard.md +99 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/context-engineering/SKILL.md +337 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/debugging-and-error-recovery/SKILL.md +300 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/deprecation-and-migration/SKILL.md +247 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/documentation-and-adrs/SKILL.md +288 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/doubt-driven-development/SKILL.md +243 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/frontend-ui-engineering/SKILL.md +328 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/git-workflow-and-versioning/SKILL.md +355 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/idea-refine/SKILL.md +178 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/idea-refine/examples.md +238 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/idea-refine/frameworks.md +99 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/idea-refine/refinement-criteria.md +113 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/idea-refine/scripts/idea-refine.sh +15 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/incremental-implementation/SKILL.md +249 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/interview-me/SKILL.md +225 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/observability-and-instrumentation/SKILL.md +238 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/performance-optimization/SKILL.md +496 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/planning-and-task-breakdown/SKILL.md +257 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/security-and-hardening/SKILL.md +524 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/shipping-and-launch/SKILL.md +330 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/source-driven-development/SKILL.md +216 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/spec-driven-development/SKILL.md +245 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/test-driven-development/SKILL.md +398 -0
- package/.versions/2.0.22/vendor/agent-skills-upstream/skills/using-agent-skills/SKILL.md +192 -0
- package/CHANGELOG.md +13 -0
- package/bin/cli.js +3 -2
- package/docs/ARCHITECTURE.md +6 -3
- package/docs/system1-damage-guard.md +23 -2
- package/install-manifest.json +1 -1
- package/package.json +1 -1
|
@@ -0,0 +1,455 @@
|
|
|
1
|
+
# pi Extensions
|
|
2
|
+
|
|
3
|
+
A catalog of the pi extensions in this repo — what each one does, how to run it, the
|
|
4
|
+
supporting data it needs, and how the ported set differs from upstream.
|
|
5
|
+
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
## Attribution
|
|
9
|
+
|
|
10
|
+
The session harnesses documented here — together with their supporting agent
|
|
11
|
+
definitions, design specs, and the `justfile` — are ported
|
|
12
|
+
from the **`pi-vs-claude-code`** project:
|
|
13
|
+
|
|
14
|
+
- **Author:** [disler](https://github.com/disler) (IndyDevDan)
|
|
15
|
+
- **Source:** <https://github.com/disler/pi-vs-claude-code>
|
|
16
|
+
- **License:** MIT — Copyright (c) 2026 IndyDevDan
|
|
17
|
+
|
|
18
|
+
Ported files retain their original authorship; this repo adapts them to its layout and
|
|
19
|
+
conventions. Runtime design specs for the imported harnesses live in `docs/pi-specs/`.
|
|
20
|
+
|
|
21
|
+
The model-poll / debate / merge mechanism (`.pi/agents/voices.yaml`, `/af-poll`,
|
|
22
|
+
`/af-debate`, `just flow poll`, `just flow debate`) follows the *form* of
|
|
23
|
+
[disler/fusion-harness](https://github.com/disler/fusion-harness) (MIT). This repo does
|
|
24
|
+
not vendor that code; the mechanisms are rebuilt on Agent Fleet seams.
|
|
25
|
+
|
|
26
|
+
---
|
|
27
|
+
|
|
28
|
+
## What these extensions are
|
|
29
|
+
|
|
30
|
+
`.pi/extensions/` contains utility extensions. Fleet Core explicitly loads
|
|
31
|
+
`compact-and-continue` and `btw`; browser and voice are
|
|
32
|
+
feature-gated: after setup installs them, launch with `just fleet --browser` or
|
|
33
|
+
`just fleet --voice`. This keeps Default deterministic even though pi can auto-discover
|
|
34
|
+
extensions outside Fleet Core. `btw` adds a
|
|
35
|
+
`/af-btw <task>` prompt command (plus an `Alt+'` shortcut) that forks the current session
|
|
36
|
+
into an in-process sub-session and opens a focused, capturing full-screen panel — full
|
|
37
|
+
context, same cwd, live transcript, and follow-up composer. `Esc` returns to the main
|
|
38
|
+
session while the side task continues; a compact result card lands in the main transcript
|
|
39
|
+
at idle. See [.pi/extensions/btw/README.md](../.pi/extensions/btw/README.md).
|
|
40
|
+
|
|
41
|
+
When loaded with `just fleet --voice`, `pi-voice-stt` adds **Alt+S** push-to-talk dictation: it records the mic to a temp WAV via
|
|
42
|
+
`ffmpeg` and transcribes through one of three backends — a generic OpenAI-compatible endpoint,
|
|
43
|
+
Azure Speech (REST short-audio, with optional per-phrase language identification), or Azure
|
|
44
|
+
OpenAI Whisper (Azure AI Foundry). Alt+S toggles record→insert; Enter-while-recording
|
|
45
|
+
transcribes and sends; Esc cancels. It is **gated**: the hotkey binds only once a provider is
|
|
46
|
+
configured (project-local `.ai/stt.json`, the global `~/.pi/agent/stt.json`, or `PI_STT_CONFIG`),
|
|
47
|
+
so an unconfigured session is a no-op. `/af-stt doctor`
|
|
48
|
+
checks the setup. A simplified port of [`cgarrot/pi-voice-stt`](https://github.com/cgarrot/pi-voice-stt);
|
|
49
|
+
see [.pi/extensions/pi-voice-stt/README.md](../.pi/extensions/pi-voice-stt/README.md).
|
|
50
|
+
|
|
51
|
+
> **macOS terminal note:** Option-to-Alt behavior belongs to the outer terminal, not macOS, Pi, or
|
|
52
|
+
> Herdr. If Option+M inserts `µ` (or another shortcut inserts a character) instead of activating the
|
|
53
|
+
> shortcut, the terminal is sending the keyboard-layout character rather than a Meta/Alt key event.
|
|
54
|
+
> In Terminal.app, open **Settings → Profiles → Keyboard** for the profile used by the window and
|
|
55
|
+
> enable **Use Option as Meta key**. In Zed, set `terminal.option_as_meta` to `true`. Then verify
|
|
56
|
+
> Option+M opens the Fleet work-mode picker; the terminal should send Meta/Alt chords as an Escape
|
|
57
|
+
> prefix (for example, ESC followed by `m`). This enables the existing shortcuts; it is not an
|
|
58
|
+
> OS-wide keybinding change. Command+M is separate: Terminal.app handles it as **Minimize**, so it
|
|
59
|
+
> does not reach Pi or Herdr as a Fleet shortcut.
|
|
60
|
+
|
|
61
|
+
The documented harnesses below are different: each is a **session harness**. They
|
|
62
|
+
reshape the whole pi session — some set orchestration/UI surfaces and some gate every
|
|
63
|
+
tool call. The unified `just fleet` entry point composes them with a deterministic
|
|
64
|
+
Fleet Core: `damage-control-continue` (which also runs the shared package update
|
|
65
|
+
check once per session), `ask-user-remote`, Compact & Continue, and BTW. Voice is an optional feature, not Default Fleet Core.
|
|
66
|
+
Every public Pi launch through bare `just fleet` also loads
|
|
67
|
+
`agent-hub`; operator/orchestrator work mode changes its direct tool surface without changing
|
|
68
|
+
process or session. `just fleet peer` starts a standalone coms peer. Harnesses live in
|
|
69
|
+
**`.pi/harnesses/`** — a directory pi does
|
|
70
|
+
*not* auto-discover — so a plain `pi` run still loads no safety/orchestration harness.
|
|
71
|
+
|
|
72
|
+
### Selective loading — read this first
|
|
73
|
+
|
|
74
|
+
pi auto-discovers every extension directory under a project's `.pi/extensions/` and loads
|
|
75
|
+
all of them. If the harnesses lived there, a plain `pi` run would load them all at once
|
|
76
|
+
— UI surfaces would fight, orchestrators would collide, and harnesses that register the
|
|
77
|
+
same CLI flags would abort startup with duplicate registrations. So the harnesses live in
|
|
78
|
+
`.pi/harnesses/` instead, and you load the desired recipe explicitly:
|
|
79
|
+
|
|
80
|
+
- through the unified `justfile` interface — `just fleet`, `just fleet --agents <roster>`, `just fleet --peers <preset>`, `just fleet peer <name>`, …
|
|
81
|
+
- or directly — `pi -e .pi/harnesses/<name>/index.ts` (advanced use; you must compose safety/utilities yourself)
|
|
82
|
+
|
|
83
|
+
When you consume this repo from another project, use deterministic `agent-fleet
|
|
84
|
+
setup` to select Default, Full, and named features; it installs the recorded
|
|
85
|
+
harness closure into *that project's* `.pi/harnesses/`. Then load it via the
|
|
86
|
+
managed `justfile` region, or point `pi -e` at a harness file directly — never
|
|
87
|
+
drop harnesses into `.pi/extensions/`, and never load all of them at once. The supported multi-harness
|
|
88
|
+
exception is loading `damage-control-continue` and `ask-user-remote` before `agent-hub` for a guarded hub session (see
|
|
89
|
+
[pi-setup.md](pi-setup.md#optional-pi-extensions)).
|
|
90
|
+
|
|
91
|
+
---
|
|
92
|
+
|
|
93
|
+
## Setup
|
|
94
|
+
|
|
95
|
+
```bash
|
|
96
|
+
just fleet deps # install nested runtime deps only; starts no Pi/harness
|
|
97
|
+
just fleet # Hub/operator + Fleet Core; empty native roster
|
|
98
|
+
just fleet --agents frontend
|
|
99
|
+
# Hub/orchestrator + native specialist roster
|
|
100
|
+
just fleet --agents default --peers docs --project af
|
|
101
|
+
# Hub + native roster + standing Herdr peers
|
|
102
|
+
just fleet peer code-reviewer --project af # ONE peer in its own Herdr pane, no team
|
|
103
|
+
just fleet help # unified command grammar
|
|
104
|
+
just --list # shows the single public `fleet` entry point
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
`just fleet deps` installs all three runtime dependency roots:
|
|
108
|
+
`.pi/extensions/` for utilities (`@modelcontextprotocol/sdk`, `typebox`),
|
|
109
|
+
`.pi/harnesses/` for harnesses (`@sinclair/typebox`, `yaml`), and `.pi/agent-fleet/scripts/` for
|
|
110
|
+
deterministic workflows (`@sinclair/typebox`, `yaml`). That is the **clone** path. In a
|
|
111
|
+
target workspace, deterministic `agent-fleet setup --allow-exec` runs `npm ci`
|
|
112
|
+
for those same three roots after its file transaction. Without `--allow-exec`, the plan lists those runtime steps for the
|
|
113
|
+
operator to run by hand. The extension dependencies are also root production dependencies of
|
|
114
|
+
the published `@chankov/agent-fleet` package, so a pi-package install resolves them from
|
|
115
|
+
the package's real path. The `@mariozechner/pi-*` packages are provided by the pi runtime
|
|
116
|
+
itself.
|
|
117
|
+
|
|
118
|
+
---
|
|
119
|
+
|
|
120
|
+
## Catalog
|
|
121
|
+
|
|
122
|
+
| Extension | Category | What it does | Run |
|
|
123
|
+
|-----------|----------|--------------|-----|
|
|
124
|
+
| [agent-hub](../.pi/harnesses/agent-hub/README.md) | Orchestration | Unified operator/orchestrator runtime: Fleet Core guardrails, dynamic native roster, specialist delegation, research helpers, embedded coms, `/af-handoff`, explicit native/coms backend routing, and footer `agent fleet v<version> · <model><thinking> · <team>` — plus, inside [Herdr](https://herdr.dev), constrained peer spawn, raw pane spawn, read, confirmed close, and notify tools | `just fleet` |
|
|
125
|
+
| [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`) |
|
|
126
|
+
| [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` |
|
|
127
|
+
| [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>` |
|
|
128
|
+
| [Hermes local monitor transport](../.pi/agent-fleet/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 a Herdr topology such as `just fleet --herdr` |
|
|
129
|
+
|
|
130
|
+
Each extension directory has its own `README.md` with the full description, command/tool
|
|
131
|
+
surface, requirements, and per-extension upstream changes.
|
|
132
|
+
|
|
133
|
+
### Migration: retired hard-stop harness
|
|
134
|
+
|
|
135
|
+
The former `.pi/harnesses/damage-control/` hard-stop harness and its standalone recipe
|
|
136
|
+
are retired. Refresh pi harnesses with `agent-fleet setup`: removal is bound by
|
|
137
|
+
the ownership rule, so only an unchanged, recorded copy
|
|
138
|
+
goes — user-modified and unowned copies are preserved, and the managed `justfile` region
|
|
139
|
+
is refreshed without touching recipes outside the sentinels. Use `damage-control-continue` for standalone and
|
|
140
|
+
Agent Hub safety; missing child safety now fails closed instead of falling back or spawning
|
|
141
|
+
unguarded.
|
|
142
|
+
|
|
143
|
+
### Harness version footer and provenance
|
|
144
|
+
|
|
145
|
+
The three persistent-UI harnesses — `agent-hub`, `coms`, and
|
|
146
|
+
`damage-control-continue` — each register `agent fleet v<version>` on one shared status key. In pi's
|
|
147
|
+
default status footer, that shared key gives a supported stack exactly one version instead of one
|
|
148
|
+
copy per harness. `agent-hub` replaces the default footer: it does **not** consume that status
|
|
149
|
+
key. Its custom footer reads its own adjacent stamped manifest and renders one local version
|
|
150
|
+
first — `agent fleet v<version> · <model><thinking> · <team>` — so an agent-hub stack also displays the
|
|
151
|
+
version exactly once.
|
|
152
|
+
|
|
153
|
+
The `agent fleet` half of that label is an [OSC 8](https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda)
|
|
154
|
+
terminal hyperlink to the project homepage, so a click in a terminal that supports hyperlinks
|
|
155
|
+
(Ghostty, iTerm2, WezTerm, Kitty, VS Code, GNOME Terminal, tmux 3.4+) opens the repository. It is a
|
|
156
|
+
terminal-level link, not a TUI control: pi has no mouse tracking, so a click cannot open an
|
|
157
|
+
in-process overlay — the URL goes to the OS opener. Terminals without OSC 8 support render the
|
|
158
|
+
label unchanged, and pi's `visibleWidth`/`truncateToWidth` strip OSC sequences, so the link costs no
|
|
159
|
+
footer columns. Set `AGENT_FLEET_NO_LINKS=1` to fall back to a plain label on multiplexers that
|
|
160
|
+
mangle unknown OSC sequences (GNU screen, tmux before 3.4).
|
|
161
|
+
|
|
162
|
+
The shared version status is independent of mutable owner status: for example, a
|
|
163
|
+
Damage-Control violation can replace its own safety message without overwriting the version
|
|
164
|
+
entry. The canonical value is the root `package.json` version. During a release,
|
|
165
|
+
`bin/sync-harness-versions.js` stamps that value into each adjacent persistent-harness
|
|
166
|
+
`package.json` after the root bump and before lockfile finalization and snapshotting. Each
|
|
167
|
+
harness keeps a local `version.ts` provenance reader so copied or symlinked harness directories
|
|
168
|
+
resolve their adjacent stamp rather than the launch directory. That local provenance does not
|
|
169
|
+
make a harness self-contained: copied target harnesses still require the existing full
|
|
170
|
+
`.pi/harnesses/` dependency installation described in [Setup](#setup).
|
|
171
|
+
|
|
172
|
+
### `agent-hub` components
|
|
173
|
+
|
|
174
|
+
`agent-hub` is the consolidated orchestration harness. It replaces the retired standalone
|
|
175
|
+
`agent-team` recipe and absorbs the day-to-day pieces that previously required separate
|
|
176
|
+
harnesses:
|
|
177
|
+
|
|
178
|
+
- **Two live Work Modes** — bare `just fleet` starts as an operator with direct coding tools and an
|
|
179
|
+
empty native roster; `/af-work-mode operator|orchestrator` switches prompt and tool surface without
|
|
180
|
+
restarting or losing session state, while `/af-work-mode` without an argument and **Alt+M** open
|
|
181
|
+
the picker. Orchestrator removes `bash`/`edit`/`write`, keeps read-only `filesystem` inspection, refuses self-read above 64 KiB per file or per turn. Dispatch and research counts are usage, never a per-turn allowance. A pending task transition lets `set_task_tier` and `ask_user` through; the second other tool call stops the turn, including a parallel batch, and the fence survives resume. Research, nested delegation, and the task envelope follow task tier. All Hub slash commands remain registered in both work modes; capability-off actions
|
|
182
|
+
refuse actionably.
|
|
183
|
+
- **Fleet widget** — **`Alt+I`**, registered through Pi's shortcut API, expands or collapses the
|
|
184
|
+
bounded below-editor fleet view when its focus, empty-editor, autocomplete/modal, row, and height
|
|
185
|
+
gates allow it. Use `j`/`k` inside the view; plain and Alt arrow keys remain editor input unchanged.
|
|
186
|
+
- **Fleet Dashboard** — **`Alt+A`** or `/af-agents-list` opens a
|
|
187
|
+
full-screen dashboard of the active native roster, delegates, currently running research
|
|
188
|
+
helpers, and coms peers, with the coms pool panel pinned to the bottom. Live research helpers never appear in the
|
|
189
|
+
main dispatcher view; they vanish from the dashboard on every terminal outcome while their
|
|
190
|
+
session/findings files and `/af-agents-history` records remain. The dashboard supports row
|
|
191
|
+
detail, filtering, finished-row visibility, confirmed kills, and a confirmed specialist restart.
|
|
192
|
+
In local row detail, **`m`**
|
|
193
|
+
opens a visible inline full-screen picker over the logs, selects from every model currently
|
|
194
|
+
available in Pi, and applies it to the next specialist, research, or nested-delegate run without
|
|
195
|
+
interrupting current work. See the
|
|
196
|
+
[agent-hub README](../.pi/harnesses/agent-hub/README.md#fleet-dashboard-and-detail) for
|
|
197
|
+
keys and action semantics.
|
|
198
|
+
- **Specialist delegation** — `dispatch_agent` for writable child-agent work. Read-only
|
|
199
|
+
investigation is automated through dispatcher-invoked `spawn_research` and the specialists'
|
|
200
|
+
`NEEDS_RESEARCH:` pipe; dedicated research lifecycle slash commands are not registered.
|
|
201
|
+
- **Verification Contract** — the dispatcher owns a ledger of checkable acceptance assertions
|
|
202
|
+
built before any builder runs, via the `set_assertions` / `update_assertion` tools. Each
|
|
203
|
+
assertion is tagged (`test` | `runtime-ui` | `code-grep` | `manual`) and advanced only on
|
|
204
|
+
*proven with evidence*; the ledger persists to `.pi/agent-sessions/assertions.json` (wiped at
|
|
205
|
+
session start like `findings/`) and shows a one-line status, keeping the contract out of the
|
|
206
|
+
dispatcher LLM context. It kills the parity failure (exemplar shipped, siblings missed) by
|
|
207
|
+
requiring a parity/touchpoint inventory for "behave like" requests and runtime proof for UI
|
|
208
|
+
assertions — see the [`orchestration-verification`](../skills/orchestration-verification/SKILL.md)
|
|
209
|
+
skill, which the `orchestrator` persona drives. Advisory in this phase (surfaced, not a hard
|
|
210
|
+
dispatch refusal).
|
|
211
|
+
- **Operator controls** — `/af-zoom` timeline inspection plus child-agent kill/restart controls. `/af-context` is a separate read-only full-screen context-budget view: provider totals/cache fields are authoritative, component estimates are labelled heuristic or provider-scaled, stable prompt and volatile-state cost are separated, loaded-but-excluded and inactive packs visibly cost zero, and fleet members use separate model-window denominators. It also shows live pressure phase, measured usage, the 60%/70% thresholds and 80% ceiling, episode, and last recovery outcome. It never reveals or persists raw prompts, schemas, conversation content, error bodies, or compaction summaries.
|
|
212
|
+
- **Automatic capability packs** — no activation command is needed. Intent, work mode, tier, pending work, and runtime state resolve the model-visible tools before the turn; readiness alone does not make coms/Herdr visible. Ambiguous fleet, peer, or workspace use asks once before its first side effect. The compact pack is transient when explicitly requested or pressure is imminent; ordinary task packs persist until `set_task_tier(new_task: true)`. Managed children receive selected replacement prompts/manifests (`--no-skills` and `--no-context-files` where applicable), not inherited global context.
|
|
213
|
+
- **Usage without continuation quotas** — dispatch, research and review counts and active time stay visible per turn and task, but authorized work never stops for a budget renewal. The watchdog supervises repeated work; genuinely different work uses `set_task_tier(new_task: true)`. Active-time clocks exclude human wait time.
|
|
214
|
+
- **Damage-control + ask_user by default** — `just fleet` and `just fleet --no-coms` load the
|
|
215
|
+
`damage-control-continue` safety harness and `ask-user-remote` before `agent-hub`, so the
|
|
216
|
+
dispatcher's tool calls are checked against the rules file and the `askUserAvailable` probe sees
|
|
217
|
+
`ask_user`. A blocked call feeds back and the turn keeps going rather than aborting. `agent-hub` also
|
|
218
|
+
re-loads `damage-control-continue` into every native specialist, research helper, and nested
|
|
219
|
+
delegate (via an explicit `-e` that survives `--no-extensions`). Protected-path access can be
|
|
220
|
+
granted at runtime: `/af-allow <pattern> [turn|session]` in the hub pre-authorizes, a parent-session
|
|
221
|
+
block opens an approval dialog, and a headless child escalates to the hub. Protected deletion
|
|
222
|
+
offers only deny/once; other protected paths may be scoped to an agent or session. Denial and
|
|
223
|
+
timeout fail closed without aborting the child turn. Destructive bash patterns are never exemptible,
|
|
224
|
+
and a missing continue harness refuses child dispatch.
|
|
225
|
+
- **Embedded coms** — peer discovery, `coms_list` / `coms_send` / `coms_get` / `coms_await`,
|
|
226
|
+
`/af-handoff`, and peer-as-subagent flows.
|
|
227
|
+
- **No-coms mode** — `just fleet --no-coms` keeps direct operator work, native delegation,
|
|
228
|
+
research helpers, and controls, but starts without embedded coms. `/af-handoff`
|
|
229
|
+
remains registered and explains why it cannot run. Legacy `--solo` maps to this flag with a warning.
|
|
230
|
+
- **Optional Hermes local monitor transport** — uses `AGENT_FLEET_PROFILE_ID`, the absolute
|
|
231
|
+
`AGENT_FLEET_MONITOR_RUNTIME_DIR`, and the Herdr `HERDR_WORKSPACE_ID` and `HERDR_PANE_ID`
|
|
232
|
+
required to establish its stable hub identity. It is a source-owned, local-only transport—not a
|
|
233
|
+
Hermes SDK task/lifecycle RPC or a bundled plugin—and fails closed without validated owner-only
|
|
234
|
+
discovery, lease, token, and socket state. Follow the
|
|
235
|
+
[Hermes integration guide](../.pi/agent-fleet/hermes/README.md#local-agent-hub-monitor-integration) for startup,
|
|
236
|
+
wire examples, cancellation semantics, and reconnect behavior.
|
|
237
|
+
|
|
238
|
+
#### Context and roster recovery troubleshooting
|
|
239
|
+
|
|
240
|
+
A green standing-prompt budget does not guarantee that a long tool loop fits: messages and tool
|
|
241
|
+
results continue accumulating inside the current model window. Agent Hub warns at **60%** live
|
|
242
|
+
usage. At **70%** it aborts the next same-turn provider request, waits for persistence/settlement,
|
|
243
|
+
and starts one automatic Pi compaction. The **80%** ceiling stops work only after a failed recovery
|
|
244
|
+
or when even the compacted baseline is at or above it. Startup or newly submitted input is retained in memory and
|
|
245
|
+
replayed exactly once after recovery. Use `/af-context` to distinguish `warning`, `compacting`,
|
|
246
|
+
`recovered`, and `failed` pressure from stable prompt/schema cost.
|
|
247
|
+
|
|
248
|
+
If automatic compaction fails, retained input is not discarded. Use Pi's built-in `/compact
|
|
249
|
+
[instructions]` command—even in bare Pi without Agent Hub—or switch to a larger-context model. Pi's
|
|
250
|
+
session JSONL under `~/.pi/agent/sessions/` remains the authoritative append-only record. Context
|
|
251
|
+
overflow does not imply corruption: inspect with `/session`, resume with `/resume` or Pi's session
|
|
252
|
+
flags, and **never edit, truncate, reorder, or synthesize JSONL entries to recover**.
|
|
253
|
+
|
|
254
|
+
If resume instead reports that orchestrator work mode has no valid native roster, direct tools and
|
|
255
|
+
model input intentionally remain blocked. Select a current team with `/af-agents-team`; restart via
|
|
256
|
+
`just fleet --agents <name>` (direct Pi: `--agent-team <name>`); or explicitly choose operator with
|
|
257
|
+
`/af-work-mode operator` / `just fleet --work-mode operator`. Repair stale team/persona definitions
|
|
258
|
+
before selecting them. The Hub never invents a roster or silently downgrades persisted work mode, and
|
|
259
|
+
explicit startup flags retain precedence.
|
|
260
|
+
|
|
261
|
+
### Runtime axes and explicit routing
|
|
262
|
+
|
|
263
|
+
Work mode, native roster, and peer topology are independent:
|
|
264
|
+
|
|
265
|
+
```bash
|
|
266
|
+
just fleet # operator, empty native roster
|
|
267
|
+
just fleet --agents frontend # orchestrator inferred
|
|
268
|
+
just fleet --work-mode operator --agents frontend # direct tools + native roster
|
|
269
|
+
just fleet --herdr --project af # one Hub pane in Herdr
|
|
270
|
+
just fleet --agents frontend --peers frontend --project af
|
|
271
|
+
```
|
|
272
|
+
|
|
273
|
+
A **native specialist** is a local headless Pi child selected from `teams.yaml`; a **peer** is a
|
|
274
|
+
separate long-lived Pi or Claude Code process registered over coms, usually in a sibling Herdr
|
|
275
|
+
pane. Add a native reviewer at runtime with `/af-agents-add code-reviewer`. When a same-name
|
|
276
|
+
Claude reviewer is live, `dispatch_agent`'s `backend: "native"` still forces the local Pi child,
|
|
277
|
+
`backend: "coms"` requires that peer with no native fallback, and `backend: "auto"` follows
|
|
278
|
+
`dispatch-policy.yaml`.
|
|
279
|
+
|
|
280
|
+
Inside a Herdr-backed Hub, `herdr_spawn_peer({ name: "code-reviewer" })` uses the declaration in
|
|
281
|
+
`peers.yaml` (including `runner: claude-code`), creates a sibling pane, locks it to the Hub project,
|
|
282
|
+
and waits for coms readiness. Then use `coms_send` + `coms_await`, or `/af-handoff
|
|
283
|
+
code-reviewer`. These actions need a running Herdr server and/or ready coms as appropriate; the
|
|
284
|
+
commands stay registered and explain missing capability. Arbitrary pane commands use the separate
|
|
285
|
+
`herdr_spawn_pane` tool. In orchestrator work mode that tool is limited by policy to auxiliary
|
|
286
|
+
processes such as watchers or servers; it must not be used to bypass delegation for code work.
|
|
287
|
+
|
|
288
|
+
---
|
|
289
|
+
|
|
290
|
+
## Two browser stacks — when to use which
|
|
291
|
+
|
|
292
|
+
This repo ships **two** ways to drive a browser from a pi agent. They are complementary, not redundant — the axis that separates them is the **tool model** (and where they can run), not just headless-vs-headful, since both can do either:
|
|
293
|
+
|
|
294
|
+
| | `bowser` / `playwright-cli` | `web-debugger` / `chrome-devtools-mcp` |
|
|
295
|
+
|---|---|---|
|
|
296
|
+
| Tool model | CLI over **Bash** (no tool schemas in context) | live `chrome_devtools__*` MCP tools |
|
|
297
|
+
| Strength | headless, parallel named sessions, background automation, scraping, token-efficient | interactive headful debugging, live DOM/console/network, performance traces |
|
|
298
|
+
| Where it runs | **dispatched subagent** (survives `--no-extensions`), peer, or main session | main session or **coms peer** (the extension must be loaded into the process) |
|
|
299
|
+
| Persona | `bowser` | `web-debugger` |
|
|
300
|
+
| Skill | `.pi/skills/bowser/` | `skills/browser-testing-with-devtools/` |
|
|
301
|
+
|
|
302
|
+
**Policy:**
|
|
303
|
+
|
|
304
|
+
- **Automated / CI / background / parallel runtime-UI evidence** → `bowser` (headless `playwright-cli`). This is what the `orchestrator` delegates as a subagent to close `runtime-ui` acceptance assertions.
|
|
305
|
+
- **Interactive debugging of a running dev app** → `web-debugger` (headful `chrome-devtools-mcp`), reached as a coms peer or run on the main session.
|
|
306
|
+
- **Manual visual inspection / login flows** → `web-debugger` headful, or attach to an existing Chrome.
|
|
307
|
+
- **Always require runtime evidence** — snapshot + console + network before/after a critical interaction; a screenshot only for visual/layout confirmation.
|
|
308
|
+
|
|
309
|
+
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.
|
|
310
|
+
|
|
311
|
+
## One peer at a time — `just fleet peer`
|
|
312
|
+
|
|
313
|
+
`just fleet --peers <preset>` is the right topology for a *known* set of collaborators, but it
|
|
314
|
+
requires every peer to be declared in `.pi/agents/peers.yaml` and it builds a whole
|
|
315
|
+
workspace. When you want **one** more agent — often a Claude Code reviewer — next to
|
|
316
|
+
what you already have:
|
|
317
|
+
|
|
318
|
+
```bash
|
|
319
|
+
just fleet peer code-reviewer --project af # peers.yaml decides the runner
|
|
320
|
+
just fleet peer scratch-reviewer --runner claude-code --model opus --project af
|
|
321
|
+
just fleet peer researcher --model openai-codex/gpt-6-luna --project af
|
|
322
|
+
just fleet peer web-debugger --browser --project af # persona peer + devtools MCP
|
|
323
|
+
just fleet peer nick --here --project af # this terminal, not a pane
|
|
324
|
+
just fleet peer anything --runner claude-code --dry-run # print the plan, touch nothing
|
|
325
|
+
```
|
|
326
|
+
|
|
327
|
+
**The name decides the shape of the peer** — one verb, three launchers:
|
|
328
|
+
|
|
329
|
+
| The name… | Peer | Recipe |
|
|
330
|
+
|---|---|---|
|
|
331
|
+
| is declared in `peers.yaml` | whatever it declares (`runner`, `model`, `extensions`, `env_file`) | per declaration |
|
|
332
|
+
| matches `agents/<name>.md` | that guarded persona peer | `_peer` / `_peer-plus` |
|
|
333
|
+
| matches nothing | Fleet Core + coms under that identity, no persona | `_fleet-peer` |
|
|
334
|
+
| `--runner claude-code` | interactive Claude Code + its coms bridge in one pane | `_claude-peer` |
|
|
335
|
+
|
|
336
|
+
The third row is what this command meant before pane placement existed, and it is the
|
|
337
|
+
only shape that accepts raw pi arguments — everything after `--` goes to pi verbatim
|
|
338
|
+
(`just fleet peer nick --here -- --session /path/to/session.json`). Note that the
|
|
339
|
+
persona-by-name rule can change what an existing invocation means: `agents/architect.md`
|
|
340
|
+
exists, so `just fleet peer architect` is now the architect persona peer. `--no-persona`
|
|
341
|
+
forces the plain Fleet Core shape back.
|
|
342
|
+
|
|
343
|
+
- **Placement** — by default the peer gets its own pane: run inside a herdr pane and it
|
|
344
|
+
splits *that* pane (`--direction right|down`); run outside herdr and it creates a
|
|
345
|
+
single-pane workspace labelled `<worktree-tag>-peer-<name>`, refusing to clobber an
|
|
346
|
+
existing one. `--here` runs it in the calling terminal instead.
|
|
347
|
+
- **Field resolution** — explicit flag → the `peers.yaml` declaration for that *name*
|
|
348
|
+
(searched across every team) → a convention default. A name the fleet already defines
|
|
349
|
+
keeps its declared fields; a name it does not need no manifest entry at all.
|
|
350
|
+
- **Nothing is silently dropped** — a flag that cannot apply to the resolved shape is an
|
|
351
|
+
error, not a no-op: `--all-extensions` on a persona peer, `--persona` on a Claude Code
|
|
352
|
+
peer, a mistyped flag, or a pi flag that forgot its `--` separator.
|
|
353
|
+
- **`--project` matters** — same rule as teams: the flag form is `--project af`;
|
|
354
|
+
`project=af` is a `just` variable override and is silently ignored, leaving the peer
|
|
355
|
+
in the shared `default` pool.
|
|
356
|
+
- **Readiness** — a pane launch waits (bounded) for the peer to register in the coms pool
|
|
357
|
+
and exits non-zero with the pane's last output if it never does. A peer that missed
|
|
358
|
+
the window has failed to start, not started slowly.
|
|
359
|
+
|
|
360
|
+
Pure logic in `.pi/agent-fleet/scripts/lib/peer-launch.ts` (under `node --test`); the herdr wiring is
|
|
361
|
+
`.pi/agent-fleet/scripts/peer-launch.ts`. Inside a hub session the equivalent is the `herdr_spawn_peer`
|
|
362
|
+
tool, which shares the same command builder and readiness policy.
|
|
363
|
+
|
|
364
|
+
## Environment variables
|
|
365
|
+
|
|
366
|
+
The `justfile` sets `dotenv-load`, so a `.env` file at the repo root is auto-loaded
|
|
367
|
+
(`.env` is gitignored). Only a few extensions need keys:
|
|
368
|
+
|
|
369
|
+
| Variable | Needed by | Purpose |
|
|
370
|
+
|----------|-----------|---------|
|
|
371
|
+
| `PI_CHROME_DEVTOOLS_MODE` | `chrome-devtools-mcp` | `headless` runs Chrome with no UI; anything else (default) is headed |
|
|
372
|
+
| `PI_CHROME_DEVTOOLS_BROWSER_URL` | `chrome-devtools-mcp` | Attach to a running Chrome (e.g. `http://127.0.0.1:9222`) instead of launching one |
|
|
373
|
+
| `PI_CHROME_DEVTOOLS_USER_DATA_DIR` | `chrome-devtools-mcp` | Persistent Chrome profile path (else the default ephemeral `--isolated` profile) |
|
|
374
|
+
| `OPENAI_API_KEY` | `pi-voice-stt` (openai backend) | API key for the OpenAI-compatible transcription endpoint (var name overridable via `provider.apiKeyEnv`) |
|
|
375
|
+
| `AZURE_SPEECH_KEY` | `pi-voice-stt` (azure backend) | Azure Speech resource key |
|
|
376
|
+
| `AZURE_SPEECH_ENDPOINT` | `pi-voice-stt` (azure backend) | Azure resource endpoint, used when `provider.endpoint` is unset |
|
|
377
|
+
| `PI_STT_CONFIG` / `PI_STT_KEYBIND` | `pi-voice-stt` | Override config (inline JSON or path) / the record hotkey (default `alt+s`) |
|
|
378
|
+
| `AGENT_FLEET_SPAWN_DELAY` | `_peer` / `_peer-plus` recipes | Seconds to sleep before launching pi in a fleet pane (set per pane by `just fleet --peers`/`just fleet resume`, see below) |
|
|
379
|
+
|
|
380
|
+
The `chrome-devtools-mcp` server starts once at extension load, so changing its vars needs a pi
|
|
381
|
+
restart / `/reload` to take effect.
|
|
382
|
+
|
|
383
|
+
### Spawn pre-warm/stagger
|
|
384
|
+
|
|
385
|
+
pi loads its credential store (`~/.pi/agent/auth.json`) once at boot under a short-retry
|
|
386
|
+
file lock. When the stored OAuth token is stale, the first pi to boot refreshes it over
|
|
387
|
+
the network *while holding that lock*; sibling panes spawned in the same instant (as
|
|
388
|
+
`just fleet --peers` / `just fleet resume` do) lose the lock race and come up
|
|
389
|
+
with every provider showing **unconfigured**. To dodge this, the team scripts check
|
|
390
|
+
`auth.json` before spawning (only `type`/`expires` are read — values never leave the
|
|
391
|
+
process): if any OAuth credential is expired or about to expire, one pi pane (the hub
|
|
392
|
+
when present, else the first pi peer) starts immediately and refreshes the token, and
|
|
393
|
+
every other pi pane gets `AGENT_FLEET_SPAWN_DELAY` in its pane env — the `_peer` /
|
|
394
|
+
`_peer-plus` recipes sleep that many seconds before launching pi. Fresh tokens mean zero
|
|
395
|
+
delay everywhere; `claude-code` runner panes never wait. Pure logic in
|
|
396
|
+
`.pi/agent-fleet/scripts/lib/spawn-stagger.ts` (under `node --test`).
|
|
397
|
+
|
|
398
|
+
---
|
|
399
|
+
|
|
400
|
+
## Supporting data
|
|
401
|
+
|
|
402
|
+
These ported files are runtime dependencies of the extensions above:
|
|
403
|
+
|
|
404
|
+
- **`agents/`** — canonical persona Markdown files for shared and pi-specific agents.
|
|
405
|
+
Read by `agent-hub`.
|
|
406
|
+
- **`.pi/agents/`** — pi YAML configs only (`teams.yaml`, `peers.yaml`).
|
|
407
|
+
The earlier `reviewer` and `red-team` personas were folded into `code-reviewer` and
|
|
408
|
+
`security-auditor`; the remaining team/peer configs already reference the canonical names.
|
|
409
|
+
A peer entry may carry an optional `extensions:` field (comma-separated names under
|
|
410
|
+
`.pi/extensions/`) — Fleet's team launcher then routes it through the `_peer-plus` recipe so those
|
|
411
|
+
extensions load into the peer process. The `web-debugger` peer uses this to get
|
|
412
|
+
`chrome-devtools-mcp`'s `chrome_devtools__*` tools (see the two-browser-stacks section above).
|
|
413
|
+
- **`.pi/damage-control-rules.yaml`** — the destructive-command / protected-path rule set
|
|
414
|
+
for `damage-control-continue`.
|
|
415
|
+
- **`.pi/skills/bowser/`** — a pi-runtime skill for headless Playwright browser
|
|
416
|
+
automation, used by the `bowser` agent persona. Kept separate from the core
|
|
417
|
+
engineering `skills/`. It drives the external **Playwright Agent CLI**
|
|
418
|
+
(`playwright-cli`), which is **not** bundled — install it once with
|
|
419
|
+
`npm install -g @playwright/cli@latest` (deterministic setup checks for it when
|
|
420
|
+
`bowser` is selected). Docs: <https://playwright.dev/agent-cli/installation>.
|
|
421
|
+
- **`docs/pi-specs/`** — the original design specifications: `agent-forge` (now consolidated
|
|
422
|
+
into `agent-hub`), `agent-workflow` (retired `agent-chain`), and `damage-control`.
|
|
423
|
+
|
|
424
|
+
---
|
|
425
|
+
|
|
426
|
+
## Upstream changes
|
|
427
|
+
|
|
428
|
+
What changed relative to `disler/pi-vs-claude-code`:
|
|
429
|
+
|
|
430
|
+
- **Theme code removed.** Every ported harness imported `applyExtensionDefaults` from a
|
|
431
|
+
shared `themeMap.ts`. That import and its `session_start` call site were stripped from
|
|
432
|
+
the ported files; `themeMap.ts` and the 11 `.pi/themes/*.json` palettes are not ported.
|
|
433
|
+
Extensions render against pi's active theme.
|
|
434
|
+
- **Layout converted.** Flat `extensions/<name>.ts` files became
|
|
435
|
+
`.pi/harnesses/<name>/index.ts` directories, each with its own `package.json` and
|
|
436
|
+
`README.md`. They live under `.pi/harnesses/` — *not* `.pi/extensions/` — because pi
|
|
437
|
+
auto-discovers and loads everything in `.pi/extensions/`, while harnesses must be loaded
|
|
438
|
+
explicitly through recipes (with `damage-control-continue` + `ask-user-remote` before
|
|
439
|
+
`agent-hub` as the supported stack).
|
|
440
|
+
- **Tooling switched to npm.** `bun` / `bun.lock` are not used; the `justfile` recipes
|
|
441
|
+
point at the new paths and use npm.
|
|
442
|
+
|
|
443
|
+
### Not ported
|
|
444
|
+
|
|
445
|
+
- The `pure-focus`, `theme-cycler`, and `cross-agent` extensions.
|
|
446
|
+
- `themeMap.ts` and all 11 `.pi/themes/*.json` theme palettes.
|
|
447
|
+
- The Claude Code `statusLine` config and `status_lines/status_line.py`, and the
|
|
448
|
+
`plan_w_team.md` command (it depended on team-agent files absent from the source).
|
|
449
|
+
|
|
450
|
+
### A note on `.pi/settings.json`
|
|
451
|
+
|
|
452
|
+
Upstream shipped a `.pi/settings.json` that only set the (now-stripped) theme and
|
|
453
|
+
registered a prompt directory. This repo already keeps pi prompts in the standard
|
|
454
|
+
`.pi/prompts/` location, so no `.pi/settings.json` is shipped — it would carry nothing
|
|
455
|
+
useful.
|
|
@@ -0,0 +1,92 @@
|
|
|
1
|
+
# pi setup
|
|
2
|
+
|
|
3
|
+
<img src="https://raw.githubusercontent.com/chankov/agent-fleet/main/docs/assets/branding/agent-fleet-logo-white-v1.png" alt="Agent Fleet — Many agents. One direction." width="480">
|
|
4
|
+
|
|
5
|
+
Agent Fleet is pi-first. Its deterministic lifecycle writes copied workspace
|
|
6
|
+
artifacts; the package-native path exposes skills/prompts directly.
|
|
7
|
+
|
|
8
|
+
## Lifecycle install
|
|
9
|
+
|
|
10
|
+
From the target repository in a real TTY, begin with:
|
|
11
|
+
|
|
12
|
+
```bash
|
|
13
|
+
just fleet setup
|
|
14
|
+
```
|
|
15
|
+
|
|
16
|
+
This is the easiest installer TUI entry point. It runs `npx
|
|
17
|
+
@chankov/agent-fleet@latest setup`, where you choose Default or Full and optional
|
|
18
|
+
comma-separated features, inspect the exact plan, and confirm once to apply. It needs
|
|
19
|
+
npm registry access unless `@latest` is cached. For automation or without `just`:
|
|
20
|
+
|
|
21
|
+
```bash
|
|
22
|
+
npx @chankov/agent-fleet@latest setup --preset default --features none --yes
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
These are published-package commands; source-checkout development uses
|
|
26
|
+
`node bin/cli.js setup`. `pi update --extensions` does not update the npm installer:
|
|
27
|
+
run `just fleet setup` to resolve `@latest` and reconcile. `just fleet deps` installs
|
|
28
|
+
nested runtime dependencies; `just fleet install` was removed. See
|
|
29
|
+
[npm-install.md](npm-install.md) for the canonical installer guide.
|
|
30
|
+
|
|
31
|
+
Default is launchable Fleet Core and does not create `.claude/` or voice
|
|
32
|
+
configuration. Full selects stable, platform-applicable roots and may add the
|
|
33
|
+
recorded Claude Code coms bridge. Feature flags are named additions over a
|
|
34
|
+
preset; they are not an arbitrary package picker. Flags do not rewrite an
|
|
35
|
+
existing desired file unless `--save-desired` is explicit.
|
|
36
|
+
|
|
37
|
+
The installer owns only paths in `.ai/agent-fleet-state.json`. Normal uninstall
|
|
38
|
+
preserves `.ai/agent-fleet.json`, `.ai/agent-fleet-overrides.md`, `.ai/stt.json`,
|
|
39
|
+
and environment files. See [npm-install.md](npm-install.md) for `--migrate`,
|
|
40
|
+
`--purge-config`, doctor exits, and self-uninstall recovery.
|
|
41
|
+
|
|
42
|
+
## Runtime closure
|
|
43
|
+
|
|
44
|
+
`just fleet` is the guarded Fleet Core launcher. It explicitly loads
|
|
45
|
+
`damage-control-continue` (which runs the shared package update check once per
|
|
46
|
+
session), `ask-user-remote`, compact-and-continue, and BTW. Voice is not a Default Core dependency. `just fleet hub`
|
|
47
|
+
adds agent-hub; `just fleet peer` adds coms; `just fleet team` uses Herdr.
|
|
48
|
+
|
|
49
|
+
```bash
|
|
50
|
+
just fleet help
|
|
51
|
+
just fleet setup
|
|
52
|
+
just fleet deps
|
|
53
|
+
just fleet doctor
|
|
54
|
+
just fleet uninstall --yes
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
Self-uninstall removes the managed justfile region and dispatcher scripts last,
|
|
58
|
+
so its report completes. Restore it only through `npx @chankov/agent-fleet
|
|
59
|
+
setup ...`; then `just fleet doctor` is available again.
|
|
60
|
+
|
|
61
|
+
## Package-native skills and prompts
|
|
62
|
+
|
|
63
|
+
```bash
|
|
64
|
+
pi install -l npm:@chankov/agent-fleet
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
Do not also copy the same skills/prompts into `.pi/`; that creates collisions.
|
|
68
|
+
Harness-only composition (package-native skills/prompts plus copied harnesses)
|
|
69
|
+
is supported. The package bundles `pi-ask-user`; copied plain-pi installations
|
|
70
|
+
need their own compatible `pi-ask-user` source.
|
|
71
|
+
|
|
72
|
+
Within the package, Pi discovery is explicitly native-first: it loads the
|
|
73
|
+
complete Fleet-native `skills/` root and only the individual vendored skill
|
|
74
|
+
directories that have no native winner. Maintainers must keep those
|
|
75
|
+
upstream-only `package.json` declarations aligned with the manifest-derived
|
|
76
|
+
winner set whenever skills are imported, customized, or retired, then run
|
|
77
|
+
`node --test bin/test/pi-skill-discovery.test.js` and
|
|
78
|
+
`npm run check:manifest`. See [UPSTREAM-SKILLS.md](UPSTREAM-SKILLS.md) for the
|
|
79
|
+
procedure.
|
|
80
|
+
|
|
81
|
+
This prevents collisions between Fleet's native and vendored copies, not
|
|
82
|
+
collisions with independently installed packages. Fleet retains the upstream
|
|
83
|
+
`test-driven-development` skill, so another package that exports that name
|
|
84
|
+
(such as Superpowers) can still conflict; resolve that external overlap by
|
|
85
|
+
choosing which package should provide the skill rather than removing it from
|
|
86
|
+
Fleet's catalog.
|
|
87
|
+
|
|
88
|
+
## Project-owned configuration
|
|
89
|
+
|
|
90
|
+
`.ai/agent-fleet-overrides.md` is minimal committed project configuration;
|
|
91
|
+
`.ai/stt.json` contains provider names and environment-variable names, never
|
|
92
|
+
secret values. The root environment file is human-owned and append-only.
|