Changelog

v1.1.1

ssh-exec's read-only guard closes its Redis and WP-CLI gaps · October 1, 2026

A fix release for spinuptui ssh-exec, the command that lets an agent run diagnostics on a server without being able to change it. Its read-only guard let Redis writes and many WP-CLI writes through. Both are closed, and the update command now reliably fetches the newest version.

Fixed

  • Redis writes are denied. The guard had no rules for Redis, so redis-cli CONFIG SET …, FLUSHALL, FLUSHDB, BGSAVE and plain SET/DEL ran as if they were diagnostics. redis-cli is now allowed only with a known read: ping, info, dbsize, lastsave, config get, memory doctor|stats|usage, latency latest|history, slowlog get|len, client list|info and a few key-inspection reads. Everything else is denied, including unrecognised options and a bare redis-cli fed from stdin.
  • Unlisted WP-CLI writes are denied. The guard named a dozen WP-CLI writes and allowed every other command, so wp transient delete, wp search-replace, wp eval, wp plugin uninstall and wp cron event run got through. wp is now allowed only with a known read (plugin list, option get, core version, cache type, cron event list, db size and the like), and --exec, --require, --ssh and --http are refused on any command.
  • Denials say what was refused. The message names the verb or option, for example redis-cli `config set` is not on the read-only allowlist.
  • The update command now actually updates. The About panel (?) suggests bun add -g spinuptui@latest --no-cache. Without --no-cache, Bun can resolve @latest from a cached copy of the package listing and reinstall the version you already have.

Changed

  • wp user list, wp user get and wp user list-caps are allowed. The guard used to refuse everything under wp user, reads included. Creating, deleting and changing users is still denied.

Notes

  • Two reads that used to pass are now denied: wp config get and wp config list, because they print the database password into the audit log.
  • A WP-CLI read that isn't on the list is denied too, where it used to pass. If a diagnostic you rely on is refused, open an issue and it can be added.
  • The guard still isn't a sandbox. Outside redis-cli and wp it matches known-destructive patterns, so it catches mistakes, not a determined write.

View on GitHub →