Automus

The problem

Working across several projects means a start command per project — php artisan serve here, npm run dev there, a GeoServer startup.sh somewhere else — each in its own terminal tab, in its own folder, retyped after every login. Servers that were meant to stop keep holding their ports, because stopping the shell does not stop the process it forked.

The approach

Automus saves each project's root folder and start command once. From then on a project is one button: its default command runs in a fixed slot, so pressing it again restarts that run instead of starting a duplicate, and any other command can be started beside it as an independent run. Every run gets its own tab with live, color-coded output. On macOS and Linux each run starts in its own session under your login shell, so your PATH is intact and Stop signals the whole process group.

What it does

One fixed slot per project

A project's default command reuses its slot, so a second click restarts the run rather than leaving two servers fighting over one port.

Concurrent one-off runs

Queue workers, watchers and migrations start with + as independent runs in the project's folder, each with its own tab and its own Stop button.

Color-coded live logs

URLs, HTTP methods, status codes, warnings and errors are highlighted as they stream, so a failing request stands out in a busy log.

Run All and Stop All

Bring a whole stack up after login and down again before closing the lid. Both buttons disable themselves when there is nothing left to do.

Stop that actually stops

Runs are started in their own process group. Stop sends SIGTERM to the group and SIGKILL after a three-second grace period, so forked children do not survive as orphans.

Local by construction

Projects are stored as JSON in the OS app-data folder. There is no account, no telemetry and no network request of its own.

Pricing

The application source is private; installers are published as public GitHub releases.