DocsOverview
lpm docs
New here? Install lpm and add a project folder. Then ask your AI agent to set it up for you, or edit the config yourself: every key is in the reference.
RecommendedAsk your AI agentTell Claude Code, Codex, Gemini CLI, or OpenCode what you want in plain words. It writes the change, and lpm checks it before the project updates.See how it worksEdit it yourselfEvery key with a live preview, copy-ready recipes, and the form and source editors built into the app.Open the reference
Or write the config yourself
Add or clone a folder and lpm fills in its dev servers. Change them here, add a profile or an action, and the preview updates as you type.
name: myapproot: ~/Projects/myapp# Long-running servicesservices: api: cmd: python manage.py runserver cwd: ./backend port: 8000 frontend: cmd: npm run dev cwd: ./frontend worker: celery -A backend worker# Named subsets of servicesprofiles: default: [api, frontend] full: [api, frontend, worker]# One-shot commands and terminalsactions: test: pytest migrate: cmd: python manage.py migrate cwd: ./backend confirm: true deploy: ./scripts/deploy.sh claude: cmd: claude label: Claude Code type: terminal~/.lpm/projects/myapp.yml
name: myapproot: ~/Projects/myapp# Long-running servicesservices: api: cmd: python manage.py runserver cwd: ./backend port: 8000 frontend: cmd: npm run dev cwd: ./frontend worker: celery -A backend worker# Named subsets of servicesprofiles: default: [api, frontend] full: [api, frontend, worker]# One-shot commands and terminalsactions: test: pytest migrate: cmd: python manage.py migrate cwd: ./backend confirm: true deploy: ./scripts/deploy.sh claude: cmd: claude label: Claude Code type: terminalServicesFound when you add a folder. Keep a one-line command, or set
cwd, port and env.ProfilesNamed sets of services. Pick one from the Start menu to boot just that set.ActionsOne-shot commands that show up as buttons — tests, migrations, deploys.TerminalsAn action with type: terminal opens a tab that stays open: Claude Code, Codex, a REPL or a log tail.Every page
Get started
- Install lpmDownload and install lpm on macOS, Windows or Linux, open your first project, and get past the warnings a beta build can show.
- Ask your agentConfigure lpm by asking Claude Code, Codex, Gemini CLI or OpenCode in plain words. The lpm skills teach the agent the config, and lpm checks every change.
- Editing in the appChange a project's config in lpm as a form, as YAML with schema hints, or let AI draft it from your code.
Configure
- ProjectThe lpm project file: the folder your code lives in, its name and Claude account, and SSH projects, with a live preview of the app.
- Service detectionHow lpm finds the dev servers in a folder you add: where it looks, what it recognizes, and how it names services and ports.
- ServicesLong-running processes lpm starts and stops together: commands, working folders, ports, env vars and dependsOn.
- ActionsOne-click buttons for tests, migrations and deploys: confirmations, split buttons, dropdowns, background actions and dynamic labels.
- TerminalsTerminal actions open a tab that stays open: Claude Code, Codex, a REPL or a log tail, one click away in the project toolbar.
- ZonesGroup a project's buttons into framed zones in the header or footer, with rows, positions and sliding layers.
- ProfilesNamed sets of services you pick from the Start menu, so you can boot just the frontend or the whole stack.
Share
- Config layersHow your project file, the repo's .lpm.yml and global config merge, so a team shares one setup while you keep your own tweaks.
- Global configActions and terminals in ~/.lpm/global.yml show up in every project: what a fresh install writes and what the file can hold.
- TemplatesReuse a set of actions and terminals across some of your projects with templates in ~/.lpm/templates and extends.
More
- RecipesComplete lpm configs to copy: a minimal blog, tests and linting, Next.js with a Node API, dev env vars, and a monorepo.
- Path resolutionHow lpm resolves root and cwd, ~ and relative folders, on local and SSH projects.
- ValidationWhat lpm config validate checks, and what the app refuses to save or start.
Keep reading
Let agents run your dev environment
The same Agent tools let Claude Code and Codex start services, read logs, and duplicate projects.
Scheduled automations
Run an agent or a command on a schedule — the jobs you may see in a config file.
Multiple Claude Code accounts
Pin a Claude login to each project — the claudeAccount key, set from the project form.
SSH projects
Run a remote machine's services, actions, and terminals from the same sidebar.
Git worktrees for AI agents
Give each agent its own copy of a project that inherits this config.
Your own Claude Code and Codex skills
Create and edit agent skills in lpm, with AI drafting the SKILL.md for you.
lpm writes your first config.
Your agent handles the rest.
Download lpm and add a project folder. It writes the config with the services it finds. Install Agent tools, and Claude Code or Codex changes it whenever you ask.