@chankov/agent-fleet 0.0.2 → 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.
Files changed (47) hide show
  1. package/.claude/commands/doctor-agent-fleet.md +1 -1
  2. package/.claude/commands/setup-agent-fleet.md +4 -4
  3. package/.opencode/commands/af-doctor-agent-fleet.md +2 -0
  4. package/.opencode/commands/af-setup-agent-fleet.md +1 -1
  5. package/.pi/agents/peers.yaml +4 -0
  6. package/.pi/agents/teams.yaml +2 -2
  7. package/.pi/harnesses/agent-hub/README.md +57 -4
  8. package/.pi/harnesses/agent-hub/index.ts +236 -80
  9. package/.pi/harnesses/agent-hub/research-retention.js +34 -0
  10. package/.pi/harnesses/ask-user-remote/README.md +2 -0
  11. package/.pi/harnesses/coms/README.md +11 -0
  12. package/.pi/prompts/doctor-agent-fleet.md +1 -1
  13. package/.pi/prompts/setup-agent-fleet.md +4 -4
  14. package/README.md +102 -540
  15. package/agents/architect.md +1 -1
  16. package/agents/planner.md +1 -1
  17. package/agents/security-auditor.md +1 -1
  18. package/bin/snapshot-version.js +17 -1
  19. package/codex/CONDUCTOR.md +148 -0
  20. package/docs/ARCHITECTURE.md +165 -0
  21. package/docs/agent-fleet-setup.md +1 -0
  22. package/docs/claude-code-coms-bridge.md +10 -0
  23. package/docs/codex-remote-conductor.md +170 -0
  24. package/docs/coms-hermes-bridge.md +121 -0
  25. package/docs/getting-started.md +14 -0
  26. package/docs/npm-install.md +2 -0
  27. package/docs/pi-setup.md +2 -0
  28. package/hermes/README.md +48 -0
  29. package/hermes/skills/hub-conductor/SKILL.md +84 -0
  30. package/hermes/skills/hub-liaison/SKILL.md +84 -0
  31. package/justfile +100 -13
  32. package/package.json +10 -3
  33. package/scripts/codex-conductor.ts +41 -0
  34. package/scripts/codex-remote-control.ts +167 -0
  35. package/scripts/coms-cli.ts +311 -199
  36. package/scripts/coms-hermes-bridge.ts +2 -2
  37. package/scripts/lib/codex-conductor.ts +88 -0
  38. package/scripts/lib/codex-remote-control.ts +480 -0
  39. package/scripts/lib/coms-envelope.ts +51 -6
  40. package/scripts/lib/herdr-layout.ts +18 -3
  41. package/scripts/lib/hermes-bridge-core.ts +4 -4
  42. package/scripts/lib/team-project.ts +85 -1
  43. package/scripts/team-up.ts +77 -18
  44. package/skills/guided-workspace-setup/SKILL.md +123 -97
  45. package/skills/guided-workspace-setup/companion-manifest.json +33 -0
  46. package/skills/peer-coms/SKILL.md +9 -0
  47. package/systemd/user/agent-fleet-codex-remote-control.service.in +23 -0
@@ -0,0 +1,121 @@
1
+ # coms Hermes bridge
2
+
3
+ Protocol contract for the Hermes ⇄ pi `coms` bridge. The first implemented daemon is `scripts/coms-hermes-bridge.ts`, which registers a `user-remote` peer and turns coms prompt envelopes into Hermes/Telegram questions.
4
+
5
+ ## Pieces
6
+
7
+ | Piece | Role |
8
+ | --- | --- |
9
+ | `scripts/coms-hermes-bridge.ts` | Daemon peer, default name `user-remote`, purpose `Remote human via Hermes/Telegram`. Accepts prompt, cancel, and ping envelopes. |
10
+ | `scripts/lib/hermes-bridge-core.ts` | Pure contract logic: qid validation, Telegram formatting, answer-file validation, answer mapping, timeout outcome, state transitions, and log records. |
11
+ | `scripts/lib/coms-envelope.ts` | Shared non-pi envelope wire shapes, including additive `cancel` envelopes. |
12
+ | `~/.pi/coms/hermes-bridge/questions/` | Private answer-file wire written by the Hermes gateway/liaison. |
13
+ | `~/.pi/coms/hermes-bridge/log.ndjson` | Bridge observability log. |
14
+
15
+ ## user-remote topology
16
+
17
+ 1. A pi peer sends a coms `prompt` envelope to `user-remote`.
18
+ 2. The bridge derives `qid` from `prompt.msg_id`, formats the question, and runs `hermes send --to <target> <message>` (`<target>` defaults to `telegram`).
19
+ 3. The human replies in Telegram; the Hermes gateway/liaison writes the answer file.
20
+ 4. The bridge polls the questions directory, validates the file, maps the answer, sends a coms `response` envelope, and removes the answer file.
21
+
22
+ ## Protocol contract v1
23
+
24
+ ### qid and correlation
25
+
26
+ `qid` is exactly the prompt envelope's `msg_id`. It must match the 26-character Crockford ULID regex `^[0-9A-HJKMNP-TV-Z]{26}$`. The same `qid` is the only correlation key across coms, Telegram, answer files, state, and logs.
27
+
28
+ ### Telegram question format
29
+
30
+ `formatTelegramQuestion` emits UTF-16 text capped at 4096 code units:
31
+
32
+ ```text
33
+ ❓ [HUB-Q:<qid>] <question>
34
+
35
+ Context: <context, truncated if needed>
36
+
37
+ Options:
38
+ 1. <title> — <description>
39
+ ...
40
+
41
+ ↩ Reply to this message, or type: HUB-Q:<qid>: <answer>
42
+ ```
43
+
44
+ `Context:` is omitted when absent. `Options:` is omitted when no options are supplied. Context receives the remaining budget after the header, options, and reply instruction.
45
+
46
+ ### Answer-file path, schema, and validation
47
+
48
+ The private wire path is:
49
+
50
+ ```text
51
+ ~/.pi/coms/hermes-bridge/questions/<qid>.answer.json
52
+ ```
53
+
54
+ Schema:
55
+
56
+ ```json
57
+ {
58
+ "qid": "<26-character Crockford ULID>",
59
+ "answer": "<text>",
60
+ "answered_by": "telegram:<user>",
61
+ "at": "<ISO timestamp>"
62
+ }
63
+ ```
64
+
65
+ Validation rejects and ignores files unless all conditions hold: filename ends in `.answer.json`; filename qid is valid; filename qid is currently pending; JSON parses; object fields match the schema; `at` parses as a timestamp; and body `qid` equals the filename qid. Rejection reasons are `invalid_path`, `invalid_qid`, `foreign_qid`, `invalid_json`, `invalid_schema`, and `qid_mismatch`; the daemon logs rejected files as `answer_rejected` and removes them. Exception: an `invalid_json` file is treated as a possible partial write and left in place for a short grace window (`max(2 × poll interval, 1s)` from first sighting); it is rejected and removed only if it still fails to parse after the grace expires.
66
+
67
+ ### Answer mapping
68
+
69
+ If options exist and the trimmed answer is a 1-based number for an option, the response is `{ "kind": "selection", "selections": ["<option title>"] }`. If options exist and the trimmed answer case-insensitively equals an option title, it maps to the same selection shape. All other answers map to `{ "kind": "freeform", "text": "<trimmed answer>" }`.
70
+
71
+ ### Cancel semantics
72
+
73
+ `cancel` is an additive coms envelope with shape `{ "type": "cancel", "msg_id", "from", "to", "created_at", "ref_msg_id" }`; `ref_msg_id` is the target `qid`. The bridge acks well-formed cancel envelopes before handling them.
74
+
75
+ For a pending qid, cancel clears the timeout, removes the pending question, records terminal state `cancelled`, appends a `cancelled` log event, and sends a Telegram note: `✖ [HUB-Q:<qid>] The question was cancelled — it was answered from the console.` Cancel for a non-pending or invalid qid is a no-op after the envelope ack. A later answer file for a closed qid is treated as `late_answer`: logged, removed, and answered in Telegram with a polite ignored note; no response envelope is sent.
76
+
77
+ ### Timeouts
78
+
79
+ The per-question remote timeout defaults to `PI_COMS_TIMEOUT_MS`, or `1800000` ms when unset/invalid; `--timeout <ms>` overrides it. On timeout, the bridge removes the pending question, records terminal state `timeout`, logs `timeout`, sends the Telegram note `⌛ [HUB-Q:<qid>] The question timed out after <ms>ms.`, and sends an error response envelope with error `no remote answer within <ms>ms` and `response: null`.
80
+
81
+ ### States
82
+
83
+ Question states are in-memory per qid: `pending`, `delivered`, `answered`, `cancelled`, and `timeout`. Implemented transitions are: `null + question_received → pending`; `pending + delivered → delivered`; `pending + delivery_error → null`; `pending|delivered + answered → answered` (the daemon currently answers from delivered or pending if the file arrives quickly); `pending|delivered + cancelled → cancelled`; `pending|delivered + timeout → timeout`; and terminal `answered|cancelled|timeout + late_answer` remains terminal.
84
+
85
+ ### ndjson logging
86
+
87
+ The bridge appends one JSON object per line to `~/.pi/coms/hermes-bridge/log.ndjson`. Core log records have shape `{ "at": "<ISO>", "qid": "<qid>", "event": "<event>", "detail"?: <value> }`. Contract events are `question_received`, `delivered`, `delivery_error`, `answered`, `cancelled`, `timeout`, and `late_answer`; the daemon also writes `answer_rejected` for invalid answer files. Ping agent cards report `queue_depth` as the current number of pending questions.
88
+
89
+ ## Hermes as conductor
90
+
91
+ Hermes can also act as the conductor without this daemon: use `coms-cli list` to discover peers and `coms-cli send --await --timeout <ms>` to delegate to hub-team pi peers, then synthesize the results for the human. This conductor topology uses the existing coms CLI as the bridge; no standing Hermes peer is required.
92
+
93
+ Launch a visible conductor workspace with:
94
+
95
+ ```bash
96
+ just conductor docs # live herdr workspace: conductor pane + docs team panes
97
+ just conductor-dry docs # no herdr calls; prints the planned layout JSON
98
+ ```
99
+
100
+ The live recipe reuses `scripts/team-up.ts --conductor`: it creates a normal herdr workspace labeled `<worktree-tag>-conductor-<team>` (the tag is the last dot-segment of the checkout's basename, so the same team from a different worktree gets its own workspace), places a `conductor` pane running `hermes -p dev`, and tiles the chosen team beside it. Team peers keep their normal coms harness and herdr presence reporting, so they continue to show agent state in the sidebar; Hermes' own herdr-agent-state plugin is responsible for the conductor pane's state.
101
+
102
+ Hard boundary: the Hermes conductor must not run `herdr` commands, drive panes, create/kill workspaces, or manage fleet lifecycle. Herdr driving stays with the human/orchestrator so the damage-control model remains intact; see `.pi/damage-control-rules.yaml` for the authoritative no-herdr boundary. Hermes may only operate inside the project coms pool through the documented coms CLI commands.
103
+
104
+ ## Hermes and the experimental Codex conductor
105
+
106
+ Hermes/Telegram remains the **inbound** human `ask_user` complement to the
107
+ experimental Codex remote-control conductor. Codex is outbound-initiated,
108
+ approval-gated, and serialized; it is not an inbound question channel. The Codex user service and control-pane lifecycle are
109
+ separate from Hermes. See the [experimental Codex operator runbook](codex-remote-conductor.md).
110
+
111
+ Both conductor contracts are advisory outside Pi damage-control: Pi wraps Pi
112
+ tool calls, not Hermes or Codex, and neither has an OS command allowlist.
113
+ Human confirmation, approvals, and sandboxing reduce risk but do not
114
+ technically enforce either external contract.
115
+
116
+ ## Deferred
117
+
118
+ - Standing conductor peer for pi → Hermes inbound messages.
119
+ - Telegram-driven conductor profile.
120
+ - Group/multi-recipient questions and non-text answers.
121
+ - Kanban-driven orchestration on top of the same conductor contract.
@@ -18,6 +18,20 @@ Each skill is a Markdown file (`SKILL.md`) that describes a specific engineering
18
18
 
19
19
  All three converge on the same `guided-workspace-setup` skill — they only differ in how the source files reach your workspace. None is being deprecated.
20
20
 
21
+ ## Optional experimental Android conductor
22
+
23
+ Linux/pi fleet users can pair Codex Remote Control with ChatGPT Android and delegate one approval-gated task at a time to peers already running in a coms project. It is optional, supports only Codex CLI `0.144.x`, requires Node `22.6+` and user systemd, and does not replace Hermes as the inbound `ask_user` route.
24
+
25
+ ```bash
26
+ cd /path/to/agent-fleet
27
+ just conductor-codex-setup docs --project af
28
+ just conductor-codex-pair
29
+ just conductor-codex-start
30
+ just hub-team docs --project af
31
+ ```
32
+
33
+ The runtime contract is generated under `$HOME/.local/state/agent-fleet/codex-conductor/`, outside the checkout. Pairing is interactive secret-bearing output and must never be captured. Read the complete [Codex conductor runbook](codex-remote-conductor.md) before enabling the service.
34
+
21
35
  ## Quick Start (Any Agent)
22
36
 
23
37
  ### 1. Clone the repository
@@ -56,6 +56,8 @@ The pi package manifest exposes this repo's skills, pi runtime skills, lifecycle
56
56
 
57
57
  It intentionally does not auto-expose this repo's own `.pi/extensions` or harness directories; install those through guided setup or the pi setup docs so their runtime dependencies are handled explicitly. `pi-codex-image-gen` is also not bundled or required; guided setup may offer it as an optional suggested external npm/pi package when package installation is available, and installs it only if selected (`pi install -l npm:pi-codex-image-gen`). Minimal setup works without it.
58
58
 
59
+ The package also ships assets for the **experimental Linux Codex Remote-Control conductor** (`codex/`, `systemd/`, lifecycle/wrapper scripts, recipes, and runbook). Guided setup copies or links those assets with selected pi harnesses but never enables systemd, edits Codex config, starts a service, or pairs a phone. Those remain explicit operator actions and support only Codex CLI `0.144.x`; see [codex-remote-conductor.md](codex-remote-conductor.md). Its managed runtime contract is created later under `$HOME/.local/state/agent-fleet/codex-conductor/`, not inside the npm package or target checkout.
60
+
59
61
  ## Commands
60
62
 
61
63
  ### `npx @chankov/agent-fleet init`
package/docs/pi-setup.md CHANGED
@@ -27,6 +27,8 @@ No plugin, wrapper, or custom system prompt is required for the core workflow.
27
27
 
28
28
  **Recommended companion packages:** [`pi-ask-user`](https://github.com/edlsh/pi-ask-user) adds an interactive `ask_user` tool and bundles an `ask-user` skill. It is bundled automatically when you install `@chankov/agent-fleet` as a pi package; clone/symlink setups should install it separately. `pi-codex-image-gen` is an optional suggested npm/pi extension for image generation; guided setup can offer it when package installation is available, but it is not bundled or required.
29
29
 
30
+ **Experimental phone conductor:** Linux users may pair Codex CLI `0.144.x` with ChatGPT Android to perform human-confirmed outbound delegation to live coms peers. Guided setup installs the repository assets when pi harnesses are selected, but deliberately never changes systemd, Codex auth/config, pairing, or service state. Host setup remains an explicit operator flow; see [Codex Remote-Control Conductor](codex-remote-conductor.md).
31
+
30
32
  ---
31
33
 
32
34
  ## Installation
@@ -0,0 +1,48 @@
1
+ # Hermes artifacts
2
+
3
+ This directory contains in-repository Hermes skills for the coms Hermes bridge plan. They are source artifacts only; this pass does not modify `~/.hermes`.
4
+
5
+ ## Skills
6
+
7
+ - `skills/hub-liaison/` — gateway-side Telegram liaison. It writes `~/.pi/coms/hermes-bridge/questions/<qid>.answer.json` answer files for `[HUB-Q:<qid>]` questions consumed by `scripts/coms-hermes-bridge.ts`.
8
+ - `skills/hub-conductor/` — dev-profile conductor. It uses `scripts/coms-cli.ts list` and `scripts/coms-cli.ts send --await --timeout` to delegate to live pi hub-team peers, while preserving the no-herdr damage-control boundary.
9
+
10
+ ## Install
11
+
12
+ Install a skill into the desired Hermes profile with either option supported by your Hermes setup:
13
+
14
+ ```bash
15
+ hermes skills install hermes/skills/hub-liaison
16
+ hermes skills install hermes/skills/hub-conductor
17
+ ```
18
+
19
+ Or copy the skill directories into the profile's skills directory:
20
+
21
+ ```bash
22
+ cp -R hermes/skills/hub-liaison ~/.hermes/<profile>/skills/
23
+ cp -R hermes/skills/hub-conductor ~/.hermes/<profile>/skills/
24
+ ```
25
+
26
+ Use `hub-liaison` in the gateway-owning Telegram profile and `hub-conductor` in the human's dev/conductor profile. Verify availability with your normal Hermes skill listing command before relying on them.
27
+
28
+ ## Usage notes
29
+
30
+ For `hub-liaison`, ensure the Telegram-capable profile has terminal/file-write tools enabled so it can create exactly `~/.pi/coms/hermes-bridge/questions/<qid>.answer.json` and nothing outside that questions directory.
31
+
32
+ For `hub-conductor`, either start the pi team/pool outside Hermes first, or use the repo recipe to create a visible conductor workspace:
33
+
34
+ ```bash
35
+ just conductor docs # conductor pane (`hermes -p dev`) + docs team panes
36
+ just conductor-dry docs # dry-run layout, no herdr calls
37
+ ```
38
+
39
+ Inside Hermes, discover and delegate only through coms:
40
+
41
+ ```bash
42
+ node --experimental-strip-types /home/nchankov/repos/agent-fleet/scripts/coms-cli.ts list
43
+ node --experimental-strip-types /home/nchankov/repos/agent-fleet/scripts/coms-cli.ts send <peer> "<task>" --await --timeout 300000
44
+ ```
45
+
46
+ Hermes must not drive herdr panes or workspaces; the `just conductor` recipe creates the pane before Hermes starts. The no-herdr boundary is documented in `docs/coms-hermes-bridge.md` and governed by `.pi/damage-control-rules.yaml`.
47
+
48
+ Hermes/Telegram remains the inbound `ask_user` path beside the experimental Codex remote-control conductor. Codex is outbound-initiated, approval-gated, and serialized through the validated wrapper; both Hermes and Codex contracts remain advisory outside Pi damage-control, and neither external process has an OS command allowlist. See the [Codex operator runbook](../docs/codex-remote-conductor.md).
@@ -0,0 +1,84 @@
1
+ ---
2
+ name: hub-conductor
3
+ description: Conducts local pi hub-team peers from Hermes through coms-cli list/send --await, while preserving no-herdr and pool-scope damage-control boundaries.
4
+ ---
5
+
6
+ # Hub Conductor
7
+
8
+ ## Overview
9
+
10
+ You are the human-facing conductor for a local pi coms pool. Your job is to decompose the human's request, discover live hub-team peers, delegate bounded tasks through `scripts/coms-cli.ts`, wait for results, and synthesize a final answer.
11
+
12
+ This is conductor-side orchestration only: the existing coms CLI is the bridge. You do not need a daemon or standing Hermes peer to ask pi peers for work.
13
+
14
+ ## When to Use
15
+
16
+ Use this skill when:
17
+
18
+ - the human asks Hermes to coordinate pi hub-team peers;
19
+ - a task benefits from parallel specialist work such as research, implementation, docs, review, or testing;
20
+ - you need to inspect which local peers are alive before deciding who should do what;
21
+ - a previous peer response needs follow-up, retry, or synthesis.
22
+
23
+ Do not use it for single-step work Hermes can safely complete alone without peer help.
24
+
25
+ ## Process
26
+
27
+ 1. Identify the repository root and set a shell variable for it when useful:
28
+
29
+ ```bash
30
+ REPO=/home/nchankov/repos/agent-fleet
31
+ ```
32
+
33
+ 2. Discover live peers in the current coms project:
34
+
35
+ ```bash
36
+ node --experimental-strip-types "$REPO/scripts/coms-cli.ts" list
37
+ ```
38
+
39
+ Use `--project <name>` when the human or launch recipe specifies a non-default project.
40
+
41
+ 3. Choose peers by their listed name and purpose. Send bounded, self-contained prompts that include the expected deliverable and any acceptance assertions the peer must prove.
42
+
43
+ 4. Delegate with an explicit timeout and wait for the response:
44
+
45
+ ```bash
46
+ node --experimental-strip-types "$REPO/scripts/coms-cli.ts" send <peer-name> \
47
+ "<bounded task; include required output and evidence>" \
48
+ --await --timeout 300000
49
+ ```
50
+
51
+ Use a longer timeout for build/test/review tasks when needed. Every `send --await` must include `--timeout <ms>`.
52
+
53
+ 5. If a peer times out or is missing, retry at most once when the task still matters. Otherwise report that peer as unavailable and continue with the best available evidence.
54
+
55
+ 6. Synthesize peer outputs for the human. Name which peers were asked, what each returned, what evidence supports the result, and what remains unproven.
56
+
57
+ 7. For inbound conversational requests, answer directly in chat after any peer delegation; keep the final response self-contained because the human sees your synthesis, not the peer transcript.
58
+
59
+ ## Hard Boundaries
60
+
61
+ - **Advisory contract only.** This skill runs in an external Hermes process. Pi damage-control wraps Pi tool calls, not Hermes; this contract and any human confirmation reduce risk but do not provide an OS command allowlist or technical enforcement.
62
+ - **No herdr driving.** Do not run `herdr pane`, `herdr workspace`, pane lifecycle commands, workspace lifecycle commands, or any command that creates, closes, restarts, or drives panes. Rationale: fleet lifecycle belongs to the human/orchestrator so the `.pi/damage-control-rules.yaml` model remains intact and Hermes cannot accidentally destroy or commandeer active work.
63
+ - **Pool scope only.** Operate only through peers visible in the current project coms pool (`coms-cli list`, then `coms-cli send ... --await`). Do not widen to unrelated projects, global registries, hidden explicit peers, or external agent pools unless the human explicitly starts that topology and names the target project. Rationale: coms pool boundaries keep delegation auditable and prevent cross-project leakage.
64
+ - **No secret or bulk-data relay.** Send bounded prompts and path references, not secrets or whole-file dumps. Rationale: peers need task context, not uncontrolled data replication.
65
+
66
+ ## Red Flags
67
+
68
+ - Running or proposing `herdr` pane/workspace commands yourself.
69
+ - Sending to a peer that was not shown by `coms-cli list` for the intended project.
70
+ - Omitting `--await` or `--timeout` for delegated work that the human expects you to synthesize.
71
+ - Retrying repeatedly after a timeout instead of one retry then reporting the gap.
72
+ - Treating a peer's prose success claim as proof when it lacks named evidence.
73
+ - Expanding beyond the repository/project pool without explicit human direction.
74
+
75
+ ## Verification
76
+
77
+ Before reporting done, check:
78
+
79
+ - [ ] `coms-cli list` was run for the intended project and the selected peers were visible.
80
+ - [ ] Every delegated task used `coms-cli send <peer> ... --await --timeout <ms>`.
81
+ - [ ] Peer responses were synthesized with named evidence and unresolved gaps.
82
+ - [ ] At most one retry was used for any timeout or missing peer.
83
+ - [ ] No `herdr` command was run or requested by Hermes.
84
+ - [ ] No delegation crossed outside the intended project coms pool.
@@ -0,0 +1,84 @@
1
+ ---
2
+ name: hub-liaison
3
+ description: On any Telegram HUB-Q reply ALWAYS write the pi hub bridge answer file — even when the thread shows cancel/closed/timeout notes; the bridge classifies late answers itself. Use when a Telegram message replies to or contains a [HUB-Q:<qid>] marker.
4
+ ---
5
+
6
+ # Hub Liaison
7
+
8
+ ## Overview
9
+
10
+ You are the gateway-side liaison between a human Telegram reply and the pi `user-remote` coms peer. When a Telegram message correlates to a hub question marker, write one answer file for the bridge. Do not answer by paraphrasing in chat only; the bridge only consumes the file.
11
+
12
+ ## When to Use
13
+
14
+ Use this skill when an incoming Telegram message either:
15
+
16
+ - replies to a message that contains `[HUB-Q:<qid>]`, or
17
+ - contains the explicit prefix `HUB-Q:<qid>:`.
18
+
19
+ `<qid>` must be a 26-character Crockford ULID matching:
20
+
21
+ ```text
22
+ ^[0-9A-HJKMNP-TV-Z]{26}$
23
+ ```
24
+
25
+ Ignore non-matching messages. If a message is ambiguous and there is more than one plausible question marker, ask the human to reply to the original question or use `HUB-Q:<qid>: <answer>`.
26
+
27
+ ## Correlation Rules
28
+
29
+ 1. Prefer the qid from the replied-to message marker: `[HUB-Q:<qid>]`.
30
+ 2. If there is no replied-to marker, accept a message prefix exactly shaped as `HUB-Q:<qid>: <answer>`.
31
+ 3. The answer text is the Telegram reply body, except for prefix-form messages where the answer text is everything after `HUB-Q:<qid>:`.
32
+ 4. Preserve the human's answer text exactly except for trimming leading/trailing whitespace around the extracted answer.
33
+ 5. Never invent or alter the qid. If the qid does not match the regex above, do not write a file.
34
+ 6. If a human message contains or replies to a `[HUB-Q:<qid>]` question, write the answer file even when the thread also contains a cancel/closed note or the user appears to be answering after cancellation. Do not decide whether the question is still open; the bridge validates pending vs. late and sends the appropriate polite closed note.
35
+
36
+ ## Process
37
+
38
+ 1. Extract `<qid>` and `<answer>` using the correlation rules.
39
+ 2. Confirm `<answer>` is non-empty. If it is empty, ask the human for the answer text.
40
+ 3. Do not suppress the write because the question appears canceled, closed, timed out, or answered locally. That state belongs to the bridge, not this skill.
41
+ 4. Write exactly this file path, replacing `<qid>` with the extracted qid:
42
+
43
+ ```text
44
+ ~/.pi/coms/hermes-bridge/questions/<qid>.answer.json
45
+ ```
46
+
47
+ 5. The JSON content must use exactly these fields:
48
+
49
+ ```json
50
+ {
51
+ "qid": "<qid>",
52
+ "answer": "<answer>",
53
+ "answered_by": "telegram:<user>",
54
+ "at": "<ISO timestamp>"
55
+ }
56
+ ```
57
+
58
+ - `qid`: the extracted 26-character qid.
59
+ - `answer`: the extracted answer text.
60
+ - `answered_by`: `telegram:<user>`, using the Telegram username/handle when available; otherwise use a stable Telegram sender identifier.
61
+ - `at`: the current ISO-8601 timestamp.
62
+
63
+ 6. After writing the file, briefly confirm to the human that the answer was delivered for `HUB-Q:<qid>`; if it was late, the bridge will handle the closed-question response.
64
+
65
+ ## Write Boundary
66
+
67
+ Hard rule: never write outside `~/.pi/coms/hermes-bridge/questions/` for this skill. Do not create, edit, or delete files elsewhere. The bridge validates and consumes only `~/.pi/coms/hermes-bridge/questions/<qid>.answer.json`; any other path is outside the private wire contract.
68
+
69
+ ## Red Flags
70
+
71
+ - A message has no `[HUB-Q:<qid>]` marker and no `HUB-Q:<qid>:` prefix.
72
+ - The qid fails `^[0-9A-HJKMNP-TV-Z]{26}$`.
73
+ - The answer text is empty after extraction.
74
+ - The requested write path is not under `~/.pi/coms/hermes-bridge/questions/`.
75
+ - The human asks you to modify bridge logs, registry files, or any unrelated project files.
76
+ - Suppressing an otherwise correlated answer because a cancel/closed note is visible in the thread.
77
+
78
+ ## Verification
79
+
80
+ - [ ] The qid came from `[HUB-Q:<qid>]` or `HUB-Q:<qid>:` and matches the regex.
81
+ - [ ] The answer file path is exactly `~/.pi/coms/hermes-bridge/questions/<qid>.answer.json`.
82
+ - [ ] The JSON has exactly `qid`, `answer`, `answered_by`, and `at` with an ISO timestamp.
83
+ - [ ] No file outside `~/.pi/coms/hermes-bridge/questions/` was written.
84
+ - [ ] Correlated late/canceled answers were still written for the bridge to classify.
package/justfile CHANGED
@@ -20,6 +20,14 @@
20
20
  # >>> agent-fleet:harnesses — managed region (regenerated on upgrade; edits inside are overwritten) >>>
21
21
  set dotenv-load := true
22
22
 
23
+ # How recipes run the fleet TS scripts. The preserve-symlinks flags matter for
24
+ # symlink installs (guided-workspace-setup's `symlink` method): there
25
+ # scripts/*.ts are links whose realpath sits under .pi/npm/node_modules/, and
26
+ # Node refuses --experimental-strip-types for anything under node_modules once
27
+ # paths are realpath'd. Keeping symlink paths avoids that; copy installs are
28
+ # unaffected (the fleet scripts import only relative paths + node builtins).
29
+ node_ts := "node --experimental-strip-types --preserve-symlinks --preserve-symlinks-main"
30
+
23
31
  # List all recipes
24
32
  default:
25
33
  @just --list
@@ -72,20 +80,20 @@ hub-solo *args:
72
80
  # simultaneous boots race on the auth.json lock and lose their logins.
73
81
  # Hidden from `just --list` because recipes prefixed with `_` are private.
74
82
  _peer persona name="" model="" session="" project="default":
75
- d="${AGENT_FLEET_SPAWN_DELAY:-0}"; if [ "$d" != "0" ]; then echo "⏳ waiting ${d}s for the pi auth pre-warm (stale OAuth token)"; sleep "$d"; fi; node --experimental-strip-types scripts/peer-banner.ts {{persona}} {{name}} 2>/dev/null || true; persona_path="agents/{{persona}}.md"; if [ ! -f "$persona_path" ]; then persona_path=".pi/agents/{{persona}}.md"; fi; pi -e .pi/harnesses/coms/index.ts -e .pi/extensions/compact-and-continue/index.ts --project {{project}} --append-system-prompt "$persona_path" {{ if name != "" { "--name " + name } else { "" } }} {{ if model != "" { "--model " + model } else { "" } }} {{ if session != "" { "--session " + session } else { "" } }}
83
+ d="${AGENT_FLEET_SPAWN_DELAY:-0}"; if [ "$d" != "0" ]; then echo "⏳ waiting ${d}s for the pi auth pre-warm (stale OAuth token)"; sleep "$d"; fi; {{node_ts}} scripts/peer-banner.ts {{persona}} {{name}} 2>/dev/null || true; persona_path="agents/{{persona}}.md"; if [ ! -f "$persona_path" ]; then persona_path=".pi/agents/{{persona}}.md"; fi; pi -e .pi/harnesses/coms/index.ts -e .pi/extensions/compact-and-continue/index.ts --project {{project}} --append-system-prompt "$persona_path" {{ if name != "" { "--name " + name } else { "" } }} {{ if model != "" { "--model " + model } else { "" } }} {{ if session != "" { "--session " + session } else { "" } }}
76
84
 
77
85
  # Like _peer, but also loads extra always-on extensions (comma-separated names under
78
86
  # .pi/extensions/) into the peer process — e.g. a chrome-devtools-mcp browser-debug peer
79
87
  # whose `chrome_devtools__*` tools a normal --no-extensions subagent could not get.
80
88
  _peer-plus extensions persona name="" model="" session="" project="default":
81
- d="${AGENT_FLEET_SPAWN_DELAY:-0}"; if [ "$d" != "0" ]; then echo "⏳ waiting ${d}s for the pi auth pre-warm (stale OAuth token)"; sleep "$d"; fi; node --experimental-strip-types scripts/peer-banner.ts {{persona}} {{name}} 2>/dev/null || true; persona_path="agents/{{persona}}.md"; if [ ! -f "$persona_path" ]; then persona_path=".pi/agents/{{persona}}.md"; fi; extra=""; old_ifs="$IFS"; IFS=','; for x in {{extensions}}; do x="$(echo "$x" | xargs)"; if [ -n "$x" ]; then extra="$extra -e .pi/extensions/$x/index.ts"; fi; done; IFS="$old_ifs"; pi -e .pi/harnesses/coms/index.ts -e .pi/extensions/compact-and-continue/index.ts $extra --project {{project}} --append-system-prompt "$persona_path" {{ if name != "" { "--name " + name } else { "" } }} {{ if model != "" { "--model " + model } else { "" } }} {{ if session != "" { "--session " + session } else { "" } }}
89
+ d="${AGENT_FLEET_SPAWN_DELAY:-0}"; if [ "$d" != "0" ]; then echo "⏳ waiting ${d}s for the pi auth pre-warm (stale OAuth token)"; sleep "$d"; fi; {{node_ts}} scripts/peer-banner.ts {{persona}} {{name}} 2>/dev/null || true; persona_path="agents/{{persona}}.md"; if [ ! -f "$persona_path" ]; then persona_path=".pi/agents/{{persona}}.md"; fi; extra=""; old_ifs="$IFS"; IFS=','; for x in {{extensions}}; do x="$(echo "$x" | xargs)"; if [ -n "$x" ]; then extra="$extra -e .pi/extensions/$x/index.ts"; fi; done; IFS="$old_ifs"; pi -e .pi/harnesses/coms/index.ts -e .pi/extensions/compact-and-continue/index.ts $extra --project {{project}} --append-system-prompt "$persona_path" {{ if name != "" { "--name " + name } else { "" } }} {{ if model != "" { "--model " + model } else { "" } }} {{ if session != "" { "--session " + session } else { "" } }}
82
90
 
83
91
  # Internal helper for team-up: a `runner: claude-code` peer — interactive
84
92
  # Claude Code plus its coms bridge (scripts/coms-claude-bridge.ts) in ONE pane.
85
93
  # The bridge registers the pane as coms peer <name>; the trailing session
86
94
  # positional maps to `claude --resume <id>` for team-resume.
87
95
  _claude-peer name model="" session="" project="default":
88
- node --experimental-strip-types scripts/coms-claude-bridge.ts --name {{name}} --project {{project}} & bridge_pid=$!; trap 'kill $bridge_pid 2>/dev/null' EXIT; claude {{ if model != "" { "--model " + model } else { "" } }} {{ if session != "" { "--resume " + session } else { "" } }}
96
+ {{node_ts}} scripts/coms-claude-bridge.ts --name {{name}} --project {{project}} & bridge_pid=$!; trap 'kill $bridge_pid 2>/dev/null' EXIT; claude {{ if model != "" { "--model " + model } else { "" } }} {{ if session != "" { "--resume " + session } else { "" } }}
89
97
 
90
98
  # The team recipes below take the team as a positional arg (defaults to "full")
91
99
  # and pass everything after it straight to the script.
@@ -94,7 +102,10 @@ _claude-peer name model="" session="" project="default":
94
102
  # where the tag is the last dot-segment of this directory's basename (main.wt2 →
95
103
  # wt2, ringithub.end2 → end2, plain agent-fleet → agent-fleet). So the same team
96
104
  # launched from different repos/worktrees gets its own workspace (wt2-hub-plan vs
97
- # end2-hub-plan) instead of colliding on a shared label.
105
+ # end2-hub-plan) instead of colliding on a shared label. This is not global
106
+ # uniqueness: unrelated checkouts with the same basename/final dot-segment can
107
+ # still collide. Existing-workspace refusal prevents clobbering; it does not
108
+ # prove the labels are unique.
98
109
  #
99
110
  # `--project <name>` is a SEPARATE axis: it scopes the coms peer POOL. Without it
100
111
  # every peer lands in the shared "default" pool, where teams launched from OTHER
@@ -108,54 +119,130 @@ _claude-peer name model="" session="" project="default":
108
119
  # e.g. just team-up full
109
120
  # just team-up review --project af
110
121
  team-up team="full" *args:
111
- node --experimental-strip-types scripts/team-up.ts --team {{team}} {{args}}
122
+ {{node_ts}} scripts/team-up.ts --team {{team}} {{args}}
112
123
 
113
124
  # Team up (dry run): print the resolved layout + per-peer commands without touching herdr.
114
125
  # e.g. just team-up-dry full
115
126
  # just team-up-dry review --project af
116
127
  team-up-dry team="full" *args:
117
- node --experimental-strip-types scripts/team-up.ts --team {{team}} --dry-run {{args}}
128
+ {{node_ts}} scripts/team-up.ts --team {{team}} --dry-run {{args}}
118
129
 
119
130
  # Hub + team in ONE herdr workspace: the guarded hub (`just hub`) in a larger
120
131
  # main pane, the team's peers tiled beside it.
121
132
  # e.g. just hub-team docs
122
133
  # just hub-team review --project af
123
134
  hub-team team="full" *args:
124
- node --experimental-strip-types scripts/team-up.ts --team {{team}} --hub {{args}}
135
+ {{node_ts}} scripts/team-up.ts --team {{team}} --hub {{args}}
125
136
 
126
137
  # Hub + team (dry run): print the combined layout without touching herdr.
127
138
  # e.g. just hub-team-dry review --project af
128
139
  hub-team-dry team="full" *args:
129
- node --experimental-strip-types scripts/team-up.ts --team {{team}} --hub --dry-run {{args}}
140
+ {{node_ts}} scripts/team-up.ts --team {{team}} --hub --dry-run {{args}}
130
141
 
131
142
  # Hermes conductor + team in ONE herdr workspace: Hermes dev profile in a conductor pane,
132
143
  # the team's peers tiled beside it. Hermes delegates via coms-cli and never drives herdr.
133
144
  # e.g. just conductor docs --project af
134
145
  conductor team="full" *args:
135
- node --experimental-strip-types scripts/team-up.ts --team {{team}} --conductor {{args}}
146
+ {{node_ts}} scripts/team-up.ts --team {{team}} --conductor {{args}}
136
147
 
137
148
  # Hermes conductor + team (dry run): print the combined layout without touching herdr.
138
149
  # e.g. just conductor-dry docs --project af
139
150
  conductor-dry team="full" *args:
140
- node --experimental-strip-types scripts/team-up.ts --team {{team}} --conductor --dry-run {{args}}
151
+ {{node_ts}} scripts/team-up.ts --team {{team}} --conductor --dry-run {{args}}
152
+
153
+ # Experimental Codex remote-control conductor lifecycle (verified with CLI
154
+ # 0.144.x). Pairing stays interactive and its short-lived code must never be
155
+ # captured. The user service is singleton across repos/projects.
156
+ # e.g. just conductor-codex-setup docs --project af
157
+ conductor-codex-setup team="full" *args:
158
+ {{node_ts}} scripts/codex-remote-control.ts setup-conductor --codex-bin "$(command -v codex)" --repo-root "$(pwd -P)" --coms-dir "$HOME/.pi/coms" --team "{{team}}" --timeout 300000 {{args}}
159
+
160
+ conductor-codex-reconfigure team="full" *args:
161
+ {{node_ts}} scripts/codex-remote-control.ts reconfigure-conductor --codex-bin "$(command -v codex)" --repo-root "$(pwd -P)" --coms-dir "$HOME/.pi/coms" --team "{{team}}" --timeout 300000 {{args}}
162
+
163
+ conductor-codex-pair:
164
+ {{node_ts}} scripts/codex-remote-control.ts pair
165
+
166
+ conductor-codex-start:
167
+ {{node_ts}} scripts/codex-remote-control.ts start
168
+
169
+ conductor-codex-status:
170
+ {{node_ts}} scripts/codex-remote-control.ts status
171
+
172
+ conductor-codex-stop:
173
+ {{node_ts}} scripts/codex-remote-control.ts stop
174
+
175
+ conductor-codex-recover:
176
+ {{node_ts}} scripts/codex-remote-control.ts recover --confirm operator-confirmed
177
+
178
+ conductor-codex-uninstall:
179
+ {{node_ts}} scripts/codex-remote-control.ts uninstall --confirm operator-confirmed
180
+
181
+ # Codex conductor + team in one workspace. The root is a requested-state
182
+ # control pane; systemd owns the remote-control daemon.
183
+ # e.g. just conductor-codex docs --project af
184
+ conductor-codex team="full" *args:
185
+ {{node_ts}} scripts/team-up.ts --team {{team}} --conductor codex {{args}}
186
+
187
+ conductor-codex-dry team="full" *args:
188
+ {{node_ts}} scripts/team-up.ts --team {{team}} --conductor codex --dry-run {{args}}
189
+
190
+ # Legacy pilot aliases retained for the 0.144.x experimental rollout.
191
+ # Setup/reconfigure resolve the selected binary and persist one validated
192
+ # repo/project/team/coms context.
193
+ # e.g. just conductor-codex-pilot-setup docs --project af
194
+ conductor-codex-pilot-setup team="full" *args:
195
+ {{node_ts}} scripts/codex-remote-control.ts setup-pilot --codex-bin "$(command -v codex)" --repo-root "$(pwd -P)" --coms-dir "$HOME/.pi/coms" --team "{{team}}" --timeout 300000 {{args}}
196
+
197
+ conductor-codex-pilot-reconfigure team="full" *args:
198
+ {{node_ts}} scripts/codex-remote-control.ts reconfigure-pilot --codex-bin "$(command -v codex)" --repo-root "$(pwd -P)" --coms-dir "$HOME/.pi/coms" --team "{{team}}" --timeout 300000 {{args}}
199
+
200
+ conductor-codex-pilot-pair:
201
+ {{node_ts}} scripts/codex-remote-control.ts pair
202
+
203
+ conductor-codex-pilot-start:
204
+ {{node_ts}} scripts/codex-remote-control.ts start
205
+
206
+ conductor-codex-pilot-status:
207
+ {{node_ts}} scripts/codex-remote-control.ts status
208
+
209
+ conductor-codex-pilot-stop:
210
+ {{node_ts}} scripts/codex-remote-control.ts stop
211
+
212
+ conductor-codex-pilot-recover:
213
+ {{node_ts}} scripts/codex-remote-control.ts recover --confirm operator-confirmed
214
+
215
+ conductor-codex-pilot-uninstall:
216
+ {{node_ts}} scripts/codex-remote-control.ts uninstall --confirm operator-confirmed
217
+
218
+ # Legacy pilot live aliases use the same verified implementation. The root pane
219
+ # is the lifecycle helper's foreground control pane, never a daemon command.
220
+ # e.g. just conductor-codex-pilot docs --project af
221
+ conductor-codex-pilot team="full" *args:
222
+ {{node_ts}} scripts/team-up.ts --team {{team}} --conductor codex {{args}}
223
+
224
+ # Legacy pilot dry-run alias.
225
+ # e.g. just conductor-codex-pilot-dry docs --project af
226
+ conductor-codex-pilot-dry team="full" *args:
227
+ {{node_ts}} scripts/team-up.ts --team {{team}} --conductor codex --dry-run {{args}}
141
228
 
142
229
  # Snapshot a RUNNING team's session refs to ~/.pi/team-snapshots/<team>.json
143
230
  # (team keeps running — take one proactively so a crash is resumable).
144
231
  # A team launched with --project must snapshot with the same --project.
145
232
  # e.g. just team-snapshot review --project af
146
233
  team-snapshot team="full" *args:
147
- node --experimental-strip-types scripts/team-snapshot.ts snapshot {{team}} {{args}}
234
+ {{node_ts}} scripts/team-snapshot.ts snapshot {{team}} {{args}}
148
235
 
149
236
  # Snapshot, then close the team workspace cleanly (peers get SIGTERM).
150
237
  # e.g. just team-down review --project af
151
238
  team-down team="full" *args:
152
- node --experimental-strip-types scripts/team-snapshot.ts down {{team}} {{args}}
239
+ {{node_ts}} scripts/team-snapshot.ts down {{team}} {{args}}
153
240
 
154
241
  # Rebuild a team from its snapshot — each pi peer resumes its previous
155
242
  # conversation (`pi --session <ref>`); peers whose ref is gone start fresh.
156
243
  # e.g. just team-resume review --project af
157
244
  team-resume team="full" *args:
158
- node --experimental-strip-types scripts/team-snapshot.ts resume {{team}} {{args}}
245
+ {{node_ts}} scripts/team-snapshot.ts resume {{team}} {{args}}
159
246
 
160
247
  # ---------------------------------------------------------------- coms (Pi-to-Pi messaging)
161
248
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@chankov/agent-fleet",
3
- "version": "0.0.2",
3
+ "version": "0.0.3",
4
4
  "description": "Multi-agent fleet orchestration for coding agents. Pi as the primary runtime, Herdr as the workspace control plane, coms as the peer data plane, and Hermes for remote control — plus skills, personas, harnesses, and a guided setup CLI.",
5
5
  "keywords": [
6
6
  "ai",
@@ -59,11 +59,17 @@
59
59
  ".pi/damage-control-rules.yaml",
60
60
  "scripts/*.ts",
61
61
  "scripts/lib/*.ts",
62
+ "codex/",
63
+ "hermes/",
64
+ "systemd/",
62
65
  "justfile",
63
66
  "references/",
64
67
  "hooks/",
65
68
  "docs/agent-fleet-setup.md",
69
+ "docs/ARCHITECTURE.md",
70
+ "docs/codex-remote-conductor.md",
66
71
  "docs/claude-code-coms-bridge.md",
72
+ "docs/coms-hermes-bridge.md",
67
73
  "docs/pi-extensions.md",
68
74
  "docs/npm-install.md",
69
75
  "docs/skill-anatomy.md",
@@ -88,7 +94,7 @@
88
94
  "access": "public"
89
95
  },
90
96
  "scripts": {
91
- "test": "node bin/cli.js --version && node bin/cli.js --help && node bin/cli.js transform-persona --list --agent claude-code && node --test \"bin/test/*.test.js\" \".pi/harnesses/lib/herdr-client.test.ts\" \".pi/harnesses/lib/herdr-presence.test.ts\" \"scripts/lib/team-project.test.ts\" \"scripts/lib/herdr-layout.test.ts\" \"scripts/lib/spawn-stagger.test.ts\" \"scripts/lib/fleet-extras.test.ts\" \"scripts/lib/team-snapshot.test.ts\" \"scripts/lib/coms-envelope.test.ts\" \"scripts/lib/claude-bridge-core.test.ts\" \"scripts/lib/hermes-bridge-core.test.ts\" \"scripts/coms-hermes-bridge.test.ts\" \".pi/harnesses/ask-user-remote/race-core.test.js\" \".pi/harnesses/ask-user-remote/index.test.ts\" \".pi/extensions/btw/state.test.js\" \".pi/harnesses/agent-hub/return-contract.test.js\" \".pi/harnesses/agent-hub/backend-policy.test.js\" \".pi/harnesses/agent-hub/artifacts.test.js\" \".pi/harnesses/agent-hub/scope-gate.test.js\" \".pi/harnesses/agent-hub/evidence-rules.test.js\" \".pi/harnesses/damage-control/shared.test.js\" \".pi/harnesses/damage-control/herdr-rules.test.js\" \".pi/harnesses/damage-control-continue/exemptions.test.js\"",
97
+ "test": "node bin/cli.js --version && node bin/cli.js --help && node bin/cli.js transform-persona --list --agent claude-code && node --test \"bin/test/*.test.js\" \".pi/harnesses/lib/herdr-client.test.ts\" \".pi/harnesses/lib/herdr-presence.test.ts\" \"scripts/coms-cli.test.ts\" \"scripts/lib/codex-conductor.test.ts\" \"scripts/lib/codex-remote-control.test.ts\" \"scripts/lib/team-project.test.ts\" \"scripts/lib/herdr-layout.test.ts\" \"scripts/lib/spawn-stagger.test.ts\" \"scripts/lib/fleet-extras.test.ts\" \"scripts/lib/team-snapshot.test.ts\" \"scripts/lib/coms-envelope.test.ts\" \"scripts/lib/claude-bridge-core.test.ts\" \"scripts/lib/hermes-bridge-core.test.ts\" \"scripts/coms-hermes-bridge.test.ts\" \".pi/harnesses/ask-user-remote/race-core.test.js\" \".pi/harnesses/ask-user-remote/index.test.ts\" \".pi/extensions/btw/state.test.js\" \".pi/harnesses/agent-hub/return-contract.test.js\" \".pi/harnesses/agent-hub/backend-policy.test.js\" \".pi/harnesses/agent-hub/artifacts.test.js\" \".pi/harnesses/agent-hub/scope-gate.test.js\" \".pi/harnesses/agent-hub/evidence-rules.test.js\" \".pi/harnesses/agent-hub/research-retention.test.js\" \".pi/harnesses/damage-control/shared.test.js\" \".pi/harnesses/damage-control/herdr-rules.test.js\" \".pi/harnesses/damage-control-continue/exemptions.test.js\"",
92
98
  "pack:dry": "npm pack --dry-run",
93
99
  "changeset": "changeset",
94
100
  "version:changeset": "node bin/force-patch-changesets.js && changeset version && npm install --package-lock-only --ignore-scripts --no-audit --no-fund && node bin/snapshot-version.js",
@@ -116,6 +122,7 @@
116
122
  ],
117
123
  "extensions": [
118
124
  "./.pi/harnesses/ask-user-remote/index.ts"
119
- ]
125
+ ],
126
+ "image": "https://raw.githubusercontent.com/chankov/agent-fleet/main/docs/assets/agent-hub-dashboard.png"
120
127
  }
121
128
  }