Built for Windows + WSL
Keep WSL distros, PowerShell, Claude Code, and Codex visible in one workspace without tab juggling.
Run Claude Code, Codex CLI, and CJK/IME-heavy terminal work side by side without broken panes, drifting composition windows, or tab juggling.

Problem
WSL context, long-running AI agents, and CJK input methods all stress normal terminal UIs. Laymux is designed around those constraints from the start.
Keep WSL distros, PowerShell, Claude Code, and Codex visible in one workspace without tab juggling.
See when Claude Code or Codex is working, idle, or finished, with completion events surfaced in the dashboard.
A shadow cursor keeps Hangul, Japanese, and Chinese composition windows aligned during aggressive TUI redraws.
How it works
Create a workspace from a terminal-first pane layout.
Sync CWD, git branch, ports, and notifications across panes.
Expose terminals, output, screenshots, and pane control through local REST + MCP.
Automation
Local LLM tools can open panes, run commands, read terminal output, take screenshots, and post notifications through a local allowlisted interface.
curl http://localhost:19280/api/v1/workspaces
curl -X POST http://localhost:19280/api/v1/terminals/{id}/write \
-H "Content-Type: application/json" \
-d '{"input":"npm test\n"}'
// Claude / Codex MCP
http://localhost:19280/mcpWatch releases, inspect the roadmap, or open issues while the first public distribution path is finalized.
FAQ
Developers who live in Windows + WSL and use terminal AI agents such as Claude Code or Codex CLI as part of daily coding.
No. It is a Tauri desktop IDE with terminal panes, docks, workspace state, notifications, an lx CLI, REST automation, and MCP integration.
TUI apps often repaint aggressively, which can make CJK candidate windows drift or flicker. Laymux treats IME positioning as a core workflow.
Yes. A local REST API and Streamable-HTTP MCP server expose tools for panes, terminals, screenshots, output search, and notifications.