task-orchestrator

You can orchestrate parallel Codex execution by defining a manifest of phases and tasks, which the orchestrator uses to spawn isolated git worktrees and tmux sessions for concurrent agent execution.

Self-healing heartbeat monitoring tracks active agents and automatically triggers error recovery procedures when it detects stalled tmux sessions or failed Codex executions during autonomous task processing.

Yes, per-task isolation requires git worktrees and tmux sessions to separate concurrent agent environments. The orchestrator automatically creates these isolated workspaces to prevent file conflicts during parallel execution.

Dependency-aware task planning analyzes task relationships and enforces phase gates, ensuring dependent tasks wait for prerequisite completion before executing. This prevents cascading failures and manages parallel execution order across large projects.

Yes, manifest-driven orchestration supports large software engineering projects by defining phases and tasks in a manifest file. The system then coordinates parallel work, automated code generation, testing, and passive progress auditing across the project.

Setting up the orchestrator requires git, tmux, gh, and Codex installed and configured in your environment. These tools provide the version control, terminal multiplexing, and code generation capabilities needed for autonomous workflow execution.