Orchestrate Windows coding-agent fleets with Wmux
Use Wmux to fan out Claude Code, Codex, Gemini, and other agent CLIs across native Windows panes, isolated worktrees, approval gates, durable channels, and browser/MCP automation.
npx skills add agentskillexchange/skills --skill orchestrate-windows-coding-agent-fleets-with-wmux
Use Wmux when an operator needs to run and supervise multiple coding agents on native Windows without WSL. The agent/operator opens Wmux, creates split panes or workspaces for Claude Code, Codex, Gemini, OpenCode, or other detected agent CLIs, fans one prompt into isolated git worktree tasks, reviews diffs hunk by hunk, uses channels and A2A tools for coordination, and gates risky execution before it touches the workspace. Invoke it instead of ordinary terminal tabs, a single agent CLI, or a generic tmux setup when the job needs Windows-native multi-agent orchestration, reboot-surviving sessions, one-window fleet visibility, browser automation through MCP, and auditable worktree review. The scope boundary is operating Wmux as a Windows terminal and agent orchestration cockpit for coding-agent runs; it is not a generic Electron app, terminal emulator, tmux clone, or agent runtime replacement.\n\nInputs and prerequisites: Windows 10 or 11, Wmux, target git repository, one or more supported agent CLIs such as Claude Code, Codex, Gemini CLI, OpenCode, Aider, or GitHub Copilot CLI, optional gh or glab for pull request workflows, and optional browser/MCP tools.\n\nSetup notes: Install with winget install openwong2kim.wmux, choco install wmux, or the latest Setup.exe from GitHub releases. Start Wmux, open the target repository, launch agent CLIs in panes, use worktree task fan-out or split panes for parallel runs, and review/adopt diffs through the Git dock before merging or opening pull requests.\n\nSource and verification boundary: use https://github.com/openwong2kim/wmux as the canonical reference before running the workflow; keep commands, pane actions, worktree changes, browser actions, and generated diffs reviewable against that upstream source.\n\nFramework fit: publish this as a Multi-Framework workflow because upstream explicitly supports multiple agent CLIs and model/tool runtimes, while the concrete invocation remains Wmux-supervised Windows agent orchestration rather than a broad platform listing.