localhelm
v0.1.50
Published
Local command center for your projects. Run dev servers, commit, and push from one board; for projects that go out, publish packages to npm, update dependents, and deploy sites.
Maintainers
Readme
LocalHelm
Local command center for your projects. Run, commit, and ship every project from one board.
Pick the repos you keep, including ones that only ever run on this machine. Start and stop their dev servers, see which have uncommitted work or unpushed commits, and commit and push from the same place. For projects that go out, LocalHelm also bumps versions, publishes packages to npm, updates the projects that depend on them, and deploys sites. Work across many repos in one batch. Every write opens a plan first and waits for you to confirm.
The controls depend on where you open it:
- Operator board at
http://127.0.0.1:4321, on the machine that runslocalhelm serve: every read and every write. - Deck at
/deck, from a phone or any other device on your LAN or Tailscale: read-only. One tile per running app that has a LocalSlip claim and listens beyond127.0.0.1. Tap to open, long-press to copy the link. No commit, publish, start, or stop. Write requests from anywhere but loopback get a 403.
Start and stop need LocalSlip. The Sites tab needs a FilePress site. Both are optional. LocalSlip is the slip. LocalHelm is the wheel.
pnpm add -g localhelm
# or from a checkout:
pnpm install && pnpm build
# From the folder that contains your repos:
localhelm serveOpen http://127.0.0.1:4321. Click Add projects, scan that folder (. is where you ran serve), tick the ones you keep, and confirm. Nothing auto-enrolls.
The same actions exist on the CLI if you want them. scan, status, and deps only read. Other commands print a plan; --apply writes. publish, push, ship, and global need named ids. Never --force.
For a new Cloudflare Pages site, dashboard Ship can offer Create Pages project with the account, project name, and production branch shown for confirmation. Creation is followed by a separate Ship plan. See Pages setup for supported scripts and recovery.
Publish builds and verifies an npm archive, then publishes those same bytes. Release targets explain generated packages, version and README sources, and recovery from a failed build.
localhelm scan .
localhelm enroll ./my-cli ./my-lib --apply
localhelm status
localhelm serve --free-port # stop the named pid on that port, then serveMenu Main / Demo (or localhelm serve --demo) is a sandbox fleet (localhelm.fleet.demo.json). Add and remove stay off the main file. Clear demo wipes only that sandbox. Commit, publish, push, and Land stay off.
localhelm serve opens the dashboard on port 4321. A global install runs the packaged board (SSR deps are bundled; no app/ needed). A checkout still uses Vite. Serve from the same tree as localhelm.fleet.json (or a child) or the board stays empty. If that port is already taken, serve names the pid and stops. Re-run with --free-port to stop it and bind. Never --force. Writes stay on loopback.
Skip folders with .localhelmignore at the workspace, or ~/.localhelm/ignore.
Commit-message drafts send repository text to Ollama on 127.0.0.1:11434 by default. For a remote host, explicitly set LOCALHELM_OLLAMA_MACHINE or LOCALHELM_OLLAMA_URL; LOCALHELM_OLLAMA_MODEL selects the model. The CLI and commit dialog name the destination. Drafting never scans the LAN or selects a cached remote host. Use ollanet scan --lan separately if you want discovery, then select the host. When Ollama is unavailable, the editable fallback message remains.
Requires Node 22+. License Apache-2.0. Site: localhelm.dev.
