fleet-dispatch

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.

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.

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.

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.

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.

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.