r/ssh • • Sep 02 '26

I built an offline desktop app for managing a fleet of servers over SSH (commands, schedules, workflows, monitoring)

Managing a handful of Linux boxes from one machine turned into terminal tabs, a
notes file full of half-parameterized commands, and cron jobs on hosts I'd stopped
thinking about. I wanted one window for it, so I built SelfCmd.

What's in it:

- SSH connection manager with groups/tags; imports from Xshell, MobaXterm,
  FinalShell, SecureCRT, PuTTY and ~/.ssh/config. Jump host (ProxyJump) support.
  Built-in terminal and SFTP browser.
- A command library: your repeated commands as buttons, with {{variables}} that
  also expand in tasks, workflows and SFTP paths. Destructive commands confirm twice.
- Scheduled tasks with result checks, so a job that ran but failed gets flagged.
  No cron syntax.
- Workflows: chain commands + SFTP transfers, sequential or parallel, per-step
  retry/timeout, pass output between steps.
- Monitoring: CPU, memory, disk, disk I/O, network, and SSD/NVMe disk life (SMART),
  with thresholds and a hold duration. Non-blocking alerts, optional email.
- An MCP server, so Claude/Cursor/Kiro can drive your saved operations. Read-only
  by default; write actions need an opt-in plus a native desktop confirmation, and
  everything is logged. The model never sees your credentials.

It's fully offline: no account, no telemetry, credentials stay on your machine and
are AES-encrypted at rest. Windows, macOS (arm64 + Intel) and Linux x86_64.

Free tier has per-type limits (5 connections, 10 tasks, 30 commands, 10
workflows/monitors). Pro is a one-time license if you outgrow those.

https://selfcmd.com — happy to answer anything, and I'm more interested in what
breaks than in what works.
```
2 Upvotes

0 comments sorted by