@tiens.nguyen/gu-cli 1.0.756 → 1.0.757

package/cli-token.mjs

@@ -307,6 +307,14 @@ export function barNotice({ token, publicKeyB64, mode, now = new Date(), attempt
     if (age <= STALE_AFTER_DAYS * 86_400_000) return null;
   } else if (mode === "client" && !attempted) {
     return null; // Client mode fetches one by itself; do not complain before it has tried.
+  } else if (mode === "expert") {
+    // NO TOKEN on a Client Expert machine (#292): not "old" — there is none — and not said twice.
+    // Startup already prints the linking steps, and the first turn asks for the token in place, so
+    // the bar repeating it was the same message in two places (reported with a screenshot).
+    return null;
+  } else {
+    // Hosted client, its automatic fetch has failed: the bar is the only place this is said.
+    return { kind: "missing", urgent: false, text: "gu isn't signed in · run gu login" };
   }
 
   // ROUTINE, so not an alarm (#292): a token getting old only means updates will stop one day.

package/gu-repl.mjs

@@ -9208,9 +9208,15 @@ async function localScaffoldState() {
 /** Print the startup scaffold line — deferred while a turn owns the transcript. */
 function announceScaffold() {
   if (!scaffoldNotice || following) return;
-  const { kind, text } = scaffoldNotice;
+  const { kind, text, steps } = scaffoldNotice;
   scaffoldNotice = null;
-  console.log(GUTTER + (kind === "ok" ? accent("✓ " + text) : kind === "warn" ? yellow("⚠ " + text) : red("✗ " + text)));
+  if (kind === "link") {
+    // A setup step, said calmly (#292): the headline, then the steps on their own lines.
+    console.log(GUTTER + yellow("! " + text));
+    for (const s of steps ?? []) console.log(GUTTER + "  " + dim(s));
+  } else {
+    console.log(GUTTER + (kind === "ok" ? accent("✓ " + text) : kind === "warn" ? yellow("⚠ " + text) : red("✗ " + text)));
+  }
   if (barPinned()) paintBar();
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tiens.nguyen/gu-cli",
-  "version": "1.0.756",
+  "version": "1.0.757",
   "description": "Gu CLI — the gu terminal plus the local worker that runs agent / OCR / PDF / embedding jobs on your Mac (Ollama / MLX / OpenAI-compatible).",
   "type": "module",
   "license": "MIT",

package/terminal-layout.mjs

@@ -1890,6 +1890,22 @@ export function scaffoldStartupNotice({ local = null, refresh = null, private: p
   }
   if (refresh.ok) return { kind: "ok", text: `scaffold fetched from the gu service (v${refresh.version})` };
   const why = String(refresh.error ?? "unknown error").replace(/\.$/, "");
+  // NOT LINKED YET (#292): the one "error" a new Client Expert machine always shows, and it is a
+  // setup step, not a failure — gu asks for the token before the first turn anyway. It used to be
+  // one red sentence ("× scaffold: … Please run `gu token` — copy … then: gu token …") wrapping
+  // mid-word across three rows; now a calm headline and two numbered steps. The account address is
+  // taken from the API's own text, so it follows the site the API was set up for.
+  if (/isn't linked to your gu account/i.test(why)) {
+    const url = (/(https?:\/\/[^\s)]+\/account)/.exec(why)?.[1] ?? "https://gu.getmarsic.cc/account").replace(/^https?:\/\//, "");
+    return {
+      kind: "link",
+      text: "This computer isn't linked to your gu account yet.",
+      steps: [
+        `1. Copy your gu CLI token from ${url}`,
+        "2. Run: gu token <your token>   (or just ask something — gu will ask for it)",
+      ],
+    };
+  }
   return refresh.kept !== undefined
     ? { kind: "warn", text: `scaffold: couldn't fetch — ${why}. Still using v${refresh.kept}.` }
     : { kind: "err", text: `scaffold: ${why}.` };