fleet-dispatch

Dispatch remote tasks to fleet nodes with per-task tracking.

2|Updated Apr 5, 2026

Search Tags:#monitoring #dispatch #orchestration #distributed #priority #task #fleet

Ready to run

npx skills add https://github.com/supportersimulator/multi-fleet --skill fleet-dispatch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fleet-dispatch
Source: https://github.com/supportersimulator/multi-fleet/tree/main/skills/fleet-dispatch
Command: npx skills add https://github.com/supportersimulator/multi-fleet --skill fleet-dispatch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatch remote tasks to fleet nodes and monitor outcomes with per-task tracking.

Core Features & Use Cases

Remote task dispatch to fleet nodes
Per-task tracking and status polling
Priority-driven routing and on-demand worker spawning for tasks
Use case: delegate tests or builds to specific machines and monitor results in real-time

Quick Start

Submit a dispatch request to POST /dispatch with a target and prompt to initiate a tracked task lifecycle.

Frequently Asked Questions about fleet-dispatch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I dispatch remote tasks to fleet nodes and monitor outcomes?▼

Remote task dispatch to fleet nodes is initiated by sending a POST request to the /dispatch endpoint with a target and prompt. This triggers a tracked task lifecycle with per-task status polling, worker spawning, and result reporting upon completion.

How does priority routing work for distributed task orchestration?▼

Priority routing for distributed task orchestration directs tasks to specific machines based on assigned priority levels. The system spawns on-demand workers for tasks and monitors results in real-time, ensuring delegated tests or builds execute according to routing priority.

Can I track the lifecycle of distributed workers across a machine fleet?▼

You can track the lifecycle of distributed workers across a machine fleet using per-task tracking and status polling. The session-driver integration spawns workers, monitors ongoing outcomes, and reports final results back to the coordinating node.

Does fleet dispatch work for delegating tests and builds to specific machines?▼

Fleet dispatch works for delegating tests and builds to specific machines by routing tasks to targeted fleet nodes. It supports priority-driven routing and on-demand worker spawning, allowing you to monitor delegated test or build results in real-time.

What is the best way to coordinate distributed workers without external dependencies?▼

The best way to coordinate distributed workers without external dependencies is using an HTTP API with session-driver integration. It spawns workers on demand, routes tasks by priority, and provides lifecycle polling to monitor outcomes across the fleet.

Why is my task dispatch not reporting results from remote fleet nodes?▼

Task dispatch may not report results if the targeted fleet nodes are unreachable or the session-driver fails to spawn workers. The system relies on lifecycle polling to track status, so network interruptions or unresponsive targets will halt per-task outcome reporting.