Terminal
A real terminal session with recorded shortcuts, installed fonts and a live colour preview while you choose a theme.
Windows · .NET 10 · MIT
Every server,
Every server,
one window.
An SSH terminal, SFTP and a live resource monitor for the Linux and macOS machines you look after. No agent to install on the far side — it reads what the system already reports.
The Monitor page, running against a real Linux host. Numbers are live.
PlatformWindows 10 / 11
Runtime.NET 10, self-contained
RemoteLinux & macOS
AgentNone
LicenseMIT
Six things, done properly
Each one is a page you can keep open. The window is quiet on purpose — nothing moves unless a server tells it something.
Files
SFTP beside the terminal. Upload, download, rename and delete with progress that tells you the speed, not a spinner.
Monitor
CPU, memory, disks, network throughput and NVIDIA GPUs, read from the system's own tools. No daemon, no agent, nothing to deploy.
Identities
Passwords or keys, saved once and shared across servers. Stored encrypted under your Windows account, never in plain text.
Snippets
Keep the commands you type every week, then run one across a group of servers at once and read the output together.
Port Forward
Reach a database or a dashboard on a private network as if it were local. Start it, leave it, close it when you are done.
One probe, every number
A single merged script samples the counters twice, a second apart, then reads everything else behind markers. One exec channel, one round trip.
What it reads
CPU
/proc/stat sampled twice, per-core and total
Memory
/proc/meminfo, or vm_stat on macOS
Disks
df -Pk, so a mount point with spaces survives
Network
/proc/net/dev deltas, or netstat -ibn
GPUs
nvidia-smi -q -x, on its own channel so it can be slow
Load
/proc/loadavg, or top -l 2 on macOS
If it goes wrong
A hung probe empties its own card and leaves the rest alone. Lose the connection and the last reading stays on screen, labelled, instead of blanking out.
Why no agent
Everything here is a tool the operating system already ships. Nothing to install, nothing to keep updated, nothing listening on the far side.
Two ways in
Download
Grab the zip
Self-contained build — the runtime is inside it, so there is nothing
else to install. Unpack it and run Catussh.exe.
From source
Build it yourself
Needs the .NET 10 SDK. WebView2 ships with Windows 10 and 11.
git clone https://github.com/SwufeFox/catussh.NET
cd catussh.NET
dotnet run --project src/Catussh.AppWindows 10 or 11, 64-bit. The servers you point it at can be any Linux, or macOS.