Multi-Agent Coding
Run Claude Code, Codex, Grok CLI, and shell jobs in parallel panes. Use imux as a multi-agent coding command center with Git and browser verification.
Why imux?
imux is built for concurrent agent processes with operator chrome—not a single chat column only.
Key Features
- Split panes for parallel agent CLIs
- Agent Chat for membership models alongside local CLIs
- Git sidebar evidence while agents run
- Browser surface for UI verification
- Isolation / worktree-friendly long jobs
Getting Started
Open the project workspace
Create or select a workspace rooted at your repo. Keep one shell pane for git/status and others for agents.
Start the first agent CLI
Launch Claude Code, Codex, or Grok CLI in a dedicated pane. Prefer project cwd so resume commands stay tied to the repo.
Add a second agent or verifier
Split another pane for tests, logs, or a second agent with a different charter. Avoid two agents writing the same files blindly.
Review diffs and verify
Use Git sidebar + browser pane for evidence. Apply only reviewed patches. See tutorials for multi-agent layout and diff workflow.
FAQ
Is multi-agent safer than one chat window?
It is clearer when each process has its own pane and charter, but you still need review. Parallel agents can conflict on the same files.
Does imux replace Claude Code or Cursor?
No. imux hosts and supervises agents. Keep Claude Code / Cursor when you need their editor or CLI product strengths.
How do I recover a black terminal while agents run?
imux 5.0.34+ auto-reattaches portals and offers Doctor recovery. Your files and processes may still be alive—recover the surface first.