Local command center for your projects
Run, commit, and ship every project from one board.
Local command center for your projects
Run, commit, and ship every project from one board.
Start and stop your apps locally, then commit and push the work. When a project is ready to go out, LocalHelm can also bump its version, publish packages to npm, update the projects that depend on them, and deploy sites. Work across many repos at once. Every write shows its plan first and runs after you confirm, on the computer hosting your projects.
The operator board runs locally. The phone Deck is read-only. Dev-server controls require LocalSlip.

Running apps, uncommitted work, releases, and sites on one board. Inspect each plan before confirming a write.
The controls depend on where you open it:
- Operator board,
http://127.0.0.1:4321on the machine that runslocalhelm serve: every read and every write. - Deck,
/deckfrom a phone or any other device on your LAN or Tailscale: read-only. It shows one tile per running app that has a LocalSlip claim and listens beyond127.0.0.1. Tap a tile to open that app. Long-press to copy its link. No commit, publish, start, or stop.
LocalHelm refuses write requests unless they come from loopback, so a phone cannot run them even with the right URL.
Run the operator board
Install, stand in the folder that contains your repos, then run:
localhelm serve
On the board, click Add projects, scan the folder, tick the repos you keep, and confirm. Nothing enrolls on its own.
The CLI runs the same actions. scan, status, and deps only read. Other commands print a plan, and --apply writes. publish, push, ship, and global need named ids. Never --force.
Start and stop need LocalSlip. The Sites tab needs a FilePress site. Both are optional; without them those tabs stay empty.
LocalSlip is the slip. LocalHelm is the wheel.
Docs · Install · Why a wheel