dsh-launch-pad

In local development, the most tedious part is rarely the code itself: every project has a different startup command (npm, docker, make, django, go, etc.), multiple services fight over ports, the agent can only guess and produce wrong instructions, and switching projects requires manual detection and registration again and again. dsh-launch-pad pulls all of this into a single global control deck so you and your agent share one reliable path.

Four pillars drive the design. First, command normalization: an ordered probe chain reads .dsh-services.yml, package.json, docker-compose.yml, Makefile, go.mod, and more to auto-detect the right start command. Second, a global registry with port arbitration: shared across all projects, it checks real port occupancy before launch and injects the correct port argument per framework on conflict. Third, dual-channel operation: the DSH Web UI offers one-click start, stop, and restart with expandable logs, while seven agent tools (service_list, detect, register, start, stop, restart, status) give the agent the same deterministic path. Fourth, session auto-follow: the panel reads the session you have selected in the UI, resolves it to a project directory, and auto-registers new projects without any manual input.

If you juggle multiple local projects, frequently start and stop services built on different frameworks, and want your agent to operate processes through explicit tools rather than guesswork, this plugin was built for your workflow. Currently supports macOS and Linux; Windows is on the roadmap.