Files
stack/packages/mosaic/framework/fleet
Jason Woltje 3d8bd3be1e
All checks were successful
ci/woodpecker/push/ci Pipeline was successful
ci/woodpecker/pr/ci Pipeline was successful
fix(fleet): remove duplicate workingDirectory key in roster.schema.json
Edit artifact from the host/ssh addition left a third workingDirectory block in
the agent-items properties (duplicate JSON keys are last-wins, so prettier/CI did
not flag it). Keep exactly one workingDirectory + one working_directory.

Refs #620

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EsgTQzV5YUGk1JtCLP4B83
2026-06-22 12:06:31 -05:00
..

Mosaic Fleet Rosters

The local fleet canary uses a product-owned roster schema with site-owned roster files. Product examples live here; active local rosters should live outside the package, normally at:

~/.config/mosaic/fleet/roster.yaml

The default tmux socket is mosaic-factory so fleet commands do not touch the default tmux server.

Examples

  • examples/minimal.yaml starts one local canary slot.
  • examples/local-canary.yaml starts a small generic dogfood fleet.

Initialize a roster:

mosaic fleet init --profile minimal --write
mosaic fleet install-systemd
mosaic fleet start
mosaic fleet verify