Hoprig

Docs

Where it runs

Providers, Auto modeDashboardFresh-computer setup
Linuxrun and testedrun and tested (tmux and built-in terminals), systemd servicerun in clean Ubuntu, Debian and Fedora
macOSrun and testedrun and tested (built-in terminals) before this version; what is new in it was not run there (see above); the launchd service is written, not yet installed for realchecked read-only; installs not yet run
Windowsnot ready: written, the tests do not pass on Windows yetnot readynot ready

Requires Node.js 22 or newer (Node 20 is past its end of life, and it aborts when a terminal is closed under it; hoprig says so in one sentence on an older Node.js). The tests run on Linux and macOS with Node 22, 24 and 26 on every change. On Windows they have been run and do not pass yet, so Windows is not supported. tmux is used from version 3.2 on; with an older one (or none) the built-in terminals are used. With npm 12 there is nothing to do yourself: setup builds the one module that needs a build (node-pty, the only install script Hoprig's package.json approves), and hoprig doctor names the cause when it did not build.

Runtime dependencies: ws, xterm.js, Monaco (VS Code's editor core), qrcode-terminal, and optionally node-pty for the built-in terminals. No framework and no build step.