@chankov/agent-fleet 0.0.1 → 0.0.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/commands/doctor-agent-fleet.md +1 -1
- package/.claude/commands/setup-agent-fleet.md +4 -4
- package/.opencode/commands/af-doctor-agent-fleet.md +2 -0
- package/.opencode/commands/af-setup-agent-fleet.md +1 -1
- package/.pi/agents/model-profiles.yaml +12 -12
- package/.pi/agents/peers.yaml +26 -22
- package/.pi/agents/teams.yaml +2 -2
- package/.pi/harnesses/agent-hub/README.md +57 -4
- package/.pi/harnesses/agent-hub/index.ts +236 -80
- package/.pi/harnesses/agent-hub/research-retention.js +34 -0
- package/.pi/harnesses/ask-user-remote/README.md +8 -0
- package/.pi/harnesses/ask-user-remote/index.ts +41 -1
- package/.pi/harnesses/coms/README.md +11 -0
- package/.pi/prompts/doctor-agent-fleet.md +1 -1
- package/.pi/prompts/setup-agent-fleet.md +4 -4
- package/README.md +133 -354
- package/agents/architect.md +4 -2
- package/agents/bowser.md +2 -1
- package/agents/builder.md +3 -2
- package/agents/code-reviewer.md +7 -7
- package/agents/deep-researcher.md +3 -3
- package/agents/documenter.md +3 -1
- package/agents/orchestrator.md +5 -3
- package/agents/plan-reviewer.md +5 -5
- package/agents/planner.md +7 -7
- package/agents/releaser.md +3 -1
- package/agents/researcher.md +3 -3
- package/agents/security-auditor.md +7 -7
- package/agents/test-engineer.md +5 -5
- package/agents/web-debugger.md +3 -3
- package/agents/web-performance-auditor.md +3 -3
- package/bin/snapshot-version.js +17 -1
- package/codex/CONDUCTOR.md +148 -0
- package/docs/ARCHITECTURE.md +165 -0
- package/docs/agent-fleet-setup.md +1 -0
- package/docs/claude-code-coms-bridge.md +10 -0
- package/docs/codex-remote-conductor.md +170 -0
- package/docs/coms-hermes-bridge.md +121 -0
- package/docs/getting-started.md +14 -0
- package/docs/npm-install.md +2 -0
- package/docs/pi-extensions.md +16 -0
- package/docs/pi-setup.md +2 -0
- package/hermes/README.md +48 -0
- package/hermes/skills/hub-conductor/SKILL.md +84 -0
- package/hermes/skills/hub-liaison/SKILL.md +84 -0
- package/justfile +132 -15
- package/package.json +10 -3
- package/scripts/codex-conductor.ts +41 -0
- package/scripts/codex-remote-control.ts +167 -0
- package/scripts/coms-cli.ts +311 -199
- package/scripts/coms-hermes-bridge.ts +8 -4
- package/scripts/lib/codex-conductor.ts +88 -0
- package/scripts/lib/codex-remote-control.ts +480 -0
- package/scripts/lib/coms-envelope.ts +51 -6
- package/scripts/lib/herdr-layout.ts +35 -7
- package/scripts/lib/hermes-bridge-core.ts +4 -4
- package/scripts/lib/spawn-stagger.ts +101 -0
- package/scripts/lib/team-project.ts +112 -3
- package/scripts/lib/team-snapshot.ts +3 -2
- package/scripts/team-snapshot.ts +23 -6
- package/scripts/team-up.ts +106 -18
- package/skills/guided-workspace-setup/SKILL.md +123 -97
- package/skills/guided-workspace-setup/companion-manifest.json +33 -0
- package/skills/peer-coms/SKILL.md +9 -0
- package/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
|
@@ -12,9 +12,9 @@ Analyse the workspace. If prior install state is found (`.ai/agent-fleet-setup.m
|
|
|
12
12
|
|
|
13
13
|
The Skills group draws from **two roots**: fleet-native `skills/` and the vendored upstream import `vendor/agent-skills-upstream/skills/` (see `docs/UPSTREAM-SKILLS.md`). On a name collision the native copy wins — never offer the vendored duplicate as a separate row.
|
|
14
14
|
|
|
15
|
-
Then present the install menu
|
|
15
|
+
Then present the install menu per the skill's Step 1 interaction contract — drive every decision through the `ask_user` widget, never a printed table awaiting a free-text reply (the table format is reserved for the no-widget fallback when the user declined the bootstrap). Open with the **Express question** (fresh workspace: `Recommended ★` / `Everything` / `Custom — group by group` / `Nothing`; existing: `Keep as-is` / `Apply updates` / `Keep + add recommended ★` / `Custom`) — any answer but `Custom` skips all group screens. On `Custom`, run the **7 groups** (4 shared: Skills, Agent personas, Commands/prompts, References & Hooks; 3 pi-only: pi extensions & runtime skills, pi harnesses, External pi packages): each opens as a single-select quick screen (`Recommended ★ (n)` / `Everything (m)` / `Customise` / `Skip group`, or the installed-state variants with `Remove some…`), and multi-select drill-ins appear only behind `Customise`, chunked by sub-category (lifecycle phase for Skills, `rw`/`ro`/`pi-only` for personas, harness category, …) at ≤ 9 options per call, ≤ 8 `context` lines. Option titles carry `name ★ [st]` (`ok`/`upd`/`mod`/`cflt`/`gone`/`new`/`pkg`/`—`/`brk`); descriptions carry the purpose plus the state in plain words (`mod` → warn that refreshing overwrites local edits). There is **no pre-checking** (`ask_user` has no preselect) — installed state shows as counts on quick screens and words in descriptions; leaving an installed item unselected in a drill-in keeps it as-is. Freeform stays on so `all` / `recommended` (adds `★` on top — never removes) / `none` / `keep` still work; cancel = keep-as-is/skip. `cflt` rows are resolved only by printing the three-way diff and asking per row with `displayMode: "inline"` — never by Express or `Apply updates`. The External pi packages group lists `pi-ask-user` and the optional suggested `pi-codex-image-gen`. After Step 5b, `pi-ask-user` normally counts toward `Keep as-is` (`pkg`, scope `project` / `bundled by @chankov/agent-fleet` / `global` — state it in the restate line, no duplicate entries). `pi-codex-image-gen` is not bundled or bootstrapped; offer `pi install -l npm:pi-codex-image-gen` only when the user selects it. Never offer `setup`, `doctor`, or `guided-workspace-setup` — those are installer-only and live in the source agent-fleet repo.
|
|
16
16
|
|
|
17
|
-
|
|
17
|
+
Removal happens **only** on an explicit `Remove some…` multi-select (empty selection = remove nothing), and it is scoped: the screen lists only items whose name is in the agent-fleet inventory **and** that are recorded in `## install-status` (or are symlinks resolving into the source repo). User-authored skills, custom commands, third-party plugins, external pi packages not recorded by this setup, and unrelated settings/env keys are left untouched and logged as "Skipped — not owned by agent-fleet".
|
|
18
18
|
|
|
19
19
|
**No cross-tool substitution.** Each row is offered only when the source file the chosen agent needs already exists — for `pi`, that means `.pi/prompts/<name>.md`, `.pi/extensions/<name>/`, etc. Never fall back to `.claude/commands/` (or another agent's tree) to satisfy a pi prompt request; items missing their per-agent source are filtered out of the menu entirely.
|
|
20
20
|
|
|
@@ -22,6 +22,6 @@ Unchecking an installed item means *remove it*, but **removal is scoped**: only
|
|
|
22
22
|
|
|
23
23
|
**pi harness companions.** Installing, refreshing, or removing any pi harness also refreshes its companions in the same pass — the `justfile` launch recipes, `scripts/team-up.ts`, the peer/team YAML and personas, `.pi/damage-control-rules.yaml`, and `.pi/harnesses/package.json`. When `agent-hub` is installed or kept, keep its required launch companions together: `damage-control`, `damage-control-continue`, and `ask-user-remote`; the managed `just hub` / `hub-solo` recipes load `damage-control-continue`, then `ask-user-remote`, then `agent-hub` so the dispatcher probe sees `ask_user`. Refresh the `justfile` from the **current** source so retired-harness recipes are pruned and new ones added, rewriting only the managed region between the `agent-fleet:harnesses` sentinels so any user recipes survive. Leaving a stale `justfile` (recipes pointing at deleted harness dirs, or no recipe for a new harness) is the regression this prevents.
|
|
24
24
|
|
|
25
|
-
**No mid-apply overwrite prompts.** The
|
|
25
|
+
**No mid-apply overwrite prompts.** The `mod` description already warns that refreshing overwrites local edits. The user's selection is the consent; the Step 9 confirmation is the single gate. During apply, refresh selected items unconditionally — never pause to ask "should I overwrite this file?". Genuine errors (permission denied, missing source) still stop and report.
|
|
26
26
|
|
|
27
|
-
Offer override sections for the workspace's `.ai/agent-fleet-overrides.md` based on the analysis, and record what was installed in `.ai/agent-fleet-setup.md`.
|
|
27
|
+
Offer override sections for the workspace's `.ai/agent-fleet-overrides.md` based on the analysis (print each draft, then `Accept` / `Edit` / `Skip` per section via `ask_user`), and record what was installed in `.ai/agent-fleet-setup.md`. Print the plan as compact action-grouped lines (Add / Refresh / Remove / Keep-count / Records / Method), then confirm with one `ask_user` single-select asked with `displayMode: "inline"` — `Apply — and remove the installer commands` (default) / `Apply — keep the installer commands` / `Adjust picks` / `Cancel` — and write nothing until an Apply is chosen. Then perform the setup, re-scan for any new breakage, and report what changed.
|