MrTerminal

One window for every terminal your projects need. Add a repository and every script it defines is one click away. Start the dev server, the tests and the webhook listener together, see at a glance what is running, and get it all back after a restart.

Why

Working on a real project usually means four or five long-running commands: a dev server, a test watcher, an API, a queue worker, a tunnel or webhook listener. Usually across more than one repository. In a plain terminal that turns into:

• Tab archaeology. A dozen tabs titled node or zsh, and the one you need is never the one you click.
• Retyping the same commands every morning. cd into each folder, recall whether it was pnpm dev or make run, and repeat after every reboot or crash.
• Not knowing what is actually running. Did the worker die? Is something still holding port 5173? Which project is that server from?
• Remembering every repo's commands. package.json, Makefile, pyproject.toml, compose.yaml: each project hides its commands somewhere different.

IDE terminals and multiplexers help with parts of this, but they either tie you to one editor or ask you to write and maintain a config file. MrTerminal reads the commands your projects already define and gives each one a button.

What it does

• Every script, one click away. MrTerminal reads package.json, Makefile, pyproject.toml, justfile, Procfile, compose.yaml, Cargo.toml, go.mod and more, including sub-folders, and picks the right runner (npm, pnpm, yarn, bun, uv, poetry, make...). Green ▶ starts a command, red ■ stops it.
• Honest "running" status. Green means a command is executing right now, as reported by your shell, not just "a tab is open". Every project card shows what is running inside it, even when folded, each with its own stop button.
• Your real shell. Each terminal is your own login shell (zsh, bash, fish) with your prompt, aliases and history. MrTerminal types the command for you, so Ctrl-C drops you back at a prompt exactly like in Terminal.app or iTerm.
• Layouts you arrange by dragging. Split, stack and resize terminals. Each project keeps its own layout, and its terminals keep running while you look at another project.
• Presets. Save a set of terminals and their arrangement ("Full stack") and start them all with one click tomorrow.
• Sessions that survive restarts. Quit and reopen: your projects, layouts and commands come back, and MrTerminal can start them again for you.
• Your own commands too. Add anything that is not in a script file (stripe listen, docker compose logs -f), give scripts friendlier names, and reopen a tab you closed by mistake with ⇧⌘T.

Six themes (Midnight, Dracula, Nord, Solarized Dark, Daylight, Solarized Light) recolour the app and the terminals together, and you can use any installed font.

Install

Download the build for your system from the Releases page:

• macOS (Apple silicon and Intel): .dmg (arm64 or x64).
• Windows 10/11 (x64): win-x64-setup.exe. Run the installer. The app is unsigned; Windows may show a SmartScreen prompt.
• Linux (x64): .AppImage or .deb. Make the AppImage executable (chmod +x MrTerminal-*.AppImage) and run it, or install the Debian package with sudo apt install ./MrTerminal-*.deb. AppImages need FUSE 2 (or launch with --appimage-extract-and-run).

Windows uses PowerShell by default, with your profile and PSReadLine. PowerShell and PowerShell 7 (pwsh.exe, selectable in Settings) report command status; custom Windows shells without integration do not provide running status or per-command exit codes.

Download the .dmg from the Releases page (arm64 for Apple silicon, x64 for Intel) and drag MrTerminal to Applications.

The macOS app is signed with a Developer ID certificate and notarized by Apple, so it opens normally on first launch.

Updates

MrTerminal checks this repository's GitHub releases when it starts and every few hours. On Windows and Linux, the update button opens the release page to download and install the newer build. On macOS, when a newer version exists an Update to x.y.z button appears in the top bar; clicking it downloads the update, verifies its checksum, replaces the app and restarts it, and your terminals reopen. Settings shows the running version and has a "Check for updates" button.

To publish a version: bump version in package.json, commit, then git tag v<version> && git push --tags.

Command line and coding agents: mrt

Everything you can click, mrt can do from a shell, and so can a coding agent such as Claude Code. Choose Shell → Install 'mrt' Command… once, then add the displayed directory to your PATH if needed. On Windows, add %USERPROFILE%\.mrterminal\bin to your user Path in Environment Variables and open a new terminal. Then:

mrt status                                   # what is open and what is running
mrt run dev                                  # start a script in its own terminal
mrt wait dev --match 'ready' --timeout 60    # until the server is up
mrt run test --wait                          # run tests: their output, their exit code
mrt read dev --lines 40                      # what a terminal printed
mrt send notes 'git status'                  # type into a terminal
mrt stop dev                                 # Ctrl-C

This is the beginning of the README. Read the rest at the original. Read the full README ↗