runit
s6
systemd
sysvinit
Dinit
Upstart
Supervisor
M/Monit
Command Book
Warp Terminal
iTerm
Kitty terminal
Ghostty
tmux
Foreman
PM2
Command Book is a native macOS app built with SwiftUI that gives your long-running terminal commands a permanent home. Instead of juggling terminal tabs for dev servers, background workers, Docker containers, and log tails every morning, Command Book lets you save each command once with its working directory, environment variables, and pre-commands, then run them instantly whenever you need them.
The app includes auto-restart on crash (nicknamed "Honey Badger mode") to keep dev servers running through file change errors, a โK command palette for keyboard-first workflows, automatic URL detection that keeps your dev server addresses accessible regardless of output scrolling, and a full CLI for running saved commands directly from the terminal. At 21 MB with no Electron or Chromium, it stays lightweight and fast.
Free personal license available. Pro edition is a one-time $14.99 purchase with no subscription, no account required, and no tracking. No VC, no enterprise upsell. Feedback welcome. Windows version is under consideration.
runit Command BookCommand Book's answer:
Swift and SwiftUI for a fully native macOS experience.
Command Book's answer:
Command Book is a dedicated command/process manager for developers, not a terminal emulator. Instead of replacing your terminal, it works alongside it as a companion for long-running commands. It's a native macOS app built with SwiftUI at just 21 MB. No Electron, no Chromium. It combines a GUI with a full CLI, so you can manage commands visually or from your terminal.
Command Book's answer:
Terminal emulators are great for interactive work but terrible as process managers. Command Book fills that gap. You save a command once with its working directory, env vars, and pre-commands, then run it forever without remembering the setup. Auto-restart keeps crashed dev servers running. URL detection means you never lose track of your dev server's address. And at 21 MB with no subscription or tracking, it's lightweight in every sense.
Command Book's answer:
Developers who juggle multiple long-running processes every day. Web developers running dev servers and background workers, data scientists kicking off training runs, DevOps engineers managing Docker containers and log tails. Anyone who opens 4-6 terminal tabs each morning just to get their environment running.
Command Book's answer:
After years juggling commands for dev projects, I was tired of rebuilding my terminal setup every morning. Five or six tabs, each needing the right directory and env vars, and when something crashed mid-day I'd hunt through tabs to find it. I looked for a tool that managed long-running commands as saved, reproducible, auto-restarting processes. It didn't exist, so I built it for myself. It was such a delight, I turned it into a product.
Based on our record, runit seems to be more popular. It has been mentiond 11 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
If all you need is init (and not a process supervisor), docker comes with one called 'tini' built in. All you have to do is supply `--init` to the `docker run` command. As far as a different process supervisor, I'm not sure. I've used supervisord and agree it's kind of awkward. I have heard of these but don't know much about them: https://smarden.org/runit/ https://github.com/nicolas-van/multirun... - Source: Hacker News / 11 months ago
We've all done it. (-: For some while I read people saying that, despite the existence of Paul Jarc showing how svscan as process 1 would actually work and Gerrit Pape leading the way with runit-init and demonstrating the basic idea, one could not do full system management with daemontools and wholly eliminate van Smoorenberg init and rc. * https://code.dogmap.org/svscan-1/ * https://smarden.org/runit/ It was one... - Source: Hacker News / 12 months ago
Not so much about timeouts, but related in that it is based around managing children processes: The lineage of tools descending from daemontools for service management is worth exploring: daemontools: http://cr.yp.to/daemontools.html runit: https://smarden.org/runit/ s6: https://skarnet.org/software/s6/ dinit: https://davmac.org/projects/dinit/. - Source: Hacker News / over 1 year ago
I personally am a fan of runit https://smarden.org/runit/ But s6 is excellent as well. - Source: Hacker News / almost 2 years ago
How does it compare to Runit[[0] used by Void Linux? [0]http://smarden.org/runit/. - Source: Hacker News / about 3 years ago
s6 - s6 is a small suite of programs for UNIX, designed for process supervision. It can be used as an init system, or as separate supervision components.
Warp Terminal - The terminal for the 21st century. Warp is a blazingly fast, rust-based terminal reimagined from the ground up to work like a modern app.
systemd - systemd is a replacement for the init daemon for Linux (either System V or BSD-style).
iTerm - iTerm is a full featured terminal emulation program written for OS X using Cocoa.
sysvinit - Savannah is a central point for development, distribution and maintenance of free software, both GNU and non-GNU.
Kitty terminal - Super fast, GPU and OpenGL based terminal emulator with tiling support
