mosaicstack/stack
1
0
Fork 0
Code Issues 31 Pull Requests 2 Actions Packages Projects Releases 15 Wiki Activity

Onboarding/comms injection MUST cover ALL agent launch paths (orchestrator + raw claude --channels), not just mosaic yolo spawns #633

New Issue
Closed
opened 2026-06-22 20:51:34 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-06-22 20:51:34 +00:00
Owner
Copy Link

HARD REQUIREMENT (Jason 2026-06-22): every agent session MUST boot knowing its inter-agent comms tooling + available tools. The user must NEVER have to remind an agent which tools to use.

GAP: #621 injects the # Fleet Comms cheat-sheet via composeContract, which only runs in the mosaic yolo <runtime> spawn path. The ORCHESTRATOR launches via raw claude --channels ... (orchestrator-launch.sh / mosaic-fleet-orchestrator.service), which BYPASSES composeContract -> it boots WITHOUT the cheat-sheet. Any Claude Code fleet session has the same gap.

FIX:

  1. Expose the comms block as a standalone command, e.g. mosaic fleet comms-block <role> emitting readFleetCommsBlock for that roster agent (roster-driven, host-aware).
  2. The orchestrator / Claude-Code launcher passes it on launch: claude --channels ... --append-system-prompt "$(mosaic fleet comms-block <role>)" so the agent boots comms-aware with no manual reminder.
  3. Make it a hard onboarding requirement covering ALL launch paths (mosaic yolo spawns + raw claude --channels + any future runtime).

VERIFY: a freshly-launched orchestrator's context contains the Fleet Comms block with correct peer addresses (local -s, remote -H), with zero manual reminder.

This is enhancer-charter work (fleet onboarding/capability) once the enhancer is live; dragon implements for now. Generalizes #621 (#620).

HARD REQUIREMENT (Jason 2026-06-22): every agent session MUST boot knowing its inter-agent comms tooling + available tools. The user must NEVER have to remind an agent which tools to use. GAP: #621 injects the `# Fleet Comms` cheat-sheet via composeContract, which only runs in the `mosaic yolo <runtime>` spawn path. The ORCHESTRATOR launches via raw `claude --channels ...` (orchestrator-launch.sh / mosaic-fleet-orchestrator.service), which BYPASSES composeContract -> it boots WITHOUT the cheat-sheet. Any Claude Code fleet session has the same gap. FIX: 1. Expose the comms block as a standalone command, e.g. `mosaic fleet comms-block <role>` emitting readFleetCommsBlock for that roster agent (roster-driven, host-aware). 2. The orchestrator / Claude-Code launcher passes it on launch: `claude --channels ... --append-system-prompt "$(mosaic fleet comms-block <role>)"` so the agent boots comms-aware with no manual reminder. 3. Make it a hard onboarding requirement covering ALL launch paths (mosaic yolo spawns + raw claude --channels + any future runtime). VERIFY: a freshly-launched orchestrator's context contains the Fleet Comms block with correct peer addresses (local -s, remote -H), with zero manual reminder. This is enhancer-charter work (fleet onboarding/capability) once the enhancer is live; dragon implements for now. Generalizes #621 (#620).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#633
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?