@phnx-labs/agents-cli 1.22.120 → 1.22.121

package/dist/commands/sessions.test-fixture.d.ts

@@ -1,13 +1,4 @@
 import { describe } from 'vitest';
-/**
- * Shared fixture for the sessions.*.test.ts suite slices (RUSH-2819).
- *
- * sessions.test.ts was one 2,600-line file measured at 172s — the single
- * slowest file in CI, serializing an entire fork while every other selected
- * file finished. The suite is split into topical slices so vitest's per-file
- * fork parallelism can spread the subprocess-heavy tests across workers; the
- * helpers each slice shares live here.
- */
 export declare const describeLive: typeof describe.skip;
 export declare const repoRoot: string;
 export declare const cliEntry: string;

package/dist/commands/sessions.test-fixture.js

@@ -4,31 +4,14 @@ import * as path from 'path';
 import { spawnSync } from 'child_process';
 import { createRequire } from 'node:module';
 import { pathToFileURL } from 'node:url';
-/**
- * Shared fixture for the sessions.*.test.ts suite slices (RUSH-2819).
- *
- * sessions.test.ts was one 2,600-line file measured at 172s — the single
- * slowest file in CI, serializing an entire fork while every other selected
- * file finished. The suite is split into topical slices so vitest's per-file
- * fork parallelism can spread the subprocess-heavy tests across workers; the
- * helpers each slice shares live here.
- */
-// win32: Claude projects path joins absolute cwd with colons (RUSH-2215).
 export const describeLive = process.platform === 'win32' ? describe.skip : describe;
 export const repoRoot = process.cwd();
 export const cliEntry = path.join(repoRoot, 'src', 'index.ts');
-// Run the CLI as `node --import <tsx loader> src/index.ts`: spawning `node`
-// (always on PATH, no .cmd shell launcher) with the tsx ESM loader resolved to
-// an absolute file URL keeps tsx loadable regardless of the spawn cwd (which we
-// point at the project dir). Avoids both the Windows `tsx.cmd`-needs-a-shell
-// problem and shell:true arg-concatenation (which would split multi-word query
-// args like "prompt text").
 export const tsxLoaderUrl = pathToFileURL(createRequire(import.meta.url).resolve('tsx')).href;
 export function writeUpdateCache(tempHome) {
     const packageJson = JSON.parse(fs.readFileSync(path.join(repoRoot, 'package.json'), 'utf-8'));
     fs.mkdirSync(path.join(tempHome, '.agents', '.cache'), { recursive: true });
     fs.writeFileSync(path.join(tempHome, '.agents', '.cache', '.update-check'), JSON.stringify({ lastCheck: Date.now(), latestVersion: packageJson.version }), 'utf-8');
-    // ensureInitialized() checks for ~/.agents/.system/.git to confirm setup.
     fs.mkdirSync(path.join(tempHome, '.agents', '.system', '.git'), { recursive: true });
 }
 export function writeClaudeSession(tempHome, projectKey, sessionId, cwd, content, timestamp) {
@@ -162,19 +145,21 @@ exit 1
     fs.chmodSync(openclawBin, 0o755);
     return path.join(activeHome, 'sergey');
 }
+function pathWithoutPackageBins() {
+    return (process.env.PATH || '')
+        .split(path.delimiter)
+        .filter((dir) => !(path.basename(dir) === '.bin' && path.basename(path.dirname(dir)) === 'node_modules'))
+        .join(path.delimiter);
+}
 export function runAgents(args, cwd, home, envOverrides = {}) {
     return spawnSync('node', ['--import', tsxLoaderUrl, cliEntry, ...args], {
         cwd,
         env: {
             ...process.env,
             HOME: home,
-            // os.homedir() (used via homeDir() in discovery) reads USERPROFILE on
-            // Windows and ignores HOME, so set both to redirect the home to tempHome.
             USERPROFILE: home,
-            PATH: `${path.join(home, 'bin')}${path.delimiter}${process.env.PATH || ''}`,
-            // Some fixtures place files at $HOME/.agents/versions/<agent>/<ver>/ as
-            // legacy / synthetic state. The bootstrap-time migration would otherwise
-            // move those into ~/.agents-system/, breaking workspace-scoped lookups.
+            SESSIONS_BIN: '',
+            PATH: `${path.join(home, 'bin')}${path.delimiter}${pathWithoutPackageBins()}`,
             AGENTS_SKIP_MIGRATION: '1',
             NODE_NO_WARNINGS: '1',
             ...envOverrides,

package/dist/commands/setup-accounts.d.ts

@@ -1,9 +1,3 @@
-/**
- * `agents setup accounts` — mint a Claude setup-token so unattended usage/probe
- * is not stuck on "usage pending". Delegates to the same mint engine as the
- * mint step of `agents accounts add claude [name]` /
- * `agents accounts login claude#<name>`.
- */
 import type { Command } from 'commander';
 export declare function runAccountsSetupWizard(): Promise<void>;
 export declare function registerSetupAccountsCommand(setupCmd: Command): void;

package/dist/commands/setup-browser.d.ts

@@ -1,26 +1,3 @@
-/**
- * `agents setup browser` — get `agents browser` working on a fresh machine:
- * install the standalone `browser` CLI (@phnx-labs/browser-cli), let it detect
- * installed browsers and create machine-local profiles (`browser profiles seed`),
- * then pick this machine's default (`browser use`).
- *
- * The engine owns profile declarations and browser detection now (PHNX-4101), so
- * this wizard DELEGATES to it rather than crafting profiles itself. What stays
- * agents-cli's is the onboarding flow and the readiness check over the shared
- * `browser.profile` config key both CLIs read/write.
- *
- * Idempotent: `profiles seed` leaves existing profiles untouched, and `use`
- * re-points the device default.
- */
 import type { Command } from 'commander';
-/**
- * Interactive browser setup. Returns true if a default profile is configured
- * afterwards, false if none is / the user backed out. Non-interactively it only
- * RECOGNIZES an existing default — it never creates one (PHNX-3296), since
- * silently minting a logged-out profile on a headless box is the exact bug that
- * removed; a headless box gets its browser from the fleet hub. Never throws on
- * cancel — the `agents setup` hub relies on that.
- */
 export declare function runBrowserWizard(): Promise<boolean>;
-/** Register `agents setup browser` under the parent `setup` command. */
 export declare function registerSetupBrowserCommand(setupCmd: Command): void;

package/dist/commands/setup-browser.js

@@ -1,17 +1,3 @@
-/**
- * `agents setup browser` — get `agents browser` working on a fresh machine:
- * install the standalone `browser` CLI (@phnx-labs/browser-cli), let it detect
- * installed browsers and create machine-local profiles (`browser profiles seed`),
- * then pick this machine's default (`browser use`).
- *
- * The engine owns profile declarations and browser detection now (PHNX-4101), so
- * this wizard DELEGATES to it rather than crafting profiles itself. What stays
- * agents-cli's is the onboarding flow and the readiness check over the shared
- * `browser.profile` config key both CLIs read/write.
- *
- * Idempotent: `profiles seed` leaves existing profiles untouched, and `use`
- * re-points the device default.
- */
 import { openSetupTerminal } from './setup-terminal.js';
 import chalk from 'chalk';
 import { getConfigValue } from '../lib/device-config.js';
@@ -20,23 +6,13 @@ import { installSetupTool } from '../lib/setup-tool-install.js';
 import { refreshToolSetup } from '../lib/setup-tool-status.js';
 import { browserInstalled, runBrowser } from '../lib/browser-client.js';
 import { buildBrowserContext } from '../lib/browser/context.js';
-/** The device-local default profile, as both agents-cli and browser-cli see it. */
 function configuredDefaultProfile() {
     return getConfigValue('browser.profile').value || undefined;
 }
-/** Run one standalone `browser` verb, inheriting the terminal, and return its exit code. */
 async function runBrowserVerb(argv) {
     const { exitCode } = await runBrowser({ argv, context: await buildBrowserContext() });
     return exitCode;
 }
-/**
- * Interactive browser setup. Returns true if a default profile is configured
- * afterwards, false if none is / the user backed out. Non-interactively it only
- * RECOGNIZES an existing default — it never creates one (PHNX-3296), since
- * silently minting a logged-out profile on a headless box is the exact bug that
- * removed; a headless box gets its browser from the fleet hub. Never throws on
- * cancel — the `agents setup` hub relies on that.
- */
 export async function runBrowserWizard() {
     if (!isInteractiveTerminal()) {
         const existing = configuredDefaultProfile();
@@ -55,8 +31,6 @@ export async function runBrowserWizard() {
             return false;
         }
     }
-    // Let the engine detect installed browsers and create a machine-local profile
-    // for each (idempotent), then open its own picker to set this machine's default.
     const seedCode = await runBrowserVerb(['profiles', 'seed']);
     if (seedCode !== 0) {
         console.error(chalk.red('`browser profiles seed` failed — see the output above.'));
@@ -71,7 +45,6 @@ export async function runBrowserWizard() {
     printOnboardingNextStep(chosen);
     return true;
 }
-/** The one step we can't automate: the browser's first-run + your own sign-in. */
 function printOnboardingNextStep(name) {
     console.log(chalk.bold('\nOne manual step left:'));
     console.log('  ' +
@@ -79,7 +52,6 @@ function printOnboardingNextStep(name) {
         chalk.dim('   # finish the browser first-run + sign in to any sites you want automated'));
     console.log(chalk.dim(`  Then check it's ready:  agents browser profiles doctor ${name}`));
 }
-/** Register `agents setup browser` under the parent `setup` command. */
 export function registerSetupBrowserCommand(setupCmd) {
     setupCmd
         .command('browser')

package/dist/commands/setup-computer.d.ts

@@ -1,19 +1,3 @@
-/**
- * `agents setup computer` — guided setup for `agents computer` on macOS: fetch +
- * verify the signed helper, install it, then walk the user through the two TCC
- * permission grants (Accessibility + Screen Recording) by opening the exact
- * System Settings panes and polling until the grant lands.
- *
- * The plain `agents computer setup` / `start` commands remain for scripted use;
- * this wizard chains them with the permission hand-holding a fresh machine needs.
- * Idempotent: re-running re-installs the current helper and re-checks trust.
- */
 import type { Command } from 'commander';
-/**
- * Interactive computer setup. Returns true if the helper is installed and trust
- * is granted (or the user chose to finish later), false if unsupported/aborted.
- * Never throws on cancel — the `agents setup` hub relies on that.
- */
 export declare function runComputerWizard(): Promise<boolean>;
-/** Register `agents setup computer` under the parent `setup` command. */
 export declare function registerSetupComputerCommand(setupCmd: Command): void;

package/dist/commands/setup-computer.js

@@ -1,13 +1,3 @@
-/**
- * `agents setup computer` — guided setup for `agents computer` on macOS: fetch +
- * verify the signed helper, install it, then walk the user through the two TCC
- * permission grants (Accessibility + Screen Recording) by opening the exact
- * System Settings panes and polling until the grant lands.
- *
- * The plain `agents computer setup` / `start` commands remain for scripted use;
- * this wizard chains them with the permission hand-holding a fresh machine needs.
- * Idempotent: re-running re-installs the current helper and re-checks trust.
- */
 import { openSetupTerminal } from './setup-terminal.js';
 import os from 'node:os';
 import { execFileSync } from 'node:child_process';
@@ -20,20 +10,13 @@ import { refreshToolSetup } from '../lib/setup-tool-status.js';
 const ACCESSIBILITY_PANE = 'x-apple.systempreferences:com.apple.preference.security?Privacy_Accessibility';
 const SCREEN_PANE = 'x-apple.systempreferences:com.apple.preference.security?Privacy_ScreenCapture';
 const sleep = (ms) => new Promise((r) => setTimeout(r, ms));
-/** Open a System Settings Privacy pane (best-effort — never throws). */
 function openPane(pane) {
     try {
         execFileSync('/usr/bin/open', [pane], { stdio: 'ignore' });
     }
     catch {
-        // ignore — we print the manual path as a fallback
     }
 }
-/**
- * Interactive computer setup. Returns true if the helper is installed and trust
- * is granted (or the user chose to finish later), false if unsupported/aborted.
- * Never throws on cancel — the `agents setup` hub relies on that.
- */
 export async function runComputerWizard() {
     if (os.platform() !== 'darwin') {
         console.log(chalk.yellow('`agents setup computer` configures the macOS helper (local control).'));
@@ -56,7 +39,6 @@ export async function runComputerWizard() {
             return false;
         }
     }
-    // 1. Download + verify + install the signed, notarized helper.
     console.log(chalk.bold('Installing the Agents Computer helper...'));
     try {
         await installComputerHelperMacLocal();
@@ -65,7 +47,6 @@ export async function runComputerWizard() {
         console.error(chalk.red(`Install failed: ${err.message}`));
         return false;
     }
-    // 2. Activate the daemon so macOS can attribute the TCC grants to it.
     console.log(chalk.bold('\nStarting the helper...'));
     let trusted = false;
     try {
@@ -75,7 +56,6 @@ export async function runComputerWizard() {
         console.error(chalk.red(`Could not start the helper: ${err.message}`));
         return false;
     }
-    // 3. Guide the two permission grants if not already trusted.
     if (!trusted) {
         console.log(chalk.bold('\nGrant two permissions to "Agents Computer" (one-time):'));
         console.log('  1. ' + chalk.cyan('Accessibility') + chalk.dim('     — lets it click/type'));
@@ -85,7 +65,6 @@ export async function runComputerWizard() {
         if (isInteractiveTerminal()) {
             trusted = await pollForTrust();
         }
-        // Also nudge the Screen Recording pane so both are visible.
         openPane(SCREEN_PANE);
         if (!trusted) {
             console.log(chalk.yellow('\nAccessibility not granted yet.'));
@@ -97,8 +76,6 @@ export async function runComputerWizard() {
     if (trusted) {
         console.log(chalk.green('\nComputer control is ready.'));
     }
-    // 4. App allow-list guidance (deny-by-default) — always shown; it's the gate
-    // between "trusted" and "can actually drive an app".
     console.log(chalk.bold('\nWhitelist the apps the helper may drive (default is deny-all):'));
     console.log(chalk.dim('  Add a YAML under ~/.agents/permissions/groups/, e.g. computer.yaml:'));
     console.log(chalk.dim('    name: computer'));
@@ -108,10 +85,6 @@ export async function runComputerWizard() {
     console.log(chalk.dim('  Then reload: ') + chalk.cyan('agents computer reload'));
     return trusted;
 }
-/**
- * Poll the daemon's trust status while the user toggles the Accessibility
- * checkbox in System Settings. Bounded to ~2 minutes; the user can Ctrl+C.
- */
 async function pollForTrust() {
     const { default: ora } = await import('ora');
     const spinner = ora('Waiting for Accessibility to be granted (toggle the checkbox in System Settings)...').start();
@@ -132,7 +105,6 @@ async function pollForTrust() {
         return false;
     }
 }
-/** Register `agents setup computer` under the parent `setup` command. */
 export function registerSetupComputerCommand(setupCmd) {
     setupCmd
         .command('computer')

package/dist/commands/setup-fleet.d.ts

@@ -1,10 +1,3 @@
-/**
- * `agents setup fleet` — guided Tailscale device onboarding.
- *
- * This wizard is a front door over the existing fleet/device commands: sync
- * Tailscale into the registry, choose auth, render SSH config, test devices, and
- * optionally run the fleet updater without reimplementing those subcommands.
- */
 import type { Command } from 'commander';
 interface SetupFleetOptions {
     auth?: string;
@@ -16,6 +9,5 @@ interface SetupFleetOptions {
     fleetUpdate?: boolean;
 }
 export declare function runFleetSetupWizard(opts?: SetupFleetOptions): Promise<boolean>;
-/** Register `agents setup fleet` under the parent `setup` command. */
 export declare function registerSetupFleetCommand(setupCmd: Command): void;
 export {};

package/dist/commands/setup-fleet.js

@@ -1,10 +1,3 @@
-/**
- * `agents setup fleet` — guided Tailscale device onboarding.
- *
- * This wizard is a front door over the existing fleet/device commands: sync
- * Tailscale into the registry, choose auth, render SSH config, test devices, and
- * optionally run the fleet updater without reimplementing those subcommands.
- */
 import chalk from 'chalk';
 import { spawnSync } from 'node:child_process';
 import { getCliLaunch } from '../lib/cli-entry.js';
@@ -175,13 +168,9 @@ export async function runFleetSetupWizard(opts = {}) {
     if (choices.fleetUpdate)
         runAgentsSubcommand(['fleet', 'update']);
     printOnboardingSummary(names, choices.auth);
-    // With a fleet registered, the next wrong-machine trap is artifacts opening on
-    // some other box — offer to pin the interactive host (TTY-only, skippable,
-    // silent non-TTY and when already set).
     await maybePickInteractiveHost();
     return true;
 }
-/** Register `agents setup fleet` under the parent `setup` command. */
 export function registerSetupFleetCommand(setupCmd) {
     setupCmd
         .command('fleet')

package/dist/commands/setup-mine.d.ts

@@ -1,16 +1,2 @@
-/**
- * `agents setup mine` — interactive wizard to white-label the CLI under your own
- * name. Pick a name, choose which features to turn off, and get a personally-
- * named binary (e.g. `jack`) that runs every agents verb as yours. Delegates the
- * actual minting to `initBrand` (see mine.ts). Manage verbs (init/list/toggle/
- * remove) live under the same `setup mine` command.
- *
- * Idempotent: re-running for an existing brand offers to re-mint it.
- * Bare `agents setup mine` (no subcommand) runs the wizard.
- */
 import type { Command } from 'commander';
-/**
- * Register `agents setup mine` under the parent `setup` command.
- * Bare invocation runs the wizard; init/list/toggle/remove manage brands.
- */
 export declare function registerSetupMineCommand(setupCmd: Command): void;

package/dist/commands/setup-mine.js

@@ -1,23 +1,8 @@
-/**
- * `agents setup mine` — interactive wizard to white-label the CLI under your own
- * name. Pick a name, choose which features to turn off, and get a personally-
- * named binary (e.g. `jack`) that runs every agents verb as yours. Delegates the
- * actual minting to `initBrand` (see mine.ts). Manage verbs (init/list/toggle/
- * remove) live under the same `setup mine` command.
- *
- * Idempotent: re-running for an existing brand offers to re-mint it.
- * Bare `agents setup mine` (no subcommand) runs the wizard.
- */
 import chalk from 'chalk';
 import { initBrand, registerMineManageCommands } from './mine.js';
 import { validateBrandName, getBrandConfig } from '../lib/brand.js';
 import { isShimsInPath } from '../lib/installations/shims.js';
 import { isInteractiveTerminal, isPromptCancelled } from './utils.js';
-/**
- * Optional/heavier top-level commands a brand commonly turns off. Kept short so
- * the checkbox is scannable — anything can still be toggled later with
- * `agents setup mine toggle <name> --disable <cmd>`.
- */
 const DISABLEABLE_FEATURES = [
     { name: 'teams', hint: 'coordinate multiple agents on shared work' },
     { name: 'cloud', hint: 'dispatch agent tasks to the cloud' },
@@ -27,11 +12,6 @@ const DISABLEABLE_FEATURES = [
     { name: 'routines', hint: 'run agents on a cron schedule' },
     { name: 'monitors', hint: 'event-triggered watchers' },
 ];
-/**
- * Interactive white-label setup. Returns true when a brand exists afterward,
- * false if the user backed out. Never throws on cancel — the `agents setup` hub
- * relies on that.
- */
 async function runMineWizard() {
     if (!isInteractiveTerminal()) {
         console.log(chalk.dim('Non-interactive shell. Create a brand directly, e.g.:\n') +
@@ -47,7 +27,6 @@ async function runMineWizard() {
             return err ?? true;
         },
     })).trim();
-    // Existing brand → offer to re-mint rather than error out.
     let force = false;
     if (getBrandConfig(name)) {
         const again = await confirm({
@@ -85,10 +64,6 @@ function printNextSteps(name, pathWarning) {
         console.log(chalk.yellow(`\n  note: the shims dir isn't on your PATH yet — run 'agents setup' or open a new shell.`));
     }
 }
-/**
- * Register `agents setup mine` under the parent `setup` command.
- * Bare invocation runs the wizard; init/list/toggle/remove manage brands.
- */
 export function registerSetupMineCommand(setupCmd) {
     const mineCmd = setupCmd
         .command('mine')

package/dist/commands/setup-preferences.d.ts

@@ -1,55 +1,8 @@
-/**
- * Preferences onboarding — the guided path over the same device-config keys the
- * `agents devices …` commands write (lib/device-config.ts). Two questions, each
- * TTY-only, skippable, and absent non-interactively:
- *
- *   1. "Which machine do you sit at?"   → `interactive.host` (central config:)
- *   2. "Which browser should agents drive on THIS machine?"
- *                                       → `browser.profile` (device-local default)
- *
- * Shared by the bare `agents setup` flow (a short step after the capability
- * hub) and by `agents setup fleet` (interactive host after a successful sync).
- * Unset always keeps today's behavior — skipping is a real choice, not a
- * partial state.
- */
 import { type DeviceRegistry } from '../lib/devices/registry.js';
-/** Registered macOS device names, sorted — the interactive-host candidates. */
 export declare function macDeviceNames(reg: DeviceRegistry): string[];
-/**
- * The interactive-host picker's highlighted default: this machine when it is a
- * candidate (the common case — you run setup on the box you sit at), else the
- * first candidate. null when there are no candidates.
- */
 export declare function defaultInteractiveHostChoice(candidates: string[], self?: string): string | null;
-/**
- * Offer to set the interactive host when none is configured and the registry
- * has more than one macOS device. Returns true when a host was set. Silent
- * no-op non-TTY, when already set, or with fewer than two candidates (the
- * answer is obvious or absent).
- */
 export declare function maybePickInteractiveHost(): Promise<boolean>;
-/**
- * Offer to pin this machine's default browser profile to a chosen browser.
- * Only asked when there is nothing to preserve: no configured device default
- * AND no existing `default` profile (an existing profile is the user's earlier
- * choice — never re-pinned behind their back). The list is the installed
- * Chromium-family browsers plus a "None — this box uses the fleet hub" opt-out.
- *
- * This is the ONE place a default browser is chosen for a machine (PHNX-3296):
- * a bare `agents browser start` no longer auto-detects and mints one, so picking
- * here (or `agents browser use` / `agents setup browser` later) is how a box
- * gets a local default at all. Picking "None" leaves it to the fleet hub
- * (`browser.device`). Returns true when a profile was created and set as the
- * device default. Silent no-op non-TTY — a headless box relies on the hub.
- */
 export declare function maybePickBrowserProfile(deps?: {
-    /** Force interactivity in a test; defaults to a real TTY probe. */
     interactive?: boolean;
 }): Promise<boolean>;
-/**
- * The bare-`agents setup` preferences step: interactive host, then browser.
- * Runs AFTER the capability hub so it never delays the bootstrap. Never
- * throws — a prompt cancel or a failed pick ends the step quietly and lets
- * setup complete (the same semantics as the capability hub).
- */
 export declare function runPreferencesStep(): Promise<void>;

package/dist/commands/setup-preferences.js

@@ -1,17 +1,3 @@
-/**
- * Preferences onboarding — the guided path over the same device-config keys the
- * `agents devices …` commands write (lib/device-config.ts). Two questions, each
- * TTY-only, skippable, and absent non-interactively:
- *
- *   1. "Which machine do you sit at?"   → `interactive.host` (central config:)
- *   2. "Which browser should agents drive on THIS machine?"
- *                                       → `browser.profile` (device-local default)
- *
- * Shared by the bare `agents setup` flow (a short step after the capability
- * hub) and by `agents setup fleet` (interactive host after a successful sync).
- * Unset always keeps today's behavior — skipping is a real choice, not a
- * partial state.
- */
 import chalk from 'chalk';
 import { browserInstalled, runBrowser } from '../lib/browser-client.js';
 import { buildBrowserContext } from '../lib/browser/context.js';
@@ -20,29 +6,17 @@ import { loadDevices } from '../lib/devices/registry.js';
 import { machineId } from '../lib/machine-id.js';
 import { isInteractiveTerminal } from './utils.js';
 const SKIP = '__skip__';
-/** Registered macOS device names, sorted — the interactive-host candidates. */
 export function macDeviceNames(reg) {
     return Object.values(reg)
         .filter((d) => d.platform === 'macos')
         .map((d) => d.name)
         .sort();
 }
-/**
- * The interactive-host picker's highlighted default: this machine when it is a
- * candidate (the common case — you run setup on the box you sit at), else the
- * first candidate. null when there are no candidates.
- */
 export function defaultInteractiveHostChoice(candidates, self = machineId()) {
     if (candidates.length === 0)
         return null;
     return candidates.includes(self) ? self : candidates[0];
 }
-/**
- * Offer to set the interactive host when none is configured and the registry
- * has more than one macOS device. Returns true when a host was set. Silent
- * no-op non-TTY, when already set, or with fewer than two candidates (the
- * answer is obvious or absent).
- */
 export async function maybePickInteractiveHost() {
     if (!isInteractiveTerminal())
         return false;
@@ -67,34 +41,14 @@ export async function maybePickInteractiveHost() {
     console.log(chalk.green(`Interactive host: '${picked}'`) + chalk.dim(' — marked ★ interactive in `agents devices list`.'));
     return true;
 }
-/**
- * Offer to pin this machine's default browser profile to a chosen browser.
- * Only asked when there is nothing to preserve: no configured device default
- * AND no existing `default` profile (an existing profile is the user's earlier
- * choice — never re-pinned behind their back). The list is the installed
- * Chromium-family browsers plus a "None — this box uses the fleet hub" opt-out.
- *
- * This is the ONE place a default browser is chosen for a machine (PHNX-3296):
- * a bare `agents browser start` no longer auto-detects and mints one, so picking
- * here (or `agents browser use` / `agents setup browser` later) is how a box
- * gets a local default at all. Picking "None" leaves it to the fleet hub
- * (`browser.device`). Returns true when a profile was created and set as the
- * device default. Silent no-op non-TTY — a headless box relies on the hub.
- */
 export async function maybePickBrowserProfile(deps = {}) {
     const interactive = deps.interactive ?? isInteractiveTerminal();
     if (!interactive)
         return false;
-    // Already chosen (by an earlier setup, `agents browser use`, or browser-cli
-    // directly) — never re-pin behind the user's back.
     if (getConfigValue('browser.profile').value)
         return false;
-    // The engine owns detection and profile creation (PHNX-4101); it is optional,
-    // so skip the pick quietly when it is not installed rather than nagging.
     if (!browserInstalled())
         return false;
-    // Let the engine detect installed browsers and create a machine-local profile
-    // for each (idempotent), then open its own picker to set this machine's default.
     const context = await buildBrowserContext();
     const seed = await runBrowser({ argv: ['profiles', 'seed'], context });
     if (seed.exitCode !== 0)
@@ -107,12 +61,6 @@ export async function maybePickBrowserProfile(deps = {}) {
         chalk.dim(' — this machine\'s default (agents browser use to change).'));
     return true;
 }
-/**
- * The bare-`agents setup` preferences step: interactive host, then browser.
- * Runs AFTER the capability hub so it never delays the bootstrap. Never
- * throws — a prompt cancel or a failed pick ends the step quietly and lets
- * setup complete (the same semantics as the capability hub).
- */
 export async function runPreferencesStep() {
     if (!isInteractiveTerminal())
         return;
@@ -123,6 +71,5 @@ export async function runPreferencesStep() {
             console.log();
     }
     catch {
-        // Cancel (ctrl-c) or a picker failure — the step is optional; end it.
     }
 }

package/dist/commands/setup-secrets.d.ts

@@ -1,30 +1,8 @@
-/**
- * `agents setup secrets` — install the standalone `secrets` CLI if missing,
- * then hand off to its own `secrets migrate` onboarding (PHNX-3989).
- *
- * The engine lives in `@phnx-labs/secrets-cli`. agents-cli never rebundles it
- * (DIST-1). A missing binary is a routine install, not a fatal gap: try
- * `agents clis install secrets` (system `clis/secrets.yaml`) then a pinned
- * `npm i -g`. Users do not set extra env vars.
- */
 import type { Command } from 'commander';
-export declare const SECRETS_CLI_PACKAGE = "@phnx-labs/secrets-cli@0.1.5";
-export declare const INSTALL_HINT = "agents clis install secrets   # or: npm i -g @phnx-labs/secrets-cli@0.1.5";
+export declare const SECRETS_CLI_PACKAGE = "@phnx-labs/secrets-cli@0.1.8";
+export declare const INSTALL_HINT = "agents clis install secrets   # or: npm i -g @phnx-labs/secrets-cli@0.1.8";
 export declare function setupSecretsPrefsPath(): string;
-/** True when the standalone `secrets` executable resolves ($SECRETS_BIN or PATH). */
 export declare function isSecretsCliInstalled(): boolean;
-/**
- * Install the published secrets CLI. Prefers the host-CLI manifest
- * (`clis/secrets.yaml` in the system repo) so doctor/clis stay one path.
- * Falls back to a pinned npm global install. Returns whether `secrets` is
- * on PATH afterwards. Never writes an `agents secrets` shim.
- */
 export declare function installSecretsCli(): boolean;
-/**
- * Install the standalone if missing, then hand off to `secrets migrate`.
- * Returns whether setup is now complete (installed, and migrate exited 0
- * when it ran).
- */
 export declare function runSecretsSetupWizard(): Promise<boolean>;
-/** Register `agents setup secrets` under the parent `setup` command. */
 export declare function registerSetupSecretsCommand(setupCmd: Command): void;

package/dist/commands/setup-secrets.js

@@ -1,12 +1,3 @@
-/**
- * `agents setup secrets` — install the standalone `secrets` CLI if missing,
- * then hand off to its own `secrets migrate` onboarding (PHNX-3989).
- *
- * The engine lives in `@phnx-labs/secrets-cli`. agents-cli never rebundles it
- * (DIST-1). A missing binary is a routine install, not a fatal gap: try
- * `agents clis install secrets` (system `clis/secrets.yaml`) then a pinned
- * `npm i -g`. Users do not set extra env vars.
- */
 import { openSetupTerminal } from './setup-terminal.js';
 import chalk from 'chalk';
 import * as fs from 'fs';
@@ -18,14 +9,11 @@ import { installCli, resolveCliManifest } from '../lib/cli-resources.js';
 import { SECRETS_CLI_SPEC } from '../lib/secrets-cli.js';
 import { refreshToolSetup } from '../lib/setup-tool-status.js';
 import { execFileShellSpec } from '../lib/platform/exec.js';
-// Re-exported for back-compat; the canonical pin lives in `secrets-cli.ts` so a
-// version bump touches ONE place (PHNX-3989 consolidation).
 export const SECRETS_CLI_PACKAGE = SECRETS_CLI_SPEC;
 export const INSTALL_HINT = `agents clis install secrets   # or: npm i -g ${SECRETS_CLI_PACKAGE}`;
 export function setupSecretsPrefsPath() {
     return path.join(getHistoryDir(), 'setup', 'secrets.json');
 }
-/** True when the standalone `secrets` executable resolves ($SECRETS_BIN or PATH). */
 export function isSecretsCliInstalled() {
     try {
         resolveSecretsBin();
@@ -42,12 +30,6 @@ function recordSetupComplete() {
     fs.mkdirSync(path.dirname(file), { recursive: true, mode: 0o700 });
     fs.writeFileSync(file, JSON.stringify({ updatedAt: new Date().toISOString() }, null, 2) + '\n', { mode: 0o600 });
 }
-/**
- * Install the published secrets CLI. Prefers the host-CLI manifest
- * (`clis/secrets.yaml` in the system repo) so doctor/clis stay one path.
- * Falls back to a pinned npm global install. Returns whether `secrets` is
- * on PATH afterwards. Never writes an `agents secrets` shim.
- */
 export function installSecretsCli() {
     if (isSecretsCliInstalled())
         return true;
@@ -73,11 +55,6 @@ export function installSecretsCli() {
         return false;
     return isSecretsCliInstalled();
 }
-/**
- * Install the standalone if missing, then hand off to `secrets migrate`.
- * Returns whether setup is now complete (installed, and migrate exited 0
- * when it ran).
- */
 export async function runSecretsSetupWizard() {
     if (!isSecretsCliInstalled()) {
         if (!installSecretsCli()) {
@@ -95,7 +72,6 @@ export async function runSecretsSetupWizard() {
         recordSetupComplete();
     return ok;
 }
-/** Register `agents setup secrets` under the parent `setup` command. */
 export function registerSetupSecretsCommand(setupCmd) {
     setupCmd
         .command('secrets')