Does lpm work with monorepos?

Yes. lpm is designed around multi-service projects. Open a monorepo folder and lpm reads your service definitions from a Procfile, docker-compose.yml, package.json workspaces config, or any combination. Each service gets its own pane and start/stop controls. You can start the entire monorepo in one click or bring up individual services independently.

Can I use lpm alongside VS Code or another editor?

Yes. lpm is a terminal workspace, not an editor replacement. You write code in VS Code, Cursor, Zed, or whatever editor you prefer, and use lpm to run your dev stack, watch logs, and manage git — all in a native Mac window that sits alongside your editor.

Does lpm support SSH or remote development?

lpm runs your local development stack natively on your Mac. It does not currently proxy SSH sessions or manage remote machines. If you need remote terminal sessions, you can open a plain shell pane in lpm and SSH from there, but the service management and log pane features apply to local processes only.

How does lpm help when running multiple AI coding agents?

Each AI coding agent can be assigned its own lpm project workspace. That isolation means agents can run dev servers, execute tests, and write to log panes without conflicting with your running environment or with each other. You can watch every agent's output in real time, in separate labeled panes, from one Mac window.

Can I use my existing shell setup (zsh, dotfiles, aliases) in lpm?

Yes. lpm panes are real terminal sessions running your default shell — zsh, bash, or fish — with your full dotfile configuration loaded. Every alias, function, $PATH entry, and prompt theme works exactly as it does in Terminal.app or iTerm2.

How is lpm different from using tmux inside iTerm2?

tmux gives you pane multiplexing but no project awareness, no service lifecycle management, and no GUI for starting or stopping processes. lpm layers a visual project switcher, per-service start/stop controls, and a config editor on top of real terminal panes — so you get the workflow benefits of tmux without the config overhead, and with a native Mac interface that new team members can use on day one.

Terminal built for your developer workflow

The Mac terminal workspace built for developers
who run real stacks.

lpm replaces scattered terminal tabs with a project-aware workspace — one window for every service, per-service log panes, and instant project switching that keeps your state intact. Native Apple Silicon, zero Electron.

Download for macOS

Signed & notarized by Apple

View on GitHub

Live interactive demo

Projects, terminals, Claude Code or Codex — one click each

Click anywhere below. Switch projects, start services, launch Claude Code or Codex — all running live in your browser, right now.

Loading demo…

The daily friction

Your terminal was built for commands, not for building software

Running a modern stack on a Mac means managing half a dozen processes in half a dozen windows. That's not a workflow — it's damage control.

Monorepo service sprawl

Your monorepo has an API, a worker, a frontend, a database, and a cron job. Every morning you open five tabs, cd into each one, run the right command, and hope nothing crashed while you were in standup. There has to be a better way.

Context evaporates when you switch repos

You're three services deep in a debugging session when Slack pings with a blocking issue on a different client project. You switch repos and your running services, terminal history, and mental state all disappear. Getting back is a 15-minute tax every time.

Logs drown in one shared scroll buffer

When five services write to the same terminal, you debug by grepping a firehose. Was that error from the API or the worker? Which service restarted? You shouldn't need to be a log archaeologist to run your own stack.

Built for the way developers actually work

A terminal workspace that understands your stack

Six capabilities that change how you develop on a Mac — not just how you type commands.

Per-project workspaces, not tabs

Each project lives in its own persistent workspace with its own services, logs, and terminal sessions. Switch repos in the sidebar without touching what's running anywhere else.

Per-service log panes

Every service gets its own scrollable log pane. Watch your API, your worker, and your Next.js dev server simultaneously — each one labeled, each one isolated, so you know in two seconds which service threw the error.

One-click full-stack start

Define your services once. After that, one click starts your entire stack in the right order. lpm auto-detects Rails, Next.js, Go, Django, Flask, and Docker Compose configurations the first time you open a project folder.

Git and services coexist in the same window

Run git rebase, git bisect, or a full migration in a shell pane while your dev servers keep streaming in adjacent panes — all inside one native Mac window, no window-manager juggling required.

Run multiple AI agents without conflicts

Assign each AI coding agent its own workspace so agents working on the same codebase don't clobber each other's running servers or terminal state. Purpose-built for multi-agent development flows.

Native Apple Silicon, zero Electron

A proper macOS app — no Chromium runtime, no Node.js renderer process. Your M-series chip runs your stack, not a web browser dressed up as a terminal.

The developer difference

What changes when your terminal knows your stack

Four measurable improvements to your development day.

Onboard a new repo in under two minutes.
Open any project folder, let lpm auto-detect its services, review the generated config, hit Start. Every service streams live output immediately — no README archaeology, no `which python`, no "wait, what port does this run on?".
Debug across services without losing the thread.
When something breaks, you're watching all five services at once. The error is visible, labeled, and in context — not buried in a shared scroll buffer you have to grep through.
Switch between projects without a mental-state reset.
Jump to another repo mid-session. Your first project keeps running, logs intact, terminal history preserved. Switch back and pick up exactly where you left off.
Coordinate AI agents without stepping on your own work.
Each AI coding agent gets its own workspace. Agents can run servers, make changes, and run tests without colliding with your running dev stack or each other.

In practice

Three developer workflows your Mac terminal should make effortless

Real scenarios that take 30+ minutes with scattered tabs and under 5 with a proper dev workspace.

Spin up an unfamiliar repo your first morning on a project

Clone the repo, open it in lpm. The auto-detection pass reads your package.json, Procfile, docker-compose.yml, or manage.py and proposes a service config. Review it, tweak the ports, hit Start. Every service streams live side by side — no README guessing, no missing env vars surfaced at runtime.

Run your full stack while debugging a specific service

Open a shell pane next to your service panes. Set a breakpoint or add debug logging, restart just that one service from its pane controls, and watch its isolated log while the rest of the stack stays up. No need to tear down and rebuild the whole environment to test one change.

Juggle three client projects in the same afternoon

Each client project has its own sidebar entry. Pause project A, open project B, make changes, context-switch to project C for a quick hotfix. All three keep their running state, their service logs, and their terminal history. No re-cloning, no nvm use, no “which version of Node does this one need?” — lpm handles it per-project.

How it compares

lpm vs iTerm2, Terminal.app, tmux, Warp, and VS Code terminal

A capability matrix for Mac developers choosing between the tools already on their machine.

Capability	lpm	iTerm2	Terminal.app	tmux	Warp	VS Code terminal
Native Apple Silicon app (no Electron)
Per-project persistent workspace with live state
Start your full dev stack in one command
Isolated per-service log pane
Auto-detects Rails, Next.js, Go, Django, Flask, Docker Compose
Run multiple AI agents on the same codebase without conflicts
Switch between projects without restarting services
Built-in config editor for your project's services
Free and open source

lpm

Native Apple Silicon app (no Electron)
Per-project persistent workspace with live state
Start your full dev stack in one command
Isolated per-service log pane
Auto-detects Rails, Next.js, Go, Django, Flask, Docker Compose
Run multiple AI agents on the same codebase without conflicts
Switch between projects without restarting services
Built-in config editor for your project's services
Free and open source

iTerm2

Native Apple Silicon app (no Electron)
Per-project persistent workspace with live state
Start your full dev stack in one command
Isolated per-service log pane
Auto-detects Rails, Next.js, Go, Django, Flask, Docker Compose
Run multiple AI agents on the same codebase without conflicts
Switch between projects without restarting services
Built-in config editor for your project's services
Free and open source

Terminal.app

Native Apple Silicon app (no Electron)
Per-project persistent workspace with live state
Start your full dev stack in one command
Isolated per-service log pane
Auto-detects Rails, Next.js, Go, Django, Flask, Docker Compose
Run multiple AI agents on the same codebase without conflicts
Switch between projects without restarting services
Built-in config editor for your project's services
Free and open source

tmux

Native Apple Silicon app (no Electron)
Per-project persistent workspace with live state
Start your full dev stack in one command
Isolated per-service log pane
Auto-detects Rails, Next.js, Go, Django, Flask, Docker Compose
Run multiple AI agents on the same codebase without conflicts
Switch between projects without restarting services
Built-in config editor for your project's services
Free and open source

Warp

Native Apple Silicon app (no Electron)
Per-project persistent workspace with live state
Start your full dev stack in one command
Isolated per-service log pane
Auto-detects Rails, Next.js, Go, Django, Flask, Docker Compose
Run multiple AI agents on the same codebase without conflicts
Switch between projects without restarting services
Built-in config editor for your project's services
Free and open source

VS Code terminal

Native Apple Silicon app (no Electron)
Per-project persistent workspace with live state
Start your full dev stack in one command
Isolated per-service log pane
Auto-detects Rails, Next.js, Go, Django, Flask, Docker Compose
Run multiple AI agents on the same codebase without conflicts
Switch between projects without restarting services
Built-in config editor for your project's services
Free and open source

FAQ

What developers ask before switching their Mac terminal

Does lpm work with monorepos?
Yes. lpm is designed around multi-service projects. Open a monorepo folder and lpm reads your service definitions from a Procfile, docker-compose.yml, package.json workspaces config, or any combination. Each service gets its own pane and start/stop controls. You can start the entire monorepo in one click or bring up individual services independently.
Can I use lpm alongside VS Code or another editor?
Yes. lpm is a terminal workspace, not an editor replacement. You write code in VS Code, Cursor, Zed, or whatever editor you prefer, and use lpm to run your dev stack, watch logs, and manage git — all in a native Mac window that sits alongside your editor.
Does lpm support SSH or remote development?
lpm runs your local development stack natively on your Mac. It does not currently proxy SSH sessions or manage remote machines. If you need remote terminal sessions, you can open a plain shell pane in lpm and SSH from there, but the service management and log pane features apply to local processes only.
How does lpm help when running multiple AI coding agents?
Each AI coding agent can be assigned its own lpm project workspace. That isolation means agents can run dev servers, execute tests, and write to log panes without conflicting with your running environment or with each other. You can watch every agent's output in real time, in separate labeled panes, from one Mac window.
Can I use my existing shell setup (zsh, dotfiles, aliases) in lpm?
Yes. lpm panes are real terminal sessions running your default shell — zsh, bash, or fish — with your full dotfile configuration loaded. Every alias, function, $PATH entry, and prompt theme works exactly as it does in Terminal.app or iTerm2.
How is lpm different from using tmux inside iTerm2?
tmux gives you pane multiplexing but no project awareness, no service lifecycle management, and no GUI for starting or stopping processes. lpm layers a visual project switcher, per-service start/stop controls, and a config editor on top of real terminal panes — so you get the workflow benefits of tmux without the config overhead, and with a native Mac interface that new team members can use on day one.

Your Mac terminal, built for development.
Free, native, and ready in two minutes.

Download a native macOS binary, drag to Applications, open your first project. lpm auto-detects your stack and has you running in under two minutes. Works on every Intel and Apple Silicon Mac running macOS 12 or later.