troxy-cli 1.29.6 → 1.29.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "troxy-cli",
-  "version": "1.29.6",
+  "version": "1.29.8",
   "description": "A secure control layer for AI agents: policies across payments, messages, logins, destructive actions, model usage, and secrets, all enforceable from the CLI",
   "homepage": "https://troxy.io",
   "bugs": {

package/src/init.js

@@ -9,6 +9,8 @@ import { INTERCEPTOR_PORT } from './daemon.js';
 import { ensureInterceptionCerts } from './tls-ca.js';
 import { enabledProviders, interceptHostsFor } from './providers.js';
 import { probePort } from './proxy.js';
+import { launchdUserDomain } from './launchd.js';
+import { reclaimOwnership } from './sudo-ownership.js';
 
 // Re-point every consumer of the API key (MCP client configs, the background service /
 // systemd env file / launchd plist, OpenClaw) at `key`. Shared by runInit and rotate-key
@@ -141,6 +143,19 @@ export async function reprovisionKeyConsumers(key, agentName, proxyOptIn = null)
     console.log(`  Background service  ✗  (${err.message})`);
     console.log('  You can start it manually with: troxy daemon &');
   }
+
+  // Sudo safety net, not part of the normal (unprivileged) flow's own
+  // correctness - see sudo-ownership.js's own docstring. A no-op unless
+  // this whole process is running elevated via sudo (e.g. `sudo troxy
+  // update`, the CLI's own suggested remedy for a permission-denied
+  // global npm install), in which case everything reprovisionKeyConsumers
+  // just wrote under ~/.troxy (config, TLS interception certs) and the
+  // LaunchAgent plist would otherwise be left root-owned - unreadable by
+  // the daemon, which always runs as the normal user.
+  reclaimOwnership([
+    path.join(os.homedir(), '.troxy'),
+    path.join(os.homedir(), 'Library/LaunchAgents/ai.troxy.mcp.plist'),
+  ]);
 }
 
 const AGENTS_START = '<!-- troxy:start -->';
@@ -467,8 +482,12 @@ WantedBy=multi-user.target
     // owner only. launchd runs as this same user and can still read it.
     fs.writeFileSync(plistPath, plist, { mode: 0o600 });
     fs.chmodSync(plistPath, 0o600);
-    try { execSync(`launchctl unload ${plistPath} 2>/dev/null`); } catch {}
-    execSync(`launchctl load ${plistPath}`);
+    // bootstrap/bootout with an explicit domain, not load/unload - see
+    // launchd.js's own docstring for why plain load/unload breaks when
+    // this whole process is running as root (e.g. `sudo troxy update`).
+    const domain = launchdUserDomain();
+    try { execSync(`launchctl bootout ${domain} ${plistPath} 2>/dev/null`); } catch {}
+    execSync(`launchctl bootstrap ${domain} ${plistPath}`);
 
   } else {
     throw new Error('Auto-start not supported on this platform. Start manually: troxy mcp &');

package/src/launchd.js

@@ -0,0 +1,44 @@
+// macOS launchd domain-target helper, shared by init.js's installService and
+// uninstall.js's removeService.
+//
+// Found live 2026-09-12: `sudo troxy update` - the CLI's own suggested
+// remedy for a permission-denied global npm install (see bin/troxy.js's
+// EACCES handling) - runs the whole re-provisioning flow, including the
+// LaunchAgent (re)install, as root. The old code called plain `launchctl
+// load <plist>` / `launchctl unload <plist>` regardless of who's actually
+// running it. launchctl's classic load/unload verbs infer the target
+// domain from the CALLING process's own identity - called as root, they
+// assume you mean a system-wide LaunchDaemon (/Library/LaunchDaemons), and
+// refuse a per-user LaunchAgent plist outright: "Expecting a LaunchDaemons
+// path since the command was run as root... Load failed: 5: Input/output
+// error". A LaunchAgent is inherently a per-user concept - there is no
+// version of this that's actually meant to run as root.
+//
+// The fix launchctl's own warning names is bootstrap/bootout, which take
+// an EXPLICIT target domain instead of inferring one from the caller's
+// identity - root can bootstrap a job into another user's domain by
+// design (this is the standard, supported way for a root-context script
+// to manage a per-user service), and a normal, unprivileged user can
+// bootstrap into their own domain the same way. Works correctly either
+// way, unlike load/unload.
+//
+// user/<uid>, not gui/<uid>: troxy's daemon needs no GUI/Aqua session, and
+// troxy explicitly targets "your laptop, a server, a VM" (see the CLI's
+// own README) - a server or VM may have no GUI login at all, where
+// gui/<uid> would fail outright. user/<uid> exists as soon as the user is
+// logged in at all, GUI or headless SSH-only alike.
+
+/**
+ * The launchd domain-target to bootstrap/bootout ai.troxy.mcp.plist into -
+ * correct whether or not the calling process itself is root.
+ *
+ * `env.SUDO_UID` is what `sudo` itself sets to the REAL invoking user, not
+ * the elevated one - `process.getuid()` is 0 (root) for the whole process
+ * once elevated, which is exactly the case this exists to handle. Falls
+ * back to `getuid()` for the normal, non-sudo case, where that call
+ * already returns the real, correct user.
+ */
+export function launchdUserDomain(env = process.env, getuid = () => process.getuid?.()) {
+  const uid = env.SUDO_UID || String(getuid() ?? '');
+  return `user/${uid}`;
+}

package/src/sudo-ownership.js

@@ -0,0 +1,81 @@
+// Found live 2026-09-12, a broader version of the incident launchd.js fixes
+// (same trigger, different subsystem): `sudo troxy update` - the CLI's own
+// suggested remedy for a permission-denied global npm install (see
+// bin/troxy.js's EACCES handling) - runs the WHOLE process as root. In this
+// user's sudo session $HOME was preserved (not reset to root's own home),
+// so every path resolved correctly to the real user's ~/.troxy - but every
+// file written there (most importantly the TLS interception certs
+// tls-ca.js generates, mode 0600/0700) was still created ROOT-OWNED,
+// because the writing PROCESS's effective UID was 0, regardless of which
+// directory it happened to be writing into.
+//
+// The daemon later runs as the normal user (by design - see
+// installService's own plist, which never sets a UserName key, so launchd
+// runs it as whoever loaded it) and cannot read 0600/0700 files it
+// doesn't own. Real, observed failure: the local TLS-intercepting proxy
+// silently failed to bind at all, and every Anthropic call configured to
+// route through it got a bare connection-refused - completely invisible
+// until someone went looking, because installService's own try/catch
+// only ever sees "the daemon started", never "the daemon can actually do
+// its job". The user's own fix was `sudo chown -R` back to themselves;
+// this reclaims that automatically instead of requiring it after the
+// fact.
+
+import fs from 'node:fs';
+import path from 'node:path';
+
+/**
+ * {uid, gid} of the user sudo invoked as - SUDO_UID/SUDO_GID are what sudo
+ * itself sets to the REAL invoking user, never the elevated (0/root) one
+ * process.getuid() reports once elevated. Returns null when this process
+ * isn't running elevated via sudo at all: a normal, unprivileged run (the
+ * overwhelmingly common case, where nothing here needs to do anything),
+ * or root running with no sudo wrapper and thus no real user on record to
+ * hand ownership back to - never guessed at.
+ */
+export function realUserIds(env = process.env, getuid = () => process.getuid?.()) {
+  if (getuid() !== 0) return null;
+  if (!env.SUDO_UID) return null;
+  const uid = Number(env.SUDO_UID);
+  const gid = Number(env.SUDO_GID ?? env.SUDO_UID);
+  if (!Number.isInteger(uid) || !Number.isInteger(gid)) return null;
+  return { uid, gid };
+}
+
+function _chownRecursive(target, uid, gid) {
+  let stat;
+  try {
+    stat = fs.lstatSync(target);
+  } catch {
+    return; // doesn't exist - nothing to reclaim
+  }
+  try { fs.chownSync(target, uid, gid); } catch { /* best-effort, see below */ }
+  if (stat.isDirectory()) {
+    let entries = [];
+    try { entries = fs.readdirSync(target); } catch { return; }
+    for (const entry of entries) _chownRecursive(path.join(target, entry), uid, gid);
+  }
+}
+
+/**
+ * Recursively reclaims ownership of every given path back to the real
+ * user, when (and only when) this process is running elevated via sudo -
+ * a complete no-op otherwise. Never throws: every failure mode here
+ * (a path that doesn't exist, a permission quirk on one file deep in a
+ * tree) is worth trying the next path over, never worth failing the
+ * command that already did its real job. This is purely defensive
+ * cleanup for the sudo case; it is never load-bearing for the normal,
+ * far more common unprivileged run.
+ */
+export function reclaimOwnership(paths, env = process.env, getuid = () => process.getuid?.()) {
+  const real = realUserIds(env, getuid);
+  if (!real) return;
+  for (const p of paths) {
+    try {
+      _chownRecursive(p, real.uid, real.gid);
+    } catch {
+      // Never let reclaiming ownership of one path stop another, or
+      // surface as a failure of whatever real operation just ran.
+    }
+  }
+}

package/src/tests/install-service.test.js

@@ -59,11 +59,14 @@ describe('installService: launchd log capture (source inspection)', () => {
   });
 
   it('creates the ~/.troxy log directory before the plist is loaded', () => {
+    // 'launchctl bootstrap', not 'launchctl load' - see launchd.test.js for
+    // why the verb changed (bootstrap/bootout with an explicit domain,
+    // needed so this doesn't break under `sudo troxy update`).
     const darwinIdx = initSrc.indexOf("platform === 'darwin'");
     const troxyDirIdx = initSrc.indexOf('const troxyDir', darwinIdx);
     const mkdirIdx = initSrc.indexOf('fs.mkdirSync(troxyDir', darwinIdx);
-    const loadIdx = initSrc.indexOf('launchctl load', darwinIdx);
+    const loadIdx = initSrc.indexOf('launchctl bootstrap', darwinIdx);
     assert.ok(troxyDirIdx !== -1 && mkdirIdx !== -1 && loadIdx !== -1);
-    assert.ok(mkdirIdx < loadIdx, 'the log directory must be created before launchctl load runs');
+    assert.ok(mkdirIdx < loadIdx, 'the log directory must be created before launchctl bootstrap runs');
   });
 });

package/src/tests/launchd.test.js

@@ -0,0 +1,70 @@
+// Found live 2026-09-12: `sudo troxy update` (the CLI's own suggested
+// remedy for a permission-denied global npm install) runs the whole
+// re-provisioning flow as root, including the LaunchAgent (re)install.
+// launchctl's classic load/unload verbs infer their target domain from the
+// CALLING process's own identity - called as root, they assume a system
+// LaunchDaemon and refuse a per-user LaunchAgent outright ("Expecting a
+// LaunchDaemons path... Load failed: 5: Input/output error"). See
+// launchd.js's own docstring for the full reasoning and the fix
+// (bootstrap/bootout with an explicit domain instead).
+
+import { describe, it } from 'node:test';
+import assert from 'node:assert/strict';
+import { readFileSync } from 'node:fs';
+import { fileURLToPath } from 'node:url';
+import { dirname, join } from 'node:path';
+
+import { launchdUserDomain } from '../launchd.js';
+
+const __dirname = dirname(fileURLToPath(import.meta.url));
+const initSrc = readFileSync(join(__dirname, '..', 'init.js'), 'utf8');
+const uninstallSrc = readFileSync(join(__dirname, '..', 'uninstall.js'), 'utf8');
+
+describe('launchdUserDomain', () => {
+  it('uses SUDO_UID when running under sudo, ignoring the elevated (root) uid', () => {
+    const domain = launchdUserDomain({ SUDO_UID: '501' }, () => 0);
+    assert.equal(domain, 'user/501');
+  });
+
+  it('falls back to the caller\'s own uid when not running under sudo', () => {
+    const domain = launchdUserDomain({}, () => 501);
+    assert.equal(domain, 'user/501');
+  });
+
+  it('prefers SUDO_UID even if somehow both are present', () => {
+    const domain = launchdUserDomain({ SUDO_UID: '501' }, () => 0);
+    assert.notEqual(domain, 'user/0');
+  });
+
+  it('never throws when getuid is unavailable (e.g. non-POSIX platform)', () => {
+    assert.doesNotThrow(() => launchdUserDomain({}, () => undefined));
+  });
+});
+
+describe('installService / removeService: bootstrap-not-load (source inspection)', () => {
+  it('init.js darwin branch uses bootstrap/bootout, not the old load/unload verbs', () => {
+    const darwinIdx = initSrc.indexOf("platform === 'darwin'");
+    assert.ok(darwinIdx !== -1, 'darwin branch not found');
+    const darwinBlock = initSrc.slice(darwinIdx, initSrc.indexOf('function mcpEntry'));
+    assert.match(darwinBlock, /launchctl bootstrap/);
+    assert.match(darwinBlock, /launchctl bootout/);
+    assert.doesNotMatch(darwinBlock, /launchctl load \$\{plistPath\}/);
+    assert.doesNotMatch(darwinBlock, /launchctl unload \$\{plistPath\}/);
+  });
+
+  it('init.js passes an explicit domain to both bootstrap and bootout', () => {
+    const darwinIdx = initSrc.indexOf("platform === 'darwin'");
+    const darwinBlock = initSrc.slice(darwinIdx, initSrc.indexOf('function mcpEntry'));
+    assert.match(darwinBlock, /launchdUserDomain\(\)/);
+    assert.match(darwinBlock, /launchctl bootstrap \$\{domain\}/);
+    assert.match(darwinBlock, /launchctl bootout \$\{domain\}/);
+  });
+
+  it('uninstall.js darwin branch uses bootout, not the old unload verb', () => {
+    const darwinIdx = uninstallSrc.indexOf("platform === 'darwin'");
+    assert.ok(darwinIdx !== -1, 'darwin branch not found in uninstall.js');
+    const darwinBlock = uninstallSrc.slice(darwinIdx, darwinIdx + 400);
+    assert.match(darwinBlock, /launchctl bootout \$\{launchdUserDomain\(\)\}/);
+    assert.doesNotMatch(darwinBlock, /launchctl unload \$\{plistPath\}/);
+  });
+});

package/src/tests/sudo-ownership.test.js

@@ -0,0 +1,104 @@
+// Found live 2026-09-12: `sudo troxy update` (the CLI's own suggested
+// remedy for a permission-denied global npm install) runs the whole
+// re-provisioning flow as root. Every file it wrote under ~/.troxy - most
+// importantly the TLS interception certs - was created root-owned even
+// though the path correctly resolved to the real user's home. The daemon
+// (always run as the normal user) couldn't read its own 0600/0700 cert
+// files afterward, and the local interceptor silently failed to bind -
+// every Anthropic call routed through it got connection-refused. See
+// sudo-ownership.js's own docstring for the full incident and fix.
+
+import { describe, it, beforeEach, afterEach } from 'node:test';
+import assert from 'node:assert/strict';
+import fs from 'node:fs';
+import os from 'node:os';
+import path from 'node:path';
+import { readFileSync } from 'node:fs';
+import { fileURLToPath } from 'node:url';
+import { dirname, join } from 'node:path';
+
+import { realUserIds, reclaimOwnership } from '../sudo-ownership.js';
+
+const __dirname = dirname(fileURLToPath(import.meta.url));
+const initSrc = readFileSync(join(__dirname, '..', 'init.js'), 'utf8');
+
+describe('realUserIds', () => {
+  it('returns the real uid/gid when running elevated via sudo', () => {
+    const ids = realUserIds({ SUDO_UID: '501', SUDO_GID: '20' }, () => 0);
+    assert.deepEqual(ids, { uid: 501, gid: 20 });
+  });
+
+  it('falls back to SUDO_UID for the gid when SUDO_GID is absent', () => {
+    const ids = realUserIds({ SUDO_UID: '501' }, () => 0);
+    assert.deepEqual(ids, { uid: 501, gid: 501 });
+  });
+
+  it('returns null when not running as root at all - nothing to reclaim', () => {
+    assert.equal(realUserIds({ SUDO_UID: '501' }, () => 501), null);
+  });
+
+  it('returns null when running as root with no sudo wrapper - no real user on record', () => {
+    assert.equal(realUserIds({}, () => 0), null);
+  });
+
+  it('never throws when getuid is unavailable', () => {
+    assert.doesNotThrow(() => realUserIds({}, () => undefined));
+  });
+});
+
+describe('reclaimOwnership', () => {
+  let dir;
+  beforeEach(() => { dir = fs.mkdtempSync(path.join(os.tmpdir(), 'troxy-reclaim-')); });
+  afterEach(() => { fs.rmSync(dir, { recursive: true, force: true }); });
+
+  it('is a complete no-op when not running elevated via sudo', () => {
+    const target = path.join(dir, 'file.txt');
+    fs.writeFileSync(target, 'x');
+    const before = fs.statSync(target);
+    assert.doesNotThrow(() => reclaimOwnership([target], {}, () => before.uid));
+    // Unchanged - never even attempts a chown outside the sudo case.
+    assert.equal(fs.statSync(target).uid, before.uid);
+  });
+
+  it('never throws for a path that does not exist', () => {
+    assert.doesNotThrow(() =>
+      reclaimOwnership([path.join(dir, 'nope')], { SUDO_UID: '501' }, () => 0));
+  });
+
+  it('never throws when chownSync itself would fail (e.g. no real permission in this test env)', () => {
+    // This test process is almost never actually root, so a real chown to
+    // an arbitrary uid will fail - the whole point is that reclaimOwnership
+    // swallows that rather than throwing, matching this file's "best-effort,
+    // never blocks the real operation" contract.
+    const target = path.join(dir, 'file.txt');
+    fs.writeFileSync(target, 'x');
+    assert.doesNotThrow(() =>
+      reclaimOwnership([target], { SUDO_UID: '501', SUDO_GID: '20' }, () => 0));
+  });
+
+  it('walks into a directory when given one, not just its top level', () => {
+    const sub = path.join(dir, 'sub');
+    fs.mkdirSync(sub);
+    fs.writeFileSync(path.join(sub, 'nested.txt'), 'x');
+    // Same "must not throw even though this test isn't really root" shape
+    // as above - the real assertion is that recursion happens at all,
+    // which a thrown error partway through would otherwise mask.
+    assert.doesNotThrow(() =>
+      reclaimOwnership([dir], { SUDO_UID: '501', SUDO_GID: '20' }, () => 0));
+  });
+});
+
+describe('reprovisionKeyConsumers: reclaims ownership after sudo (source inspection)', () => {
+  it('calls reclaimOwnership after installService, covering ~/.troxy and the LaunchAgent plist', () => {
+    const fnStart = initSrc.indexOf('export async function reprovisionKeyConsumers');
+    assert.ok(fnStart !== -1, 'reprovisionKeyConsumers not found');
+    const installIdx = initSrc.indexOf('installService(key, agentName)', fnStart);
+    const reclaimIdx = initSrc.indexOf('reclaimOwnership(', fnStart);
+    assert.ok(installIdx !== -1 && reclaimIdx !== -1);
+    assert.ok(reclaimIdx > installIdx,
+      'ownership must be reclaimed after installService has written the plist, not before');
+    const fnBody = initSrc.slice(fnStart, reclaimIdx + 400);
+    assert.match(fnBody, /\.troxy/);
+    assert.match(fnBody, /LaunchAgents\/ai\.troxy\.mcp\.plist/);
+  });
+});

package/src/uninstall.js

@@ -10,6 +10,7 @@ import {
   unpatchClaudeCodeConfig, unpatchClaudeCodeHooks,
   unpatchClaudeCodeProxy, unpatchClaudeCodeInterception,
 } from './init.js';
+import { launchdUserDomain } from './launchd.js';
 
 const MCP_CLIENTS = [
   {
@@ -57,7 +58,9 @@ function removeService() {
   } else if (platform === 'darwin') {
     const plistPath = path.join(os.homedir(), 'Library/LaunchAgents/ai.troxy.mcp.plist');
     if (fs.existsSync(plistPath)) {
-      try { execSync(`launchctl unload ${plistPath} 2>/dev/null`); } catch {}
+      // bootout with an explicit domain, not unload - see launchd.js's
+      // docstring for why plain unload breaks under `sudo troxy uninstall`.
+      try { execSync(`launchctl bootout ${launchdUserDomain()} ${plistPath} 2>/dev/null`); } catch {}
       fs.unlinkSync(plistPath);
     }
     return true;