cli-setu 0.2.3 → 0.2.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cli-setu",
-  "version": "0.2.3",
+  "version": "0.2.4",
   "description": "Bridge your terminal to your phone — run and approve Claude Code, Codex CLI and other AI coding agents from anywhere.",
   "type": "commonjs",
   "bin": {

package/src/supervisor.js

@@ -545,12 +545,24 @@ function flushOutputBuffer() {
   // Still serialized against any send already in flight, so batches
   // themselves can never arrive out of order relative to each other.
   sendInFlight = sendInFlight.then(async () => {
+    // TEMPORARY diagnostic (remove once the real lag source is found):
+    // measures the full fetch() round trip to the Backend, isolating "is
+    // the laptop's own network connection to the Backend slow" from
+    // Azure's broadcast time (measured separately, server-side, in
+    // auth-server.js's /relay/terminal-output handler) and from this
+    // batch's own BATCH_WINDOW_MS wait (not included here - that delay is
+    // intentional, not a bug).
+    const sendStart = Date.now();
     try {
       await fetch(`${AUTH_SERVER}/relay/terminal-output`, {
         method: 'POST',
         headers: { 'Content-Type': 'application/json', Authorization: `Bearer ${deviceToken}` },
         body: JSON.stringify({ sessionId: SESSION_ID, seq: ++outputSeq, data: batch }),
       });
+      const sendMs = Date.now() - sendStart;
+      if (sendMs > 150) {
+        log(`[perf] terminal-output POST took ${sendMs}ms (bytes=${batch.length})`);
+      }
     } catch (err) {
       // A dropped terminal.output batch isn't fatal the way a dropped
       // confirmation would be - the next batch (or a fresh session.attach