@piperace/cli 1.5.18 → 1.5.20

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@piperace/cli",
-  "version": "1.5.18",
+  "version": "1.5.20",
   "description": "Piperace — the missing toolkit for localhost: public tunnels, trusted local HTTPS domains and traffic inspection, with an MCP server for AI agents. One binary, one command.",
   "main": "lib/index.js",
   "bin": {

package/scripts/install.js

@@ -347,17 +347,64 @@ function registerWithLaunchServices(dest) {
 module.exports = {
   installBinary,
   installMacTrayApp,
+  autostart,
   binaryName,
   finalBinaryPath,
   platformKey,
   BINARY_MAP
 };
 
+// autostart opens the Control Center once the install is done.
+//
+// The install used to end in silence: you copy one command from the front page,
+// it prints download progress, and then nothing happens. Everything piperace
+// does lives in that dashboard, so a dashboard you have to be separately told
+// to run is one most people never see. The front page already promises "the
+// dashboard opens by itself" — this is the line that makes that true.
+//
+// Only for a global install someone typed themselves. A project dependency
+// must never start a daemon during `npm ci`, and no build server wants a
+// browser window, so both are skipped outright rather than guessed at.
+// PIPERACE_NO_AUTOSTART=1 is the way out for anyone else.
+//
+// `ui` behaves the same for a first install and an upgrade: on macOS it stops
+// the previous instance, hands the stack to the menu-bar app and returns;
+// elsewhere it stays up in the background, which is why the child is detached
+// and unref'd — npm must not wait on it.
+function autostart() {
+  const bin = finalBinaryPath('cli');
+  if (!fs.existsSync(bin)) return;
+
+  // Under `sudo npm i -g` the child would inherit root, and piperace keeps its
+  // state in $HOME — one root-owned ~/.piperace and the user's own runs cannot
+  // read their own config afterwards. Print the command; let them type it.
+  const asRoot = typeof process.getuid === 'function' && process.getuid() === 0 && process.env.SUDO_USER;
+
+  const skip =
+    process.env.PIPERACE_NO_AUTOSTART === '1' ? 'PIPERACE_NO_AUTOSTART=1' :
+    process.env.CI ? 'CI is set' :
+    process.env.npm_config_global !== 'true' ? 'not a global install' :
+    asRoot ? 'installed with sudo' : null;
+  if (skip) {
+    console.log(`[piperace] Installed. Run \`piperace\` to open the dashboard (${skip}).`);
+    return;
+  }
+
+  try {
+    const { spawn } = require('child_process');
+    spawn(bin, ['ui'], { detached: true, stdio: 'ignore' }).unref();
+    console.log('[piperace] Opening the dashboard… (run `piperace` any time to get back to it)');
+  } catch (err) {
+    console.log(`[piperace] Installed, but could not start it (${err.message}). Run \`piperace\`.`);
+  }
+}
+
 // Fetch the CLI binary (and, on macOS, the menu-bar app) at install time.
 if (require.main === module) {
   // Never let a failure here break `npm install`; the launcher retries lazily.
   Promise.resolve()
     .then(() => installBinary('cli'))
     .then(() => installMacTrayApp())
+    .then(() => autostart())
     .catch((err) => console.error(`[piperace] install skipped: ${err.message}`));
 }