twl:co-autopilot

Cross-issue workflow orchestration is automated by coordinating Pilot sessions, tmux windows, phase transitions, and merge-gate control across multiple issues. You provide a dependency graph and project directory to start the automated orchestration.

Dependency-driven autopilot is an autonomous implementation mechanism for complex Issue clusters. It sequences phase transitions and manages merge-gates across multiple repositories by coordinating worker ecosystem sessions based on dependency relationships.

Yes, tmux windows are managed directly by the autopilot to coordinate Pilot sessions across multiple repos. The orchestration controls phase sequencing and cross-repo interactions within these terminal sessions.

Setting up autopilot mode requires a project directory, a clear dependency graph of the issue cluster, and configuration that enables plan generation. Once provided, the system coordinates phase management and worker ecosystem integration automatically.

Yes, cross-issue orchestration supports Autopilot-first execution even for single issues within the orchestration. The same phase sequencing and merge-gate control applies to individual issues managed inside the workflow.

Automating merge-gate control requires a clear dependency graph and proper project directory configuration to function. Without accurate dependency mappings for the issue clusters, the autopilot cannot reliably sequence phase transitions or coordinate worker sessions.