r/commandline • • 20h ago

Terminals mpx, a minimal multi-attach terminal multiplexer

6 Upvotes

mpx is a new terminal multiplexer I wrote as a replacement for tmux and screen.

It's much simpler, preserves scrollback and doesn't make any changes to the terminal byte stream.

But you can connect any amount of clients that are then in sync.

The easiest way to use it is to run it whenever you run a coding session- then you can always connect to all your sessions when you ssh in.

mpx is designed as an alternative to alternatives that usually lock you into a certain workflow or user experience. mpx is completely transparent and works with any terminal, and is fully cross platform working on linux, osx and windows.

Homepage (osx/windows/linux install) https://mpx.capocasa.dev
Github https://github.com/capocasa/mpx

$ mpx
$ # do something
... output is happening
Ctrl-G

$ ssh myhost
$ mpx a  # terminal is now identical to before
$ # do something
... output is happening

$ ssh myhost
$ mpx a  # connecting from a different host without detaching, still works
$ # do something
... output is happening

r/commandline • • 4h ago

Command Line Interface Websitino: a tiny static file server for previewing and sharing local files. Now with https!

Thumbnail trikko.github.io
2 Upvotes

r/commandline • • 21h ago

Terminal User Interface I added a Web UI and Cockpit integration to portop, my htop-style port monitor

0 Upvotes

A little while ago I shared portop here, my htop-style TUI for figuring out what is actually using your ports.

A few people suggested that it would be useful outside the terminal too, especially as a Cockpit page.

So I built both.

portop v0.1.0 now has a local web dashboard:

portop --web

It shows sockets, local/remote endpoints, processes, CPU usage, systemd units and Docker containers.

You can search and filter the table, inspect a process and see its command line, user, executable, memory, threads and open files.

You can also send SIGTERM/SIGKILL after confirmation.

I deliberately kept the web server local-only. It binds to loopback, and process details/actions require the token generated when portop starts.

And there's now a Cockpit integration too.

Install the page and you get:

Tools → Ports (portop)

directly inside Cockpit, without running another web server. It uses Cockpit's existing bridge and user permissions.

So there are now three ways to use portop:

portop → terminal UI

portop --web → local browser dashboard

Cockpit → integrated Ports page

The TUI is still the main interface. I just liked the idea of using the same port/process inspection underneath different frontends.

Repo: https://github.com/padovanl/portop

Thanks to everyone who suggested features after the previous posts. The Cockpit idea in particular came from community feedback.