mstro-app 0.2.0 → 0.3.1

package/PRIVACY.md

@@ -0,0 +1,126 @@
+# Mstro Privacy Policy
+
+**Effective Date:** February 2026
+
+## Overview
+
+Mstro, Inc. ("we", "us", "our") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and safeguard information when you use the Mstro CLI and related services.
+
+## Information We Collect
+
+### 1. Account Information
+When you create an account, we collect:
+- Email address
+- Name (optional)
+- Device identifiers (for authentication)
+
+### 2. Telemetry Data (Anonymous)
+By default, Mstro collects anonymous telemetry to improve the software:
+
+**Error Reporting (via Sentry):**
+- Stack traces and error messages
+- Mstro version and environment
+- Operating system and architecture
+- Node.js version
+
+**Usage Analytics (via PostHog):**
+- Feature usage patterns
+- Session duration
+- Command frequency
+
+**What we DO NOT collect:**
+- File contents or source code
+- API keys or credentials
+- Personal identifying information in error reports
+- IP addresses (stripped before storage)
+
+### 3. Session Data
+When using mstro.app:
+- Orchestra configurations
+- Session metadata
+- Connection timestamps
+
+## How to Opt Out of Telemetry
+
+You can disable all telemetry at any time:
+
+```bash
+mstro telemetry off
+
+# Or via environment variable
+export MSTRO_TELEMETRY=0
+```
+
+When telemetry is disabled:
+- No error reports are sent to Sentry
+- No usage analytics are sent to PostHog
+- Core functionality remains unchanged
+
+## How We Use Your Information
+
+We use collected information to:
+- Provide and maintain the Mstro service
+- Identify and fix bugs and crashes
+- Improve software performance and features
+- Communicate service updates and changes
+- Ensure security and prevent abuse
+
+## Data Sharing
+
+We do not sell your personal information. We may share data with:
+
+- **Service Providers:** Third-party services that help operate Mstro (e.g., Sentry for error tracking, PostHog for analytics)
+- **Legal Requirements:** When required by law or to protect our rights
+- **Business Transfers:** In connection with a merger or acquisition
+
+## Data Retention
+
+- **Account Data:** Retained while your account is active
+- **Telemetry Data:** Retained for up to 90 days
+- **Error Reports:** Retained for up to 30 days
+
+## Data Security
+
+We implement appropriate security measures including:
+- Encryption in transit (TLS/HTTPS)
+- Secure credential storage (chmod 600)
+- Regular security audits
+- Minimal data collection principles
+
+## Your Rights
+
+Depending on your jurisdiction, you may have rights to:
+- Access your personal data
+- Correct inaccurate data
+- Delete your data
+- Export your data
+- Opt out of data collection
+
+To exercise these rights, contact us at the information below.
+
+## Children's Privacy
+
+Mstro is not intended for users under 13 years of age. We do not knowingly collect information from children.
+
+## International Users
+
+Mstro is operated from the United States. By using the service, you consent to the transfer of your information to the United States.
+
+## Changes to This Policy
+
+We may update this Privacy Policy periodically. We will notify users of significant changes through the CLI or our website.
+
+## Open Source
+
+Mstro CLI is open source under the MIT License. You can review the code at:
+https://github.com/mstro-app/mstro
+
+## Contact Us
+
+For privacy-related questions or concerns:
+- Website: https://mstro.app
+- GitHub: https://github.com/mstro-app/mstro/issues
+
+---
+
+Copyright (c) 2025-present Mstro, Inc. All rights reserved.

package/README.md

@@ -1,10 +1,8 @@
 # mstro
 
-Luxurious remote workspace for [Claude Code](https://docs.anthropic.com/en/docs/claude-code). Run AI-powered coding sessions from any browser while Claude executes locally on any of your machines.
+Run [Claude Code](https://docs.anthropic.com/en/docs/claude-code) from any browser. The CLI runs locally on your machine and streams live sessions to [mstro.app](https://mstro.app) via a secure WebSocket relay.
 
-**mstro** is the CLI client for [mstro.app](https://mstro.app). It runs on your machine (laptop, cloud VM, CI server) and connects to the mstro.app web interface via a secure relay. You write prompts in the browser, Claude Code runs in your terminal.
-
-**Get started at [mstro.app](https://mstro.app)** — create an account, then install this CLI to connect your machine.
+**mstro** runs on your laptop, cloud VM, or CI server and connects to the mstro.app web interface. You write prompts in the browser, Claude Code runs in your terminal.
 
 ## How It Works
 
@@ -14,7 +12,7 @@ Browser (mstro.app)  <--WebSocket-->  Platform Server (relay)  <--WebSocket-->
                                                                       Claude Code CLI
 ```
 
-1. `mstro` starts a local server and connects to the mstro.app platform server
+1. `mstro` starts a local server and connects to the mstro.app platform
 2. You open [mstro.app](https://mstro.app) in any browser and see your connected machine
 3. Prompts you send in the browser are relayed to your machine
 4. Claude Code runs locally with full access to your project files
@@ -33,19 +31,25 @@ Requires [Claude Code](https://docs.anthropic.com/en/docs/claude-code) installed
 ## Quick Start
 
 ```bash
-mstro login              # Authenticate this device with your mstro.app account
-mstro                    # Start mstro in your project directory
+mstro                    # Logs in automatically on first run, then starts the server
 ```
 
-On first run, mstro will offer to set up the **Security Bouncer** - a tool permission manager that protects against dangerous operations. Say yes.
+Or without installing globally:
 
-Then open [mstro.app](https://mstro.app) in your browser. Your machine appears as a connected "orchestra." Start prompting.
+```bash
+npx mstro-app            # Same thing — login + launch in one command
+```
 
-## Security Bouncer
+On first run, mstro will:
+1. Open your browser to authenticate with your mstro.app account
+2. Offer to set up the **Security Bouncer** — say yes
+3. Connect to the platform
 
-The Bouncer replaces the default human-in-the-loop approval model with an agent-in-the-loop approach. An AI reviewer is better suited to evaluate tool calls than a human — it has full context on what should and shouldn't run, responds in milliseconds instead of interrupting your flow, and frees you up to focus on higher-level work while Claude Code executes autonomously. The result is faster, safer workflows without the constant approval prompts. 
+Then open [mstro.app](https://mstro.app) in your browser. Your machine appears as a connected workspace. Start prompting.
 
-The bouncer hook is installed globally at `~/.claude/hooks/bouncer.sh` and applies to all Claude Code sessions, but the level of protection depends on how Claude Code is running:
+## Security Bouncer
+
+The Bouncer automatically approves or blocks Claude Code tool calls so you don't have to. It installs as a hook at `~/.claude/hooks/bouncer.sh` and applies to all Claude Code sessions.
 
 **Mstro sessions (headless)** get the full 2-layer system:
 
@@ -64,22 +68,19 @@ The bouncer is set up automatically on first run. To reconfigure or install manu
 mstro configure-hooks
 ```
 
-This installs a hook at `~/.claude/hooks/bouncer.sh` and registers it in `~/.claude/settings.json`.
-
-Set `BOUNCER_USE_AI=false` to disable the AI analysis layer (pattern matching only).
-
 ## CLI Reference
 
 ### Commands
 
 ```bash
-mstro                       # Start the client server
-mstro login                 # Authenticate this device with mstro.app
+mstro                       # Start mstro (logs in automatically if needed)
+mstro login                 # Re-authenticate or switch accounts
 mstro logout                # Sign out
 mstro whoami                # Show current user and device info
 mstro status                # Show connection and auth status
 mstro setup-terminal        # Enable web terminal (compiles native module)
 mstro configure-hooks       # Install/reconfigure Security Bouncer
+mstro telemetry [on|off]    # Show/toggle anonymous telemetry
 ```
 
 ### Options
@@ -89,7 +90,6 @@ mstro configure-hooks       # Install/reconfigure Security Bouncer
 | `-p, --port <port>` | Start on a specific port (default: 4101, auto-increments if busy) |
 | `-w, --working-dir <dir>` | Set working directory |
 | `-v, --verbose` | Verbose output |
-| `--dev` | Connect to local platform at localhost:4102 |
 | `--version` | Show version |
 | `--help` | Show help |
 
@@ -98,11 +98,11 @@ mstro configure-hooks       # Install/reconfigure Security Bouncer
 Run multiple mstro instances for different projects. Each auto-selects an available port:
 
 ```
-$ mstro                           # Project A → port 4101
-$ mstro                           # Project B → port 4102
+$ mstro                           # Project A
+$ mstro                           # Project B
 ```
 
-Each instance appears as a separate orchestra in the web interface.
+Each instance appears as a separate workspace in the web interface.
 
 ## Environment Variables
 
@@ -110,6 +110,7 @@ Each instance appears as a separate orchestra in the web interface.
 |----------|-------------|
 | `PORT` | Override server port |
 | `BOUNCER_USE_AI` | Set to `false` to disable AI analysis layer |
+| `MSTRO_TELEMETRY` | Set to `0` to disable telemetry |
 | `PLATFORM_URL` | Platform server URL (default: `https://api.mstro.app`) |
 
 ## Config Files
@@ -129,7 +130,7 @@ mstro stores config in `~/.mstro/`:
 
 ### Optional: Web Terminal
 
-The web terminal feature requires a native module (`node-pty`). mstro works without it - you just won't have the terminal tab in the browser.
+The web terminal feature requires a native module (`node-pty`). mstro works without it — you just won't have the terminal tab in the browser.
 
 On first run, mstro will automatically attempt to compile `node-pty`. If your system has build tools installed, it just works. If not, mstro will let you know what to install:
 

package/bin/commands/login.js

@@ -236,10 +236,68 @@ async function pollForAuth(deviceCode, interval, platformUrl, maxAttempts = 180)
   throw new Error('Authorization timed out. Please try again.');
 }
 
+/**
+ * Deregister old device before force re-auth
+ */
+async function deregisterOldDevice(platformUrl) {
+  const existingCreds = getCredentials();
+  if (!existingCreds?.token) return;
+  try {
+    await fetch(`${platformUrl}/api/auth/device/deregister`, {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/json',
+        'Authorization': `Bearer ${existingCreds.token}`,
+      },
+    });
+  } catch {
+    // Deregister failed (e.g. network issue), force flag on request will handle it
+  }
+}
+
+/**
+ * Run the device code authorization flow. Throws on failure.
+ */
+async function runDeviceCodeFlow(clientId, platformUrl, forceReauth) {
+  const { deviceCode, userCode, verificationUrlComplete, interval } = await requestDeviceCode(clientId, platformUrl, forceReauth);
+
+  log(`Your authorization code: ${userCode}`, colors.bold);
+  log('');
+  log('Opening browser to complete login...', colors.dim);
+  log(` If browser doesn't open, visit: ${verificationUrlComplete}`, colors.dim);
+  log('');
+
+  openBrowser(verificationUrlComplete);
+
+  log('  Waiting for authorization', colors.dim);
+  process.stdout.write('  ');
+
+  const result = await pollForAuth(deviceCode, interval, platformUrl);
+
+  const credentials = {
+    token: result.accessToken,
+    userId: result.user.id,
+    email: result.user.email,
+    name: result.user.name,
+    clientId,
+    createdAt: new Date().toISOString(),
+  };
+
+  saveCredentials(credentials);
+  return result;
+}
+
 /**
  * Main login command
+ *
+ * @param {string[]} args - CLI arguments
+ * @param {object} options
+ * @param {boolean} options.inline - When true, called from startServer() auto-login:
+ *   skips "already logged in" check, omits post-login tips, and throws on failure
+ *   instead of calling process.exit(1).
  */
-export async function login(args = []) {
+export async function login(args = [], options = {}) {
+  const { inline = false } = options;
   const forceReauth = args.includes('--force') || args.includes('-f');
   const devMode = args.includes('--dev');
   const platformUrl = devMode ? DEV_PLATFORM_URL : PROD_PLATFORM_URL;
@@ -248,8 +306,8 @@ export async function login(args = []) {
     log(`[DEV MODE] Using ${platformUrl}\n`, colors.yellow);
   }
 
-  // Check if already logged in
-  if (isLoggedIn() && !forceReauth) {
+  // Check if already logged in (skip when called inline — caller already checked)
+  if (!inline && isLoggedIn() && !forceReauth) {
     const creds = getCredentials();
     log(`  Already logged in as ${creds.email}`, colors.green);
     log(`  Use "mstro logout" to sign out, or "mstro login --force" to re-authenticate.\n`, colors.dim);
@@ -258,64 +316,36 @@ export async function login(args = []) {
 
   const clientId = getClientId();
 
-  // If force re-auth and we have existing credentials, deregister the old device first
   if (forceReauth) {
-    const existingCreds = getCredentials();
-    if (existingCreds?.token) {
-      try {
-        await fetch(`${platformUrl}/api/auth/device/deregister`, {
-          method: 'POST',
-          headers: {
-            'Content-Type': 'application/json',
-            'Authorization': `Bearer ${existingCreds.token}`,
-          },
-        });
-      } catch {
-        // Deregister failed (e.g. network issue), force flag on request will handle it
-      }
-    }
+    await deregisterOldDevice(platformUrl);
   }
 
   log('Requesting authorization...', colors.dim);
 
   try {
-    // Step 1: Request device code
-    const { deviceCode, userCode, verificationUrlComplete, interval } = await requestDeviceCode(clientId, platformUrl, forceReauth);
-
-    // Step 2: Show code and open browser
-    log(`Your authorization code: ${userCode}`, colors.bold);
-    log('');
-    log('Opening browser to complete login...', colors.dim);
-    log(` If browser doesn't open, visit: ${verificationUrlComplete}`, colors.dim);
-    log('');
-
-    openBrowser(verificationUrlComplete);
-
-    // Step 3: Poll for result
-    log('  Waiting for authorization', colors.dim);
-    process.stdout.write('  ');
-
-    const result = await pollForAuth(deviceCode, interval, platformUrl);
-
-    // Step 4: Save credentials
-    const credentials = {
-      token: result.accessToken,
-      userId: result.user.id,
-      email: result.user.email,
-      name: result.user.name,
-      clientId,
-      createdAt: new Date().toISOString(),
-    };
-
-    saveCredentials(credentials);
+    const result = await runDeviceCodeFlow(clientId, platformUrl, forceReauth);
 
     log('');
     log('');
     log(`  Logged in as ${result.user.email}`, colors.bold + colors.green);
     log('');
-    log('  Run "mstro" to start a machine.', colors.cyan);
-    log('');
+
+    if (!inline) {
+      log('  Run "mstro" to start a machine.', colors.cyan);
+      log('');
+
+      // Check if node-pty is available, show tip if not
+      try {
+        await import('node-pty');
+      } catch {
+        log('  Tip: Terminal support requires native compilation.', colors.dim);
+        log('  Run "mstro setup-terminal" to enable web terminal.\n', colors.dim);
+      }
+    }
   } catch (err) {
+    if (inline) {
+      throw err;
+    }
     log('');
     log(`  Login failed: ${err.message}`, colors.red);
     log('');