cross-machine-coordination

To distribute tasks across machines, this skill uses a git-based task queuing system that targets specific agents by hostname and priority, ensuring secure and automated execution without manual workarounds. It commits task YAML files to a shared repository.

Yes, you can use git for agent orchestration by committing task definitions to a shared repository. Squad agents on different machines pull these queued tasks, execute them, and record results, enabling secure squad collaboration without external servers.

You target a specific machine by including a squad machine tag in your git commit message, such as [squad:machine-devbox]. The system reads this tag and routes the task execution to the matching hostname within your squad.

No external servers are needed for cross-machine execution. The only requirement is git, which acts as the underlying task queuing mechanism to securely distribute and track tasks between squad agents across different machines.

If a distributed task fails on the target machine, the system supports automated retries for failed tasks. It also includes command validation and result tracking to record the execution outcome and help manage squad collaboration errors.

Cross-machine task automation is suitable for computational workloads like GPU voice cloning. You can enqueue tasks from a laptop and distribute them to DevBoxes or Azure VMs, automating the creation and execution of these heavy tasks across your squad.