Changelog

What's new in SpinupTUI

Page 2 of 6.

v0.26.1

Launch from inside a site checkout

September 18, 2026

Starting spinuptui from inside a site's checkout, where many of us live all day, could quietly feed that site's own .env into what the app does. This patch closes that off.

Fixed

  • pull db works when launched from inside a site's checkout. Bun auto-loads the .env of the directory you start it in, and every process spinuptui spawned inherited it. So a Bedrock site's own DB_* values reached wp as real environment variables. Some Bedrock configs then read blank database credentials, and the pre-import backup failed with Access denied for user '<you>'@'localhost' (using password: NO). Keys from the launch directory's .env are now dropped at startup, and every child process gets the cleaned environment. Anything you exported in your shell is kept.
  • A site's .env can no longer supply your DNS provider credentials. The names are generic, and Bedrock sites commonly keep S3 media keys under AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY. Launched from such a checkout, spinuptui used them as its Route 53 credentials, silently overriding the ones in config. Provider keys (AWS_*, CLOUDFLARE_API_TOKEN, GODADDY_API_*) from a .env are now honored only in spinuptui's own project directory. Shell-exported keys work from anywhere, as before.
  • pull db's "Access denied" hint points Bedrock and Radicle sites at their .env. It used to blame wp-config.php for every site, but those stacks keep their database credentials in .env.

Notes

  • If you were syncing from inside one site's checkout on 0.26.0, it's worth a quick check that the right local database got the import. Depending on a site's Bedrock config, the leaked values could fail outright or, in principle, point wp at the launch site's database instead.

View on GitHub →

v0.26.0

Clone a local working copy from production

August 26, 2026

Getting a site onto your machine used to be the one step SpinupTUI left you to do by hand. Now it's a keypress — or a command an agent can run.

Highlights

  • Clone a local working copy from production (L → c). On a site you have no copy of yet, L now offers a choice: e to type in a path you already have, or c to build the copy. It pulls the code down — git clone for git-deployed sites, rsync over SSH for the rest — runs composer install for Bedrock/Radicle, links the result, and hands off to the DB pull (p) and media fallback (m) you already know. Your local database and webserver config are never touched.
  • The same thing from the command line. spinuptui pull files <domain> [path] and spinuptui pull db <domain> --yes drive the identical engines with no TUI. Progress goes to stderr, the result to stdout — with --json, one object, exit code mirroring ok, and every failure carrying a stable reason plus a remedy naming the exact command that fixes it. Built so "pull that site down for local dev" can be handed to an agent.
  • --server <name> everywhere a domain is resolved (ssh, ssh-exec, both pull commands). A domain can legitimately live on two servers — a clone destination, a staging twin — and those sites were previously unreachable from the CLI: the ambiguity could be reported but never resolved. It now lists what matched and names the flag that picks one.
  • Search gets the full-width Control drawer from the Servers tab, instead of swapping its right-hand panel between Details and Actions. The Details pane stays put while you browse, and both views now share one control component, so they can't drift apart again.

Notes

  • A cloned copy needs its database credentials pointed at your machine before pull db will run, and the app now says so at the point it matters. The file pull brings the site's real wp-config.php down — production credentials and all — so local WP-CLI would otherwise authenticate as the production DB user and be denied. A Bedrock/Radicle clone has the opposite problem: .env isn't in the repo, so the checkout arrives without one. Both cases are flagged on the clone screen and again on a failed pull.
  • wp-content/uploads is deliberately skipped (that's what the media fallback is for), as are object-cache.php and advanced-cache.php — SpinupWP's Redis drop-in doesn't degrade quietly without Redis, it 500s on a cache miss.
  • The clone honors the layout rules the rest of the app does: it takes the site's whole files root, so a public/-style webroot brings wp-config.php down from the directory above it, and the real webroot is detected on the server rather than inferred from the public_folder setting.

Fixed

  • K (grant SSH key) and V (create/resume vanity site) now work on server results in Search, not just site results — both were advertised in the legend and silently did nothing.
  • A failed local-database backup no longer leaves a fake backup behind. The pre-import dump created its file before it could fail, leaving a bare .sql — empty, or worse, partial — sitting in sql/ looking like a safety net.

View on GitHub →

v0.25.0

Pending upgrades are now actionable

August 12, 2026

Server actions no longer leaves a pending SpinupWP platform upgrade as a dead end.

Highlights

  • Server actions surfaces pending SpinupWP upgrades. The API only exposes this as a flag — no title, no description, no endpoint to run it — so the overlay (a) now shows a banner explaining that, with w to jump straight to the upgrade in the SpinupWP web app.
  • App version on the splash screen, shown while the first batch of data loads.

Fixed

  • The reboot-pending detail line now shows the real reason when the SSH probe fails (e.g. an auth error), instead of a generic "couldn't read detail over SSH" message.
  • Long banner text now wraps across lines instead of overflowing the panel border.

View on GitHub →

v0.24.4

the toast crash is actually fixed now

August 6, 2026

If v0.24.2/v0.24.3 still had you crashing on startup, this is the real fix.

Fixed

  • Startup crash: Unknown component type: toaster, for real this time. The previous two patches tried to fix this by pinning/overriding the opentui version we depend on, but that only works for a local project install — it has no effect on a global install (bun add -g, npm install -g), which is how everyone actually runs spinuptui. The real problem was the toast library itself: it's stuck on a peer-dependency range from opentui's very early days, and no version pin on our side could fix how it resolves its own dependencies downstream. Every toast this app ever shows is a single-line success message, so the external toast library is gone — replaced with a small first-party implementation with no external dependency and no peer-dependency surface left to break on a future update.

View on GitHub →

v0.24.3

fix a startup crash from a duplicate opentui install

August 6, 2026

If v0.24.2 left you crashing on startup with Unknown component type: toaster, this fixes it.

Fixed

  • Startup crash: Unknown component type: toaster. The 0.24.2 fix pinned @opentui/core/@opentui/react, which resolved a toast-dismissal crash but exposed a second bug: the toast library's peer-dependency range is ancient (predates the current 0.4.x line) and our pinned version can't satisfy it, so a fresh install ended up with a second, independent nested copy of @opentui/react alongside ours. The toast library registers its custom <toaster> component on that nested copy, which our app's copy never sees — crashing the moment the toast area tries to mount. package.json now forces a single deduped install everywhere via overrides.

View on GitHub →

v0.24.2

fix toast crash from an @opentui/core dependency drift

August 6, 2026

Fixes a crash some of you may have hit on a fresh install: dismissing a toast (PHP upgrade, reboot, cache purge, etc.) could throw remove expects a renderable child object and take the app down.

Fixed

  • Toast dismissal crash. @opentui/core changed the signature of an internal method it uses starting at 0.4.3, and the toast library spinuptui depends on hasn't published a matching fix yet. Our dependency range let a fresh install with no lockfile — most likely on a machine installing spinuptui for the first time — resolve onto that broken later patch. @opentui/core and @opentui/react are now pinned to the last known-good patch (0.4.2) until the toast library ships a compatible release.

View on GitHub →

v0.24.1

fix bun update -g silently not updating

August 6, 2026

bun update -g spinuptui not updating for you? I just figured out why...since we're at the pre-release stage (i.e. not yet to v1.0.0), that command will silently fail. To pull the latest pre-release version, you must run bun add -g spinuptui@latest. More details below:

Fixed

  • bun update -g spinuptui no longer silently fails to update. While spinuptui is pre-1.0, a package-manager global install records a caret version range (e.g. ^0.22.2) that, under semver, only matches patch releases — every later minor release fell outside it, so update -g reported success without actually updating anything. The documented and in-app update command (Help/About panel, README) is now bun add -g spinuptui@latest, which always pulls the true latest version.

View on GitHub →

v0.24.0

Pull prod. DB is discoverable even when local sync is off

July 15, 2026

Added

  • p (Pull prod. DB) is now discoverable even when localSync is off. Previously the Site Control legend hid the entry entirely until localSync was enabled in config — the only one of p's three preconditions (WordPress, linked copy, localSync) that hid the entry instead of flashing a message on press. Now p always shows for WordPress sites; pressing it with localSync off opens an in-app "Enable local sync?" confirm instead. Confirming just saves the setting — you press p again afterward to actually pull, so the destructive action itself stays behind two deliberate presses, same as before.

View on GitHub →

v0.23.0

Radicle sites are now detected and labeled

July 15, 2026

Radicle (Roots' Bedrock+Sage+Acorn+Trellis starter for WordPress) is now its own detected stack, instead of being misclassified as Bedrock.

Added

  • Radicle sites are now detected and labeled as their own stack. Radicle shares Bedrock's roots/bedrock-autoloader dependency, which was tripping a naive roots/bedrock string match; detection now keys off roots/acorn instead — the package that actually makes a site Radicle. Radicle only surfaces via the on-demand SSH probe (f in the Servers/Search tabs, d/D in Stacks) — its /public/ webroot alone is indistinguishable from a hardened Standard-WP /public/ layout. DB backup/sync, plugin/theme inventory, and local working-copy linking already worked on Radicle sites (their path detection was already stack-agnostic); this release just adds the missing name. Clone-wizard support for Radicle is a separate, not-yet-built follow-up.

Fixed

  • A few README/docs mentions of p (plugins & themes) and m (monitoring) that slipped through the previous release's key-unification work — corrected to e and M, and scope notes broadened from "Search tab" to "Servers / Search tabs" where applicable.

View on GitHub →

v0.22.3

Site Control keys work the same in Servers and Search

July 15, 2026

A fix-up release building on last week's Servers-tab Control strip work.

Fixed

  • p actually pulls the production DB in the Servers tab now. The Site Control legend labeled it "Pull prod. DB," but pressing it opened the plugins/themes inventory instead — the DB-pull action was never wired up in that tab at all. Plugins/themes moved to e in both the Servers and Search tabs.
  • d, m, a, K, and f now behave the same in the Servers tab and Search. The shared Site Control legend was written against Search's key bindings, and the Servers tab had silently diverged on several of them: d ran a stack-identify probe instead of a DB backup, m had no media-fallback binding at all, a (reboot/restart) silently did nothing with a site focused, and K (grant SSH key) was listed in Search's legend but never actually wired up there. The stack-identify probe now lives on f in both tabs.

View on GitHub →