Cross-Machine Coordination Pattern

Coordinate distributed squad work across multiple machines by using Git-based task queues within .squad directories. Agents on different machines securely share work, execute tasks, and pass results without manual intervention by committing pending task files to the main branch.

Yes, GitHub Issues can supplement Git-based task queuing to handle urgent tasks across machines. The coordination pattern uses .squad directories for standard task files while integrating GitHub Issues to prioritize and track time-sensitive distributed squad work.

Cross-machine coordination for GPU workloads works by connecting laptop, DevBox, and cloud VM environments through a shared Git repository. It automatically executes queued tasks, propagates results, and maintains audit trails across the distributed machines for data processing.

Git-based task execution relies on committing to a shared repository, which requires network connectivity and manual or automated pushes to trigger work. It is not designed for real-time streaming or sub-second latency coordination, but rather for asynchronous, long-running tasks with audit logs.

Yes, cross-machine task automation requires schema validation, command whitelisting, resource limits, execution isolation, and immutable audit logs. These safety checks are enforced via a defined file and issue workflow to ensure secure coordination across distributed machines.

Start automating squad tasks by creating a task file under the .squad/cross-machine/tasks directory with a pending status. Push the file to the main branch to initiate the coordination workflow and automatically distribute work to available machines.