speculos-toolkit 1.2.4 → 1.2.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "speculos-toolkit",
-  "version": "1.2.4",
+  "version": "1.2.5",
   "description": "The Speculos toolkit for coding agents \u2014 deploy any frontend/backend to a live URL and build against your linked data connectors (BigQuery, Postgres, Snowflake, Salesforce, \u2026). Built for Claude Code, Codex, Cursor, and friends.",
   "bin": {
     "speculos-toolkit": "bin/speculos-toolkit.js"

package/skill/SKILL.md

@@ -156,7 +156,8 @@ The last stdout line is `{ ok, brokerUrl, connectors: [{ alias, name, kind, acco
 - **A frontend-only deploy keeps the app's backend.** `--no-backend` (or a repo where the
   backend did not change) redeploys the frontend against the SAME backend URL and says so
   (`backendKept: true`); it used to silently bake `null` and the live app started 404ing
-  its own API. Pass `--unset-backend` to actually detach it.
+  its own API. Pass `--unset-backend` to actually detach it — that sticks: the app
+  stays detached until a deploy actually ships a backend again.
 - `ok:true` with empty `connectors` → nothing linked (or nothing granted to this user).
   If the app clearly wants external data, tell the user to link a source (or ask their org
   admin for access) at **https://unified.speculos.ai/?tab=deploys**, then **re-run the list** —

package/src/index.js

@@ -121,7 +121,8 @@ OPTIONS
   --no-backend       frontend-only: skip backend even if one is detected (the app
                      keeps pointing at the backend it already has)
   --unset-backend    clear this app's backend URL: the frontend stops calling a
-                     backend (the sandbox itself stays up — use teardown for that)
+                     backend (the sandbox itself stays up — use teardown for that).
+                     It stays cleared until you deploy a backend again
   --private          only you can open the deployed app (needs an account;
                      the DEFAULT for a new app once this machine is linked)
   --org              anyone in your org can open it (needs an account)
@@ -280,11 +281,13 @@ async function cmdDeploy(root, opts) {
   // at the backend it already has, which allocate reports. Without this, the
   // rebuilt bundle and the regenerated speculos-env.js both said "no backend"
   // and a live app started 404ing its own API. --unset-backend is the explicit
-  // way to clear it (the backend sandbox itself stays up; `teardown` removes it).
+  // way to clear it, and the orchestrator remembers that: later frontend-only
+  // deploys stay detached (the backend sandbox itself stays up; `teardown`
+  // removes it).
   let keptBackendUrl = null;
   const liveBackendUrl = (alloc && alloc.backendUrl) || null;
   if (!backendUrl && liveBackendUrl) {
-    if (opts.unsetBackend) log(opts, `↪ clearing this app's backend URL (--unset-backend) — the backend itself stays up`);
+    if (opts.unsetBackend) log(opts, `↪ clearing this app's backend URL (--unset-backend) — it stays cleared until you deploy a backend again; the backend itself stays up`);
     else { keptBackendUrl = liveBackendUrl; log(opts, `↪ keeping this app's existing backend: ${keptBackendUrl} (--unset-backend to clear it)`); }
   }
   const feBackendUrl = backendUrl || keptBackendUrl;