nexrall-code 0.5.83 → 0.5.84

package/dist/index.js

@@ -55882,6 +55882,12 @@ function stopRowCount() {
   rowCounter = null;
   return rows;
 }
+function addRowCount(text) {
+  if (!rowCounter)
+    return;
+  const columns = process.stdout.columns || 80;
+  rowCounter.rows += rowsOccupied(text, columns);
+}
 var NEX_LOGO = [
   "\u2588\u2588\u2588\u2557   \u2588\u2588\u2557\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2557\u2588\u2588\u2557  \u2588\u2588\u2557",
   "\u2588\u2588\u2588\u2588\u2557  \u2588\u2588\u2551\u2588\u2588\u2554\u2550\u2550\u2550\u2550\u255D\u255A\u2588\u2588\u2557\u2588\u2588\u2554\u255D",
@@ -65193,34 +65199,36 @@ function startInkTerminal() {
         }
       ),
       {
-        exitOnCtrlC: false,
-        // Opt into the Kitty keyboard protocol so `key.shift` is actually
-        // populated for Enter (see the Shift+Enter handling in useInput
-        // above) instead of always being false/undefined.
+        exitOnCtrlC: false
+        // `kittyKeyboard` is deliberately OMITTED — no option object at all,
+        // matching the real `claude` binary exactly (verified: capturing
+        // claude's raw startup bytes in a pty shows no `\x1b[>1u` enable
+        // sequence and no `\x1b[?u` query anywhere in its output; it relies
+        // purely on ordinary UTF-8 keystrokes). Ink's own opt-in check
+        // (`if (!this.options.kittyKeyboard) return;` in ink.js) then does
+        // nothing at all: no enable sequence is ever written to the terminal.
         //
-        // MUST be 'enabled', not 'auto'. 'auto' has Ink send a CSI `?u` query
-        // to the terminal and then listen on `stdin`'s 'data' event for the
-        // reply (see ink/build/ink.js confirmKittySupport). That listener
-        // races Ink's own input pipeline, which reads stdin via 'readable' +
-        // `.read()` (paused mode) for its normal keystroke handling — Node
-        // streams do not support mixing 'data' (flowing) and 'readable'
-        // (paused) consumers safely, and in practice the 'readable' consumer
-        // wins the terminal's query response. The reply itself (`\x1b[?1u`)
-        // then gets fed through Ink's normal key parser, which doesn't
-        // recognise it as any special key and inserts it as literal text —
-        // this is exactly the "[?1u" that appears in the input box right
-        // after Ink mounts (e.g. right after confirming the trust prompt).
+        // This used to be `{ mode: 'enabled', flags: [...] }`, to populate
+        // `key.shift` on Enter for Shift+Enter detection. That traded away
+        // more than the tradeoff docs here previously accounted for: the
+        // protocol doesn't just risk an inert unrecognised escape sequence on
+        // unsupporting terminals — on a REAL Mac Terminal.app with the
+        // system's built-in Vietnamese Telex input source active, enabling it
+        // broke typing accented characters entirely (reported: chào/việt
+        // could be typed in `claude` but not in `nex`, same machine, same
+        // input source, only the enable sequence differed between the two
+        // binaries — confirmed by pty-capturing both). The Kitty protocol
+        // shifts key delivery from "already-composed UTF-8 text" to
+        // raw keycodes, which is exactly the layer an IME's composition
+        // depends on; some terminals that don't fully implement the protocol
+        // still react to the enable sequence by changing how they hand off
+        // composed IME text, rather than silently ignoring it as intended.
         //
-        // 'enabled' skips the query/response dance entirely: Ink just writes
-        // the enable sequence once (`\x1b[>1u`) and never listens for a
-        // reply, so there is nothing to leak into the input box. Terminals
-        // that don't support the protocol silently ignore the unrecognised
-        // escape sequence (the same way they ignore bracketed-paste mode),
-        // so Shift+Enter still safely falls back to the '\' continuation
-        // there — this trades "verify support first" for "assume support,
-        // no-op if absent", which is safe here because the only visible
-        // effect of enabling on an unsupporting terminal is nothing at all.
-        kittyKeyboard: { mode: "enabled", flags: ["disambiguateEscapeCodes"] }
+        // Shift+Enter therefore no longer gets a distinguishable `key.shift`
+        // on any terminal — it always submits, same as plain Enter, exactly
+        // matching claude's own behavior. The existing "\" continuation for
+        // multi-line input (chat.ts) remains the way to enter a literal
+        // newline, unchanged.
       }
     );
   });
@@ -66020,8 +66028,10 @@ Set ${TRUST_ENV_VAR}=1 to confirm non-interactively, or run \`nex\` interactivel
       tips
     };
     if (interactive) {
-      getInkTerminal().print(renderBanner({ ...bannerInfo, columns: process.stdout.columns ?? 80 }), { isBanner: true });
+      const bannerCard = renderBanner({ ...bannerInfo, columns: process.stdout.columns ?? 80 });
+      getInkTerminal().print(bannerCard, { isBanner: true });
       getInkTerminal().setBannerRegenerator((columns) => renderBanner({ ...bannerInfo, columns }));
+      addRowCount(bannerCard);
     } else {
       console.log(renderBanner({ ...bannerInfo, columns: process.stdout.columns ?? 80 }));
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nexrall-code",
-  "version": "0.5.83",
+  "version": "0.5.84",
   "description": "Nexrall Code — AI coding assistant for your terminal (headless agent for scripts, CI and automation)",
   "keywords": [
     "ai",