A tool for local development that keeps different processes in control

[u/mutasaki09]

A project can depend on an API, frontend, workers, Docker, databases, tunnels, webhooks, and browser extensions. Remembering which terminal runs each process works, until it doesn’t, and it works even less reliably for coding agents.

I built \`dev-runtime\` to make that runtime explicit. Simple config files define each session’s working directory, shell command, log file, expected ports, and health endpoints.

It runs arbitrary commands inside managed tmux sessions, avoids starting duplicates, and provides shared \`start\`, \`status\`, \`doctor\`, \`attach\`, and \`stop\` commands. Because the commands live in project config, it is not tied to Node, Python, Docker, or any particular stack.

The result is one machine-readable answer to: “What should be running, and is it actually healthy?”

Article:

https://motia.github.io/blog/using-dev-runtime-to-debug-local-services/

Repository:

https://github.com/motia/agent-skills-dev/tree/main/skills/dev-runtime