cli-setu 0.2.9 → 0.3.0

package/bin/setu.js

@@ -49,8 +49,16 @@ async function main() {
   if (isSubcommand) {
     switch (firstArg) {
       case 'pair': {
+        // Real product ask (PM report): a first-time user had to run
+        // `cli-setu pair` then separately `cli-setu` to actually start a
+        // session - two commands where one would do, and the phone had
+        // nothing to show (no session yet) right after pairing. Matches
+        // bare `cli-setu`'s own already-correct behavior below: pair (if
+        // needed), then immediately start watching THIS folder as a
+        // session, same single-step flow either way now.
         const { pair } = require('../src/pair');
         await pair(AUTH_SERVER, AUTH_SERVER_PUBLIC);
+        require('../src/supervisor');
         return;
       }
       case 'status': {
@@ -91,7 +99,7 @@ async function main() {
   const config = readConfig();
   if (!config || !config.deviceToken) {
     const { pair } = require('../src/pair');
-    await pair(AUTH_SERVER, AUTH_SERVER_PUBLIC, { standalone: false });
+    await pair(AUTH_SERVER, AUTH_SERVER_PUBLIC);
   }
   require('../src/supervisor');
 }
@@ -104,7 +112,8 @@ Usage:
   cli-setu --cli <name>       Same, but run a specific CLI inside the bridged
                           session instead of the default plain shell
                           (e.g. --cli claude, --cli codex)
-  cli-setu pair               Pair this computer with your phone, nothing else
+  cli-setu pair               Pair this computer with your phone, then watch
+                          this folder as a session (same as bare cli-setu)
   cli-setu status             Show pairing status and any sessions running now
   cli-setu stop               Stop every session running on this computer
   cli-setu stop <sessionId>   Stop just one session (see \`cli-setu status\`

package/package.json

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

@@ -8,7 +8,7 @@ const qrcode = require('qrcode-terminal');
 const { loadOrCreateConfig, writeConfig, hasKeypair } = require('./config');
 const { generateKeypair, publicKeyToBase64, privateKeyToBase64 } = require('./crypto');
 
-async function pair(authServer, authServerPublic, { standalone = true } = {}) {
+async function pair(authServer, authServerPublic) {
   const config = loadOrCreateConfig();
 
   // Section 1 E2E: generate this device's own keypair up front, before
@@ -125,20 +125,6 @@ async function pair(authServer, authServerPublic, { standalone = true } = {}) {
     }
   }
 
-  // Real gap found by testing (PM report): a first-time user had no clear
-  // next step after pairing succeeded - pairing a device and starting a
-  // real terminal session are deliberately separate commands (one laptop
-  // can run several sessions, switch CLIs across restarts, etc.), but
-  // nothing here ever told a first-time user that distinction, or what
-  // to actually type next. Only shown for an explicit, standalone
-  // `cli-setu pair` - bin/setu.js's own bare-`cli-setu` flow calls this
-  // function too (auto-pairing an unpaired machine before immediately
-  // starting a session right after), where this message would be
-  // immediately followed by the session actually starting anyway.
-  if (standalone) {
-    console.log('[cli-setu] Run `cli-setu` in a project folder to start your first session.');
-  }
-
   return config;
 }