The best terminal for Claude Code and Codex — built for parallel agents.

1. 01

   A second agent starts on a copy that already runs

   Duplicate copies the whole project folder, so the new copy arrives with node_modules, .venv, .env files, and your uncommitted work already in place — no reinstall, no re-configuring, no "it works on my other checkout". If you want the copy on its own branch instead, the same dialog creates a Git worktree — a real checkout of your current commit, so it starts clean: uncommitted changes and ignored files like node_modules and .env stay behind in the original.

2. 02

   One prompt, up to 50 answers to choose from

   Set a copy count in the Duplicate dialog — anywhere from 1 to 50 — and queue the same prompt in every copy at once. Claude Code, Codex, and Gemini CLI each attack the task in their own checkout, and you keep the version you like instead of rerolling the same session and hoping.

3. 03

   You find out an agent is waiting without checking on it

   Each session carries its own status in the sidebar, so a terminal that has finished or is blocked on a question announces itself. You go back to the one agent that needs you instead of cycling through five to see who stopped.

4. 04

   You see how much of your plan the agents have burned

   Claude and Codex each get a usage line in the sidebar: how much of the window is gone and when it comes back, for whichever window you pick — weekly out of the box, or the 5-hour one. Hover the line and both windows open together. When several agents run all afternoon, you know how much room is left before a limit lands mid-refactor.

Or compare lpm to cmux directly →

• Does lpm work with Claude Code and Codex out of the box?

  Yes. You point lpm at your project, hit Start in the app, and watch each service stream live output in its own pane. The agent talks to the services the app started.
• Can I run multiple agents in parallel on the same repo?

  Yes — each agent works in its own copy of the repo, so they never edit the same files. Duplicate copies the project folder (dependencies, .env files, and uncommitted work included) and Worktree checks out a real Git worktree on its own branch; either way you can create up to 50 copies at once and queue the same prompt in every one. Every copy appears in the sidebar with its own services and terminals, so Claude Code in one and Codex in another sit side by side with all their output visible. The worktree guide covers which of the two to reach for.
• Do I need Docker to use lpm?

  No. lpm runs anything that runs in a terminal. Docker Compose stacks work, and plain Rails, Next.js, Go, Django, or Flask projects work without containers.
• Is lpm open source?

  Yes. The source, issue tracker, and releases live on GitHub. Contributions and bug reports are welcome.
• Which frameworks does lpm work with?

  Rails, Next.js, Go, Django, Flask, Docker Compose, and anything else that runs in a terminal. lpm can generate the service config for you with AI when you add a project.