Changelog

What's new in SpinupTUI

Page 3 of 6.

v0.22.2

Keychain save failures are no longer silent

July 14, 2026

A follow-up fix-up release, on top of v0.22.1.

Fixed

  • A failed "Remember in macOS Keychain" save no longer fails silently. If the underlying security write fails — most commonly a locked login keychain — the sudo connection itself still succeeds, but the "Sudo connected" panel now shows the real reason as a warning instead of silently reverting to "kept in memory only, never saved" with no explanation. If you see this warning, try unlocking your login keychain (security unlock-keychain ~/Library/Keychains/login.keychain-db in Terminal) and reconnecting.

View on GitHub →

v0.22.1

Grant-key drawer discoverability fix

July 13, 2026

A small fix-up release for v0.22.0's Servers-tab Control-strip rebuild.

Fixed

  • K (grant/revoke SSH key) is discoverable again. The v0.22.0 Control-strip rebuild dropped it from both Site Control and Server Control's action lists — the keybinding itself kept working the whole time, but you had to already know it existed to use it. It's back in Site Control's Remote group and Server Control's Access group, and now also works from the Servers pane (falling back to the server's first key-eligible site as the anchor), matching how S/h already work from either pane.

View on GitHub →

v0.22.0

Actions everywhere + spinuptui ssh-exec

July 13, 2026

Two threads land together here: a safe way for external tooling/agents to run diagnostics over SSH, and a redesigned Servers tab where every action is fully visible — no hidden key combos, nothing to memorize.

Highlights

  • spinuptui ssh-exec <domain> -- <command> — resolves the domain's SSH target and runs a command, but only if it's read-only; anything that looks like a write/restart/destructive action is denied before it ever reaches the server. Built for external tooling that needs diagnostic access without building its own guardrails — logs every attempt (allowed/denied/unresolved) to <config dir>/logs/ssh-exec-audit.jsonl.
  • Every site/server action is now always visible. The Servers tab's bottom strip is now a full-width Control strip showing the whole action list (Open/Remote/Local/Vanity/Server for a site, or Clone/Access/Manage/Open for a server) — grouped, key-chipped, and flowing across the terminal width, so a long group fits on one line instead of stacking one item per line.
  • Refreshing a vanity page's HTML (R) is now discoverable everywhere a site can be selected — previously it only lived inside the m monitoring overlay.
  • Search and the Servers tab no longer duplicate their own action list in the footer — it lives in one place (the Control strip / Search's Actions pane), so it can't drift out of sync. Also fixed a stale Search hint (⏎ open site) shown even on a server row, where Enter is a no-op.

Notes

  • The Sites list dropped its per-row status badges (linked/keys/HTTPS/cache/backup/updates) — that info's already shown in Details for the selected site — to keep domain names readable at normal terminal widths.
  • Two earlier designs were tried and reverted before landing on the Control strip: a 4th always-visible side panel (cost too much width, squeezed the Sites list unreadable) and a scrollable Details panel (worked, but depended on an undiscoverable key combo and broke Search's own scrolling, since the two views share that component).

View on GitHub →

v0.21.2

Bedrock detection at any nesting depth

July 10, 2026

A reliability release for Bedrock sites whose project root isn't directly under the site's files root (moved into its own subdirectory) — a real-world layout that previously went undetected across the app.

Fixed

  • Bedrock detection now works at any nesting depth. Detection previously relied on a fixed, shallow search that could miss a nested Bedrock project even though the site worked fine and SpinupWP itself knew it was WordPress. It now anchors on the site's configured Public Folder at any depth, shared across the app:
    • The plugins/themes view (p) finds core correctly instead of reporting "no WordPress core found."
    • App identification (d) correctly labels it "Bedrock" again, not just generic WordPress.
    • The clone wizard's Bedrock pull no longer hardcodes web/. It re-detects the real project root independently on both source and destination (they're not assumed to match — the destination's layout comes from the git repo's own committed content, not the source's on-disk state), and fails cleanly with a specific message if the two disagree, instead of failing opaquely partway through. A pre-flight check also catches the common case of that mismatch before a destination site is even created.
    • The Stacks tab's default (pre-probe) "Bedrock" label also recognizes a nested webroot like site/web, not just an exact web.
  • A first-time local Bedrock pull now explains itself. "Pull production → local" (p in Search) backs up the local database before overwriting it — on a fresh Bedrock checkout with no vendor/ yet, that step failed with wp-cli's generic "not a WordPress install" error. The message now suggests running composer install first when that's the likely cause.
  • Clone-wizard error messages no longer get cut off at a fixed, often-too-short length. The site roster, Git-access deploy-key list, and DNS cutover roster all truncated errors to a small fixed character count regardless of available space. Errors now fill whatever room the row actually has.
  • Onboarding's API token link was a 404. Replaced with generic "Settings → API Tokens" navigation instructions, since the correct URL is account-specific and can't be known before you have a token.

Notes

  • Nested Bedrock layouts are now correctly detected in the plugins/themes view, app identification, and the clone wizard's size estimate — all live-tested. A standard (non-nested) Bedrock clone through the rewritten pull chain was also live-tested end to end, including a real DNS cutover. The clone wizard's pull for a nested Bedrock site detects a source/repo mismatch and refuses cleanly before creating anything, but the success path — a genuinely nested repo cloning through to completion — hasn't been live-validated yet. If you hit this, we'd welcome a report.

View on GitHub →

v0.21.1

Uptime Kuma connection reliability fix

July 10, 2026

A small reliability release: fixes an Uptime Kuma connection failure some users could hit depending on their network path to their Kuma instance.

Fixed

  • Connection now falls back to HTTP long-polling. SpinupTUI talks to Uptime Kuma over its socket.io management API, and the client previously connected over WebSocket only. If a reverse proxy or CDN sits in front of your Kuma instance and doesn't forward the WebSocket upgrade headers, that made the connection fail outright with no way to recover. It now also tries HTTP long-polling, so a proxy that mishandles the WebSocket upgrade no longer blocks the connection entirely.
  • Connection failures no longer swallow the real reason. A failed connect could previously show up as Couldn't reach Uptime Kuma at https://…: with nothing after the colon — the underlying error's message came back empty, and that empty string got used as-is. The error now checks the underlying error's description and error code before giving up, so a connection failure actually tells you something useful instead of a dangling colon.

Notes

  • If you were hitting a connection error before this release, it's worth retrying — the polling fallback may resolve it outright. If it still fails, the error message should now be more informative about why.

View on GitHub →

v0.21.0

CLI access commands + monitoring UI overhaul

July 9, 2026

A monitoring blind spot gets closed, and external tooling gets a front door in: an incident-diagnostics agent can now go from "here's a domain" to a live SSH session and its recent Kuma history without any manual lookup, and the site/server monitoring overlay gets a full rebuild to make sense of six monitor kinds instead of cramming them into a popover.

Highlights

  • spinuptui ssh <domain> and spinuptui incidents <domain>/--all. Two new non-interactive CLI subcommands built for external tooling — an incident-diagnostics agent handed only a domain can now resolve it to a live SSH session (ssh, with classified failure reasons: not found, ambiguous match, no server IP, key not granted, token rejected, …) and pull Uptime Kuma's down/up history as JSON (incidents), scoped to sites SpinupTUI actually manages monitoring for so every domain it surfaces is one ssh can reach. Both output structured JSON with exit codes.
  • A real monitoring blind spot, closed with two new monitors. SpinupWP's page cache can keep serving 200 OK on / while PHP is fataling on everything the cache doesn't already have — confirmed against a real incident that ran undetected for 54 of its 68 minutes. A PHP-fatal sentinel (one root cron per server, tailing every site's error/debug logs, needs sudo connected) catches fatals hiding behind a still-warm cache and names the affected domain in its alert. A cache-bypass monitor (opt-in per site) forces a real PHP render every check via the same bypass cookie the site doctor uses, catching a wedged PHP-FPM pool that never even logs a fatal. Both surface automatically in spinuptui incidents --all.
  • Site/server monitoring rebuilt as a full-screen two-pane browser (m on any site), replacing the old centered popover. A narrow list of monitor kinds with live status dots sits next to a wide detail pane explaining whichever one is selected — what it is, how it actually works, and how to act on it — instead of a cramped 68-column box and a disconnected glossary screen. The six per-kind action keys collapse into one a that acts on whatever's highlighted. New in the same pass: a passive "Alerts: …" header line showing notification wiring without pressing n; o to deep-link straight to a monitor's page in Kuma; and confirm-gated x to remove a front-page or cache-bypass monitor (the other four kinds re-derive themselves automatically, so removal doesn't apply there).

Changed

  • The header's fleet-wide "N monitors down" badge now names the affected domain(s) — falling back to a bare count once there are too many to list — and points at Search to find them, instead of an unactionable number.

🤖 Generated with Claude Code

View on GitHub →

v0.20.1

README rewrite + Dev Mode fleet scale-up

July 9, 2026

A docs/quality-of-life release: the README got a lot easier to skim, and Dev Mode's example fleet is big enough now to actually show off the app.

Changed

  • README rewritten for readability. It had grown to 857 lines of dense, multi-paragraph feature bullets — hard to skim for someone landing on the repo. Added a screenshot gallery (real Dev Mode captures of all five main tabs), condensed the Features list to one-liners, and moved all 13 deep-dive "how it works" sections into their own pages under docs/ (linked from the README's short pointer paragraphs). No content was removed, only relocated; RELEASING.md's "Keep the README current" checklist is updated to match the new house style.
  • Dev Mode's example fleet scaled up from 4 servers / 6 sites to 12 servers / ~80 sites / 19 events, generated deterministically (same fleet every run) with a realistic spread of EOL Ubuntu/PHP, Standard WP/Bedrock/non-WP sites, disabled HTTPS, and missing backups — mainly so the new screenshots (and any future ones) show a fleet worth looking at.

View on GitHub →

v0.20.0

Clone wizard correctness fixes + dest-picker site counts

July 8, 2026

Three correctness fixes for the clone wizard, all root-caused from real live incidents, plus a small quality-of-life addition.

Added

  • The clone wizard's existing-server picker now shows each server's current site count. Picking a destination previously showed only provider/region/IP — no sense of how busy a candidate already is. Each row now leads with N site(s).

Fixed

  • The clone wizard no longer routes git-deployed non-WordPress sites through a Bedrock pull. cloneStackFor trusted git.repo alone as "this is Bedrock" — but a git-deployed static site would be routed through composer install/wp-cli anyway, which it can't survive. A conclusive non-WordPress probe (whmcs/laravel/static) now overrides git.repo.
  • The clone wizard no longer silently skips the database for API-mislabeled WordPress sites. Its stack picker read is_wordpress straight from the API, unlike every other view, which corrects that flag against a d probe result. A mislabeled site would default to a files-only pull — filesystem copied, database never touched. The wizard now consults the same probe-corrected classification: probe the site (d) before cloning.
  • wp-cli reads now use the site's own configured PHP version, not the server's system default. wp-cli's shebang resolves through PATH to whichever PHP a server's update-alternatives currently calls default — independent of any site's configured version, and it can be missing extensions that version's CLI never got configured with. This broke the clone wizard's Verify step (v) and the installed plugins & themes view (p) whenever they differed. Verify also now distinguishes "the clone actually differs" from "wp-cli couldn't read one side's database," instead of a wall of misleading ✕ rows.

Notes

  • All three fixes share an operational caveat: probe a site (d) before cloning it so the wizard's Plan step has a corrected classification to consult — an unprobed site falls back to today's heuristics.

🤖 Generated with Claude Code

View on GitHub →

v0.19.1

Finish the SpinupTUI rebrand

July 8, 2026

A docs-only follow-up to v0.19.0 — no app behavior changed.

Fixed

  • Finished the SpinupTUI rebrand in the README and cover banner/social-preview images. The v0.19.0 rename swept the CLI banner, header wordmark, and app chrome, but missed 14 mid-sentence "Spinup" mentions scattered through the README's prose, and the cover banner/social-preview images still spelled out "SPINUP" in block-letter art. Both are fixed now; spinup-sudo (a Keychain service name) and the spinup-tui machine key (a literal SSH key identity) are unaffected — they're real persisted identifiers, not branding.

🤖 Generated with Claude Code

View on GitHub →

v0.19.0

Meet SpinupTUI, now on npm

July 8, 2026

The app has a proper name and a proper install: SpinupTUI, published to npm.

Highlights

  • Install with one command. bun install -g spinuptui puts the spinuptui command on your PATH; update any time with bun update -g spinuptui. No git checkout needed (that path still works for development). Running the bin under Node prints a friendly "install Bun" pointer instead of a crash — the terminal renderer needs Bun's FFI.
  • The app is now "SpinupTUI", and the command is spinuptui. The rename distinguishes the app from the SpinupWP service it talks to (and plain spinup was taken on npm). Nothing else moves — your config stays at ~/.config/spinupwp-tui/config.json.
  • The update hint knows how you installed. The ? About panel shows package installs the bun update -g spinuptui one-liner; git checkouts keep the in-place u (git pull) updater.

Fixed

  • Clone wizard no longer falsely fails a site when SpinupWP is slow to run its add-domain event. SpinupWP serializes events per server, so under a concurrent clone an additional-domain add can queue for minutes behind site-creates — the old 3-minute poll gave up mid-queue, reported "failed on SpinupWP", and aborted the site before any files were copied, even when the event succeeded seconds later. The poll now waits out queueing (30-minute backstop), takes one final look before giving up, and reports a timeout honestly — a per-site retry resumes safely.
  • An honest header badge when a server-connect build is waiting on you. A vanity-site build parked at the manual SSH-key step used to show a perpetual "Connecting…" spinner, as if work were happening. It now says what it wants and where: ○ {server} needs your SSH key — press V.

Notes

  • Source-checkout users: re-run bun run link-global to get the spinuptui command (and bun unlink the old spinup link if you had one).

🤖 Generated with Claude Code

View on GitHub →