DEV Community: rocky

Accelerate Server Threshold Verification with SelfCmd

rocky — Tue, 08 Sep 2026 17:41:24 +0000

In server administration and software testing, validating log retention policies, storage cleanup thresholds, and device lifecycle expiration logic is vital. However, testing these workflows traditionally forces engineers to wait days or weeks for actual time to elapse, or manually adjust system clocks repeatedly across multiple nodes—an error-prone and tedious process.
With SelfCmd, you can automate a seamless "time-acceleration" loop that shifts system clocks forward, syncs hardware time, reboots target servers, and diagnoses execution permissions automatically using AI.
1. Step-by-Step Task Setup: Automated Time Shifting
Using SelfCmd's Periodic Task Engine, you can automate clock modification and device reboot routines in a closed loop:
●Task Name: day+1 and reboot
●Task Type: Periodic Task
●Interval / Time: 1200 seconds (or custom intervals like 60s, 5m, 1h)
●Task Command:
date -s "$(date -d '+1 day' '+%Y-%m-%d %H:%M:%S')" && hwclock --systohc
●Options: Check Reboot system after task execution
By executing this task periodically, SelfCmd advances the system clock by one day and triggers a clean system reboot every cycle, compressing weeks of storage lifecycle testing into just a few hours.

** 2.Instant Troubleshooting with AI Diagnose**
Modifying system time requires administrative rights. When tasks fail due to missing sudo permissions or restricted Docker container capabilities (e.g., missing CAP_SYS_TIME), SelfCmd's AI Diagnose engine analyzes failure logs in seconds.

3. Key Product Advantages

Discover More: To explore the full feature set, user guides, and latest updates, visit our official website at https://selfcmd.com

SelfCmd – Simplify SSH Connections, Custom Commands, and AI Debugging

rocky — Mon, 07 Sep 2026 17:43:34 +0000

SelfCmd is a personal command center engineered for software engineers, system administrators, and DevOps teams. It unifies SSH/serial connection management, a reusable Command Library (Cmd Lib), cross-platform local and remote command execution, and AI-driven automated error diagnostics into a single interface.

1. Connection Management (Connections)
SelfCmd provides a central hub for managing remote host connections, network discovery, and embedded interactive sessions.
1.1 Creating a New Connection
1.Access Connections: Navigate to the Connections tab in the left sidebar to open the Connection Manager.
2.Add Connection: Click Add in the top toolbar and select Add one manually... (or utilize Scan for subnet discovery or Bulk Import).
3.Configure Connection Parameters: Fill out the required connection fields in the dialog:

Connection Name / Server Address: Set the alias and target IP address (e.g., 172.19.156.217).
Port & Username: Define the SSH port (default 22) and target account (e.g., rocky).
Auth Method: Choose between Password or SSH Key authentication.
Bastion Host: Enable Use a jump host (bastion) if tunneling is required.
Group & Tags: Categorize hosts into groups (e.g., Ungrouped) and comma-separated tags (e.g., prod, web, db).
MCP / AI Access: Define AI agent execution permissions (e.g., Full (read & run)). 4.Test & Save: Click Test Connection. Upon receiving the success confirmation (Connection test succeeded!), click OK or Save and add next.

1.2 Integrated Terminal & File Manager
SelfCmd integrates powerful inline session tools directly within the Connection Manager:
●Interactive Terminal: Launch an active SSH session directly in a dedicated tab or pop-up window.
●File Management & Verification: Switch to the Files tab to browse remote file structures, perform drag-and-drop file transfers, edit files directly, and generate MD5 checksums for integrity verification.

2. Command Library & Custom Command Management (Cmd Lib)
The Cmd Lib feature allows users to transform frequent shell commands and diagnostic scripts into interactive, reusable buttons.

2.1 Adding a Built-in Command
1.Navigate to the Cmd Lib tab and click + Add.
2.Configure the command properties:

Command Name: Give the command a descriptive label (e.g., print route table).
Command Content: Input the script payload (e.g., route print -4). Multiple statements can be separated by semicolons or newlines.
Condition / Template Inserts: Utilize {name} placeholders to turn scripts into dynamic parameter templates.
Group & Tags: Assign to a designated group (e.g., Default Group) and tags (e.g., network, diagnostic).
Local Command Flag: Check Local command (run on this machine) if the command should execute locally rather than over SSH. 3.Click OK to save the command to the button library.

3. Unified Command Execution Engine
SelfCmd's execution bar provides seamless switching between local operating system execution and remote SSH server execution.

3.1 Cyclic & Scheduled Execution (Repeat Mode)
For ongoing monitoring tasks (e.g., watching disk utilization, process health, or queue depth):
●Enable the Repeat checkbox on the execution bar.
●Set the interval duration (e.g., 5 s).
●SelfCmd will automatically execute the target command periodically and update the log console.

4. AI-Powered Error Diagnosis (AI Diagnose)
When command execution fails or returns non-zero status codes, SelfCmd leverages built-in AI intelligence to analyze logs and deliver root-cause breakdowns.
4.1 Diagnostic Workflow
1.Upon receiving a command failure (e.g., [FAIL] exit=127), select the error log text or click AI Diagnose on the toolbar.
2.Alternatively, right-click any selected log text in the Operation Log pane and choose AI Diagnose (selection / whole log).

4.2 Diagnostic Output Structure
The AI Diagnosis panel formats output into four structured analytical sections:
●Verdict: Clear, concise identification of why the script failed (e.g., missing binary or missing executable in system PATH).
●Error Summary: Grouping of distinct error messages and exit code occurrences.
●Likely Root Causes: Ranked probable causes, such as missing dependencies, environment variable misconfigurations, or syntax errors.
●Next Diagnostic Steps: Executable, safe troubleshooting commands ready for copy-pasting to verify environment state and apply fixes.

Website & Downloads: https://selfcmd.com

SelfCmd: one offline desktop app for SSH, scheduled jobs, workflows and monitoring

rocky — Wed, 02 Sep 2026 22:22:23 +0000

The problem with "just use the terminal"

Managing one server from a terminal is fine. Managing fifteen is a different job.

You end up with a browser-tab problem, except it's terminal tabs. The commands you run monthly live in a notes file, and half of them have a hostname or path you have to remember to swap out. The cleanup job you set up last quarter is a cron entry on a box you no longer think about. When disk fills at 2am, nothing tells you.

None of that is hard. It's just scattered, and the scattering is what costs you.

SelfCmd puts it in one window: connections, reusable commands, schedules, multi-step workflows, and resource monitoring. It runs entirely on your own machine.

What it actually does

Connections. Save hosts with groups and tags. Import existing sessions from Xshell, MobaXterm, FinalShell, SecureCRT, PuTTY or ~/.ssh/config, so switching clients takes seconds rather than an evening. Reach private hosts through a bastion with jump-host (ProxyJump) support, password or key on each hop. Open an interactive terminal or browse files over SFTP straight from a connection. Passwords are encrypted at rest with Fernet (AES-128-CBC + HMAC-SHA256); the key stays local.

Command library. Turn the commands you actually repeat into one-click buttons,grouped and tagged, with a "most used" view ranked by how often you run them.
Parameterize with {{variables}} that expand in commands, tasks, workflows and SFTP paths alike. The editor highlights shell syntax and previews the fully expanded command before it runs. Destructive commands (rm -rf, mkfs, dd) ask a second
time.

Scheduled tasks. One-off at a set moment, or repeating from seconds to hours, on a remote host or locally. Attach result checks so a job that "ran" but failed gets flagged. Pause and resume individual tasks, and keep a per-task output log. No cron syntax, no forgetting which box owns the job.

Workflows. Chain commands and SFTP transfers into a run you can repeat: pull code, upload config, restart the service, health-check. Sequential or parallel,per-step timeout, retry and stop-on-failure, and you can pass one step's output into the next. Export a workflow as JSON to share or version it.

Resource monitor. Track CPU, memory, disk usage, disk I/O, network bandwidth and SSD/NVMe disk life (SMART wear) against your own thresholds, with a hold duration so a brief spike doesn't page you. One host is one row with as many metrics as you want on it. Alerts are non-blocking toasts plus optional throttled email, and you get a recovery notice too.

Toolbox. Ping, port probing, LAN MAC lookup, SFTP/FTP transfer, a serial(COM-port) console for switches and embedded boards, and the small utilities you otherwise open a browser tab for: timestamp/epoch conversion, cron expression helper, JSON/YAML formatting, base conversion, checksums, text compare.

The two things that make it different

It runs offline, and it means it. No account to create. No telemetry. Your credentials, logs and server list never leave your machine, and the app doesn't phone home. Pro licenses activate offline and bind to the device. If our website went down tomorrow, your install would keep working exactly as before.

Your AI agent can drive it, without holding your credentials. SelfCmd ships a Model Context Protocol server, so Claude Desktop, Cursor or Kiro can list and run your saved commands, tasks and workflows, read metrics, tail logs and inspect remote files. It runs locally over stdio and reuses connections you already saved, so the model never sees a password.

The safety model is the point. Read-only tools work out of the box. Anything that changes state is off by default and needs an explicit opt-in, then a two-step confirmation with a native desktop prompt. Connections carry per-connection access tiers, dangerous commands and sensitive paths get screened, and every call lands in an audit log. An agent gets a set of reviewed operations, not a blank shell.

There's also an in-app assistant if you'd rather not wire up an agent: describe what you want in plain language, review the command it proposes, then run it on a connection you pick. Nothing executes without you looking at it first. When something fails, one click asks it to explain why.

Recent work (2.3.x)

The last round was mostly about fleets rather than single hosts.

One command can now target many hosts at once — scheduled tasks and the command library both take multiple connections and report a single combined summary. If a one-off task partially fails, retrying only re-runs the hosts that failed, so a server that already rebooted doesn't get rebooted twice. SFTP tasks got the same treatment in a dedicated window: one row per server, adjustable concurrency, a live queue and cancel.

Host availability also comes from one shared source now, so every connection picker agrees on who's online. Selectors probe in the background the moment they open, which means the "online only" filter is accurate without running "Test all" first.

Getting it

Windows 10/11 (64-bit), macOS 12+ (separate Apple Silicon and Intel builds), and
Linux x86_64 as a portable tar.gz (glibc 2.35+, so Ubuntu 22.04 and newer).

Starter is free, with limits that suit one person: 5 connections, 10 scheduled tasks, 30 library commands, 10 workflows and 10 monitors.

Download: https://selfcmd.com

If you try it, I'd genuinely like to hear where it gets in your way — especially the MCP piece, which is the newest and least battle-tested part.