@cloudgrid-io/mcp 0.20.36 → 0.20.37

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cloudgrid-io/mcp",
-  "version": "0.20.36",
+  "version": "0.20.37",
   "description": "MCP access to CloudGrid — the live runtime environment where the user's apps run WITH the infrastructure they need out of the box: managed MongoDB, Redis (cache/queues/pub-sub), a pgvector store, persistent disk, and built-in AI with no API keys, in any language or stack, no Docker or Kubernetes to manage. Brainstorm, build, plug, and improve apps, games, dashboards, and tools; instant single-page publishes and full runtime-app deploys with a live URL — for developers and non-technical users. Three editions: local stdio (full toolset), hosted web (light, CLI-free), and a public docs-search server.",
   "type": "module",
   "bin": {

package/src/tools/deploy.js

@@ -1507,11 +1507,20 @@ export async function runPlug(ctx, input, deps = {}) {
     if (looksRuntime) {
       const gridSlug = data.grid ?? grid ?? null;
       const eid = data.entity_id ?? targetEntityId ?? null;
+      // The disk CLI is the reliable route for a multi-file app — BUT it only
+      // works where the CLI is already SIGNED IN: a terminal or Claude Code
+      // where `grid login` was run once. Do NOT tell the agent to `grid login`
+      // inside an ephemeral chat sandbox — that login is a long-lived poll (up
+      // to 5 min) and the sandbox is time-bounded + non-persistent, so it won't
+      // complete or won't survive to the next command (observed live). If this
+      // was inline-only, the fix is to move to a signed-in shell OR ask the
+      // user — never silently drop large files.
+      const replug = eid
+        ? `npx -y @cloudgrid-io/cli plug --existing ${eid}${gridSlug ? ` --grid ${gridSlug}` : ""} --verbose`
+        : "npx -y @cloudgrid-io/cli plug";
       cliSteer =
-        "For a multi-file app the local CLI is more reliable — it reads from disk, so lockfiles and binaries can't truncate the way inline copying can. " +
-        (eid
-          ? `If you have the folder: \`cd <app> && npx -y @cloudgrid-io/cli plug\`. If not, pick it up first: \`npx -y @cloudgrid-io/cli pickup ${gridSlug ? `${gridSlug}/` : ""}<slug> --force\` then \`cd <slug> && npx -y @cloudgrid-io/cli plug\`. Or re-plug directly: \`npx -y @cloudgrid-io/cli plug --existing ${eid}${gridSlug ? ` --grid ${gridSlug}` : ""} --verbose\`.`
-          : "Prefer `npx -y @cloudgrid-io/cli plug` from the app folder over inlining files.");
+        "Heads-up: this went in INLINE. For a multi-file app the disk-based CLI is more reliable (lockfiles/binaries can't truncate), but it must run where the CLI is already signed in — a terminal or Claude Code that has done `grid login` once. Do NOT try `grid login` inside a chat sandbox: its login poll is long-lived and the sandbox is ephemeral, so it won't stick. " +
+        `If you had to leave any files out to make this inline deploy safe, tell the user — offer the complete deploy from Claude Code or a terminal (\`${replug}\`), or confirm they accept the reduced version. Do not drop files silently.`;
     }
   }
 

package/src/tools/register.js

@@ -276,13 +276,17 @@ export function registerTools(server, ctx) {
         "If you need to edit a page but don't have its HTML, call grid_get_app_source first, then deploy with " +
         "target_entity_id. " +
         // Suggestion 1: steer multi-file runtime apps to the CLI up front — inline
-        // copying truncates large lockfiles/binaries and silently fails the build.
+        // copying truncates large lockfiles/binaries and silently fails the build —
+        // but only where the CLI is actually signed in (see the login caveat).
         "RELIABILITY: `html` and `artifact_files` are sent INLINE (copied through this call), which can " +
         "truncate large files (lockfiles, binaries) on a multi-file app. For a real framework (Next.js, etc.), " +
-        "a lockfile, or binary assets — and for re-plugging an existing runtime app — prefer the local CLI, " +
-        "which reads from disk: `npx -y @cloudgrid-io/cli plug` in the app folder (pick it up first with " +
-        "`npx -y @cloudgrid-io/cli pickup <grid>/<slug> --force` if you don't have it locally). Reserve inline " +
-        "for a single page or a few small text files. (CloudGrid calls this operation 'plug'.)",
+        "a lockfile, or binary assets — and for re-plugging an existing runtime app — the disk-based CLI is more " +
+        "reliable: `npx -y @cloudgrid-io/cli plug` in the app folder. BUT it only works where the CLI is already " +
+        "signed in — a terminal or Claude Code that ran `grid login` once. Do NOT attempt `grid login` inside a " +
+        "chat sandbox: its login is a long poll and the sandbox is ephemeral, so it will not complete. If you can " +
+        "only deploy inline here and would have to omit large files, do NOT drop them silently — tell the user " +
+        "and offer to run the full deploy from Claude Code or a terminal (same entity_id). Reserve inline for a " +
+        "single page or a few small text files. (CloudGrid calls this operation 'plug'.)",
       inputSchema: plugInputSchema,
       outputSchema: {
         entity_id: z.string().optional().describe("Globally unique — pass back as target_entity_id to re-plug."),