cli-setu 0.2.2 → 0.2.4

package/bin/setu.js

@@ -60,7 +60,10 @@ async function main() {
       }
       case 'stop': {
         const { stop } = require('../src/stop');
-        await stop();
+        // args[1] (optional) - a specific sessionId to stop, copied from
+        // `cli-setu status`'s own output. Omitted stops every session on
+        // this computer, unchanged from before.
+        await stop(args[1]);
         return;
       }
       case 'unpair': {
@@ -103,7 +106,9 @@ Usage:
                           (e.g. --cli claude, --cli codex)
   cli-setu pair               Pair this computer with your phone, nothing else
   cli-setu status             Show pairing status and any sessions running now
-  cli-setu stop               Stop a running session
+  cli-setu stop               Stop every session running on this computer
+  cli-setu stop <sessionId>   Stop just one session (see \`cli-setu status\`
+                          for the exact id to use)
   cli-setu unpair             Unpair this computer (asks for confirmation)
   cli-setu --version, -v      Print the installed version
   cli-setu --update           Check for and install the latest version

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cli-setu",
-  "version": "0.2.2",
+  "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/stop.js

@@ -3,10 +3,15 @@
 // a supervisor was closing its terminal window (or Ctrl+C, which only
 // reaches the one you're actually looking at) - this reaches every
 // running session at once via the same PID files status.js reads.
+//
+// `cli-setu stop <sessionId>` (new) - real gap found by testing: running
+// several sessions at once (e.g. two different project folders) had no
+// way to stop just ONE of them without killing all the others too -
+// copy the exact sessionId from `cli-setu status`'s own output.
 const fs = require('fs');
 const { CONFIG_DIR } = require('./config');
 
-async function stop() {
+async function stop(targetSessionId) {
   let files;
   try {
     files = fs.readdirSync(CONFIG_DIR).filter((f) => f.startsWith('session.') && f.endsWith('.pid'));
@@ -20,6 +25,7 @@ async function stop() {
   }
 
   let stopped = 0;
+  let matchedTarget = false;
   for (const file of files) {
     const pidFile = `${CONFIG_DIR}/${file}`;
     let info;
@@ -28,6 +34,12 @@ async function stop() {
     } catch {
       continue;
     }
+
+    // Only act on the one session asked for, if a target was given - every
+    // other running session is left completely untouched.
+    if (targetSessionId && info.sessionId !== targetSessionId) continue;
+    if (targetSessionId) matchedTarget = true;
+
     try {
       // SIGINT (not SIGKILL) - the same signal Ctrl+C sends, so the
       // process's own handler (supervisor.js's process.on('SIGINT', ...))
@@ -43,6 +55,11 @@ async function stop() {
     }
   }
 
+  if (targetSessionId && !matchedTarget) {
+    console.log(`[cli-setu] No running session found with id "${targetSessionId}". Run \`cli-setu status\` to see what's running.`);
+    return;
+  }
+
   if (stopped === 0) {
     console.log('[cli-setu] Sessions were already stopped (stale state cleaned up).');
   }

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