wmux

# wmux — AI Agent Terminal for Windows

> **Run Claude Code + Codex + Gemini CLI side by side.**
> Split terminals, browser automation, MCP integration — the only proper way to use AI agents on Windows.

[![Windows 10/11](https://img.shields.io/badge/Windows-10%2F11-0078D6?logo=windows&logoColor=white)](https://github.com/openwong2kim/wmux/releases/latest)
[![Electron 41](https://img.shields.io/badge/Electron-41-47848F?logo=electron&logoColor=white)](https://www.electronjs.org/)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE)
[![GitHub stars](https://img.shields.io/github/stars/openwong2kim/wmux?style=social)](https://github.com/openwong2kim/wmux)

---

## Still using one terminal for your AI coding agents on Windows?

macOS has [cmux](https://github.com/manaflow-ai/cmux) — a tmux-based terminal multiplexer for AI agents.

**Windows has no tmux.** Without WSL, there was no way.

wmux fixes this. Native Windows terminal multiplexer + browser automation + MCP server. Your AI agent reads the terminal, controls the browser, and works autonomously.

```
Claude Code writes the backend on the left
Codex builds the frontend on the right
Gemini CLI runs tests at the bottom
— all on one screen, simultaneously.
```

---

## Install in 30 seconds

**Installer:**

[Download wmux Setup.exe](https://github.com/openwong2kim/wmux/releases/latest)

**One-liner (PowerShell):**
```powershell
irm https://raw.githubusercontent.com/openwong2kim/wmux/main/install.ps1 | iex
```

---

## Why wmux?

### 1. Your AI agent controls the browser — for real

Tell Claude Code "search Google for this" and it actually does it.

wmux's built-in browser connects via Chrome DevTools Protocol. Click, type, screenshot, execute JS — all done by the AI directly. Works perfectly with React controlled inputs and CJK text.

```
You: "Search for wmux on Google"
Gemini: browser_open → browser_snapshot → browser_fill(ref=13, "wmux") → browser_press_key("Enter")
→ Actually searches Go