4.0.0-beta.1 — V4 preview

A preview of V4, published on GitHub only. npm still serves 3.8.5: nothing here reaches an existing installation. The stable 4.0.0 follows once this preview has been used for real.

What V4 is

The control plane — see what an agent is running on your servers, with its output, and stop it before it runs.

• A desktop application that is the control plane: no Node, no npm. Live output of what the agent runs, a queue of commands waiting on your decision, a dual-pane file browser, health on demand, an interactive shell on any server and on your own machine, in tabs.
• An encrypted vault for credentials (AES-256-GCM, key in the OS keychain). Your .env is never modified.
• Human approval, per server — destructive or always. When approval is required and the application is closed, the request is refused, never let through.
• Telling your servers an agent is driving — AI_AGENT=mcp-ssh-manager on every command, off by default. Contributed by @mthamil107 (#84).

Downloads

Platform	File	Signature
macOS, Apple silicon	…-arm64.dmg	Signed (Developer ID) and notarized by Apple
macOS, Intel	…-x64.dmg	Signed and notarized
Windows x64 / arm64	…-setup.exe	Not code-signed in this preview. Windows shows "Windows protected your PC" — More info → Run anyway. The stable release will be signed.
Linux x64	.deb, .AppImage	Unsigned, as Linux packages usually are

Trying the npm engine without touching your installation

npm install --prefix ~/ssh-manager-v4-preview \
  https://github.com/bvisible/mcp-ssh-manager/releases/download/v4.0.0-beta.1/mcp-ssh-manager-4.0.0-beta.1.tgz
~/ssh-manager-v4-preview/node_modules/.bin/ssh-manager control

mcp-ssh-manager-4.0.0-beta.1.tgz — SHA-256 84e576bcf42b62b4d2389a022e38e51a2835b9a25b531e8802cc805eeab663c3

If you use 3.8 today

Upgrading changes nothing on its own: same 37 tools with identical schemas, same .env / TOML / environment configuration, no interface, no vault, no prompt — proved by a test that installs 3.8.5 from the registry, upgrades over it, and rolls back.

One deliberate exception: SSH host keys are now verified. 3.8.5 never compared the key a server presented. V4 does: an unknown host is trusted on first use and recorded; a changed key is refused. A server rebuilt since its key was recorded will be refused until you check its new fingerprint and remove the old entry. How, and why.

Upgrade and rollback guide · Changelog

Also in this preview: the CLI's edit server menu works again — fixed by @TheRealKamisama (#83).

An installed preview updates itself — to the next preview, and to 4.0.0 when it is released. Stable installations are never offered a preview.

Found something? Open an issue and say it is about 4.0.0-beta.1.