@phnx-labs/agents-cli 1.22.40 → 1.22.42

package/dist/lib/browser/cdp.js

@@ -227,6 +227,10 @@ export function verifyBrowserIdentity(reported, expected, port, host = 'localhos
         // doesn't override the Chromium branding. Accept chrome here so attaching
         // to a Comet instance doesn't trip a false "identity mismatch".
         comet: ['comet', 'chrome'],
+        // Arc reports itself as plain "Chrome/<version>" in /json/version (verified
+        // live: Arc 1.15x → "Chrome/151"), so accept chrome to avoid a false
+        // identity mismatch when attaching to a real Arc.
+        arc: ['arc', 'chrome'],
         brave: ['brave', 'brave-browser', 'chrome'],
         // Windows/Chromium Edge reports its /json/version "Browser" field as
         // "Edg/<version>" (the `Edg` token, not `Edge`), which normalizeBrowserName

package/dist/lib/browser/chrome.js

@@ -23,6 +23,7 @@ const BROWSER_PATHS = {
         chromium: ['/Applications/Chromium.app/Contents/MacOS/Chromium'],
         brave: ['/Applications/Brave Browser.app/Contents/MacOS/Brave Browser'],
         edge: ['/Applications/Microsoft Edge.app/Contents/MacOS/Microsoft Edge'],
+        arc: ['/Applications/Arc.app/Contents/MacOS/Arc'],
         custom: [],
     },
     linux: {
@@ -31,6 +32,8 @@ const BROWSER_PATHS = {
         chromium: ['/usr/bin/chromium', '/usr/bin/chromium-browser', '/snap/bin/chromium'],
         brave: ['/usr/bin/brave-browser', '/usr/bin/brave'],
         edge: ['/usr/bin/microsoft-edge'],
+        // Arc has no Linux build (macOS + Windows only).
+        arc: [],
         custom: [],
     },
     win32: {
@@ -57,6 +60,9 @@ const BROWSER_PATHS = {
             `${WIN_PROGRAMFILES_X86}\\Microsoft\\Edge\\Application\\msedge.exe`,
             `${WIN_LOCALAPPDATA}\\Microsoft\\Edge\\Application\\msedge.exe`,
         ],
+        // Arc ships a Windows build, but its install path is not yet verified here;
+        // leave unlisted (undetected) rather than guess a path that false-positives.
+        arc: [],
         custom: [],
     },
 };
@@ -162,6 +168,9 @@ export function findBrowserPath(browserType, customBinary) {
     if (browserType === 'comet' && platform === 'linux') {
         throw new Error('Browser "comet" is not available on Linux (Comet ships macOS and Windows builds only). Use chrome, chromium, brave, or edge on this platform.');
     }
+    if (browserType === 'arc' && platform === 'linux') {
+        throw new Error('Browser "arc" is not available on Linux (Arc ships macOS and Windows builds only). Use chrome, chromium, brave, or edge on this platform.');
+    }
     throw new Error(`Browser "${browserType}" not found. Install it first.`);
 }
 // Per-platform Chromium-family priority list for "no --profile" auto-pick.
@@ -170,7 +179,9 @@ export function findBrowserPath(browserType, customBinary) {
 // way cdp.ts expects, so they'd need separate drivers.
 const DEFAULT_BROWSER_PRIORITY = {
     // macOS: Chrome leads (>70% of dev machines), then the rest of the family.
-    darwin: ['chrome', 'brave', 'edge', 'chromium', 'comet'],
+    // Arc is last: it's in maintenance mode and needs a blank tab to drive, so it
+    // shouldn't win auto-pick over a mainstream browser.
+    darwin: ['chrome', 'brave', 'edge', 'chromium', 'comet', 'arc'],
     // Linux: Chrome/Chromium first (apt/snap), then Brave/Edge if present.
     linux: ['chrome', 'chromium', 'brave', 'edge'],
     // Windows: Edge is preinstalled on every supported build, so it's the

package/dist/lib/browser/drivers/local.d.ts

@@ -1,8 +1,14 @@
 import { CDPClient } from '../cdp.js';
-import type { BrowserProfile } from '../types.js';
+import type { BrowserProfile, ConnectionKey } from '../types.js';
 export interface LocalConnection {
     cdp: CDPClient;
     port: number;
     pid: number;
 }
-export declare function connectLocal(endpoint: string, profile: BrowserProfile): Promise<LocalConnection>;
+export declare function connectLocal(endpoint: string, profile: BrowserProfile, 
+/**
+ * Runtime key (`<profile>@<endpoint>`) the launched browser's user-data-dir,
+ * pid, and port files are stored under. Separate from `profile.name`, which
+ * stays the bare user-facing name and appears only in messages (RUSH-2709).
+ */
+key: ConnectionKey): Promise<LocalConnection>;

package/dist/lib/browser/drivers/local.js

@@ -31,7 +31,13 @@ const TUNNEL_PROCESS_NAMES = new Set(['ssh', 'autossh', 'mosh-client', 'socat'])
 function isTunnelProcess(command) {
     return TUNNEL_PROCESS_NAMES.has(command.toLowerCase());
 }
-export async function connectLocal(endpoint, profile) {
+export async function connectLocal(endpoint, profile, 
+/**
+ * Runtime key (`<profile>@<endpoint>`) the launched browser's user-data-dir,
+ * pid, and port files are stored under. Separate from `profile.name`, which
+ * stays the bare user-facing name and appears only in messages (RUSH-2709).
+ */
+key) {
     const url = new URL(endpoint);
     if (url.protocol !== 'cdp:') {
         throw new Error(`Invalid local endpoint: ${endpoint}`);
@@ -91,7 +97,7 @@ export async function connectLocal(endpoint, profile) {
         const chromeOpts = { ...profile.chrome, viewport: profile.viewport };
         let launched;
         try {
-            launched = await launchBrowser(profile.name, profile.browser, newPort, chromeOpts, profile.secrets, profile.binary, profile.electron === true);
+            launched = await launchBrowser(key, profile.browser, newPort, chromeOpts, profile.secrets, profile.binary, profile.electron === true);
         }
         catch (launchErr) {
             const reason = launchErr instanceof Error ? launchErr.message : String(launchErr);

package/dist/lib/browser/drivers/ssh.d.ts

@@ -1,5 +1,5 @@
 import { CDPClient } from '../cdp.js';
-import type { BrowserProfile } from '../types.js';
+import type { BrowserProfile, ConnectionKey } from '../types.js';
 import { shellQuote } from '../../ssh-exec.js';
 export { shellQuote };
 export interface SSHConnection {
@@ -16,7 +16,13 @@ export interface SSHConnection {
  * strings differ (no `&` backgrounding, no `lsof`, `.exe` instead of `.app`).
  */
 export type RemoteOs = 'windows' | 'posix';
-export declare function connectSSH(endpoint: string, profile: BrowserProfile): Promise<SSHConnection>;
+export declare function connectSSH(endpoint: string, profile: BrowserProfile, 
+/**
+ * Runtime key (`<profile>@<endpoint>`) this connection is stored under. It
+ * keys the tunnel's runtime record; `profile.name` is the bare, user-facing
+ * name and appears only in messages (RUSH-2709).
+ */
+key: ConnectionKey): Promise<SSHConnection>;
 /**
  * Wrap a PowerShell script as a `-EncodedCommand` invocation. Base64 of the
  * UTF-16LE bytes is a single quote-free token, so it rides through Node spawn

package/dist/lib/browser/drivers/ssh.js

@@ -11,9 +11,15 @@ export { shellQuote };
 // The `ssh -L` tunnel spawn is shared with `agents computer --device`; it lives in
 // the single ssh-tunnel helper. Calling it with no options preserves this
 // driver's original foreground, stderr-captured behavior exactly.
-import { startSSHTunnel } from '../../ssh-tunnel.js';
+import { startSSHTunnel } from '../../computer/ssh-tunnel.js';
 import { encodePwshBase64 } from '../../pwsh.js';
-export async function connectSSH(endpoint, profile) {
+export async function connectSSH(endpoint, profile, 
+/**
+ * Runtime key (`<profile>@<endpoint>`) this connection is stored under. It
+ * keys the tunnel's runtime record; `profile.name` is the bare, user-facing
+ * name and appears only in messages (RUSH-2709).
+ */
+key) {
     const url = new URL(endpoint);
     if (url.protocol !== 'ssh:') {
         throw new Error(`Invalid SSH endpoint: ${endpoint}`);
@@ -88,7 +94,7 @@ export async function connectSSH(endpoint, profile) {
     // browser process.
     const tunnelPid = tunnel.pid ?? 0;
     if (tunnelPid > 0) {
-        writeProfileRuntime(profile.name, {
+        writeProfileRuntime(key, {
             pid: 0,
             port: localPort,
             command: 'ssh',
@@ -108,7 +114,7 @@ export async function connectSSH(endpoint, profile) {
             // stays synchronous, and killRemoteBrowser never rejects.
             killRemoteBrowser(user, host, remoteOs, remotePort).catch(() => { });
             tunnel.kill();
-            clearProfileRuntime(profile.name);
+            clearProfileRuntime(key);
         },
     };
 }
@@ -142,6 +148,7 @@ const POSIX_BROWSER_PATHS = {
     chromium: '/Applications/Chromium.app/Contents/MacOS/Chromium',
     brave: '/Applications/Brave Browser.app/Contents/MacOS/Brave Browser',
     edge: '/Applications/Microsoft Edge.app/Contents/MacOS/Microsoft Edge',
+    arc: '/Applications/Arc.app/Contents/MacOS/Arc',
 };
 // Windows App Paths registry keys per browser. CreateProcess (used by WMI
 // Win32_Process.Create) does not honor App Paths the way ShellExecute/`start`

package/dist/lib/browser/hygiene.d.ts

@@ -1,5 +1,5 @@
 import { type PidSessionEntry } from '../session/pid-registry.js';
-import type { ReapResult, Task } from './types.js';
+import { type ReapResult, type Task } from './types.js';
 /** Default idle window before an untouched task is reaped. */
 export declare const DEFAULT_IDLE_MS: number;
 /**

package/dist/lib/browser/hygiene.js

@@ -28,6 +28,7 @@
  */
 import { isPidAlive, isSessionIdLiveOnProcessTable } from '../session/active.js';
 import { listPidSessionEntries, sessionIdFromLivePid } from '../session/pid-registry.js';
+import { parseConnectionKey } from './types.js';
 /** Default idle window before an untouched task is reaped. */
 export const DEFAULT_IDLE_MS = 30 * 60_000;
 /**
@@ -131,7 +132,10 @@ export async function reapAbandonedTasks(service, opts = {}) {
             continue;
         }
         if (opts.dryRun) {
-            closed.push({ task: task.name, profile, reason });
+            // Report the BARE profile, exactly as the real run does below — `profile`
+            // here is the runtime key from `listTasks()`, and printing the two shapes
+            // in one column made `gc --dry-run` and `gc` disagree (RUSH-2709).
+            closed.push({ task: task.name, profile: parseConnectionKey(profile).profile, reason });
             continue;
         }
         const result = await service.stop(task.name);

package/dist/lib/browser/profiles.d.ts

@@ -1,6 +1,30 @@
 import type { BrowserProfile } from './types.js';
 export type { BrowserProfile } from './types.js';
-export declare const DEFAULT_BROWSER_PROFILE_NAME = "default";
+/**
+ * Name of the profile `ensureDefaultBrowserProfile` auto-detects and pins.
+ *
+ * It is `auto-chrome`, NOT `default`, since RUSH-2709: `default` used to be
+ * both this concrete profile AND the alias meaning "whatever profile the user
+ * configured", so `--profile default` landed on a literal auto-detected Chrome
+ * on one command and on the user's configured Comet on another. The alias now
+ * lives alone in {@link DEFAULT_PROFILE_ALIAS} and resolves in exactly one
+ * place ({@link resolveProfileRef}).
+ */
+export declare const DEFAULT_BROWSER_PROFILE_NAME = "auto-chrome";
+/**
+ * What older builds named the auto-detected profile. Still honored everywhere:
+ * a user whose machine already carries a `default` profile keeps using it (and
+ * its running browser + runtime dirs) rather than having a second one created
+ * beside it.
+ */
+export declare const LEGACY_DEFAULT_BROWSER_PROFILE_NAME = "default";
+/**
+ * The reserved ALIAS. `--profile default` (and a `browser.profile` config value
+ * of `default`) means "the configured default profile", not a profile called
+ * `default` — unless a profile literally named `default` exists, which still
+ * wins, so no existing config breaks.
+ */
+export declare const DEFAULT_PROFILE_ALIAS = "default";
 /**
  * Where a profile is stored, and therefore who sees it:
  *   - `local` — this machine's `devices/<machine>/agents.yaml` (`deviceBrowser`)
@@ -14,7 +38,7 @@ export interface ScopedBrowserProfile {
 }
 /**
  * The device-local configured default profile name (set via
- * `agents browser profiles set-default`), or undefined when unset. When set, it
+ * `agents browser use`), or undefined when unset. When set, it
  * is the profile `agents browser start` resolves to for BOTH the no-`--profile`
  * path and an explicit `--profile default`. Stored as this machine's
  * `browser.profile` device-config key (the per-device doc's `config:` block —
@@ -62,7 +86,7 @@ export declare function isProfileLaunchableHere(profile: BrowserProfile): boolea
  * set-default <name>`) when it names an existing profile that can launch here;
  * (2) an existing `default` profile that can launch here; (3) auto-pick the
  * first installed Chromium-family browser per the platform priority list in
- * chrome.ts (macOS: chrome > brave > edge > chromium > comet; Linux: chrome >
+ * chrome.ts (macOS: chrome > brave > edge > chromium > comet > arc; Linux: chrome >
  * chromium > brave > edge; Windows: edge > chrome > brave > comet) and pin a
  * `default` profile to it. Throws an actionable error if none of those binaries
  * are installed.
@@ -75,6 +99,55 @@ export declare function isProfileLaunchableHere(profile: BrowserProfile): boolea
  * that no longer exists, or can't launch here, warns and falls through — never a
  * hard fail.
  */
+/**
+ * The auto-detected profile this machine already carries, under either name —
+ * the current `auto-chrome` or the `default` an older build wrote. Callers that
+ * ask "is a default profile set up here?" MUST use this rather than probing one
+ * name, or a machine that predates the RUSH-2709 rename grows a second one.
+ */
+export declare function getAutoDetectedProfile(): Promise<BrowserProfile | null>;
+/**
+ * Resolve what a caller typed after `--profile` to a real, BARE profile name.
+ * Every command — stop, status, navigate, tab, use, and (through
+ * {@link resolveProfileRefForStart}) start — routes through this one function,
+ * which is the whole point: before RUSH-2709 only `start` honored the reserved
+ * `default` alias, so `--profile default` meant three different profiles across
+ * three commands.
+ *
+ * Order:
+ *   1. A profile that literally bears the given name always wins — including
+ *      one a user genuinely named `default`, which resolves to itself.
+ *   2. `default` (the alias) or no argument at all → the configured
+ *      `browser.profile` for this machine, if it names a profile that exists.
+ *   3. → the auto-detected profile ({@link DEFAULT_BROWSER_PROFILE_NAME}), or
+ *      its legacy `default`-named predecessor when that is what is on disk.
+ *   4. Otherwise the input is returned unchanged (so the caller reports its own
+ *      `Profile "x" not found`), or `undefined` when nothing was passed.
+ *
+ * It never creates a profile, never warns, and never checks whether the profile
+ * can launch HERE. That is deliberate: for most callers `--profile` is a FILTER
+ * (`status`, `tasks`, `navigate --task`), where an absent flag means "no filter"
+ * and rewriting or warning about the user's config would be wrong. Note the
+ * corollary at those call sites — pass a ref only when the user gave one; do not
+ * resolve `undefined` into a concrete profile, or an unscoped listing silently
+ * becomes a scoped one.
+ */
+export declare function resolveProfileRef(ref?: string): Promise<string | undefined>;
+/**
+ * `start`'s resolver. Same order as {@link resolveProfileRef} for an explicit
+ * name, but the IMPLICIT path (no `--profile`, or the bare `default` alias with
+ * no profile of that name) goes through {@link ensureDefaultBrowserProfile} —
+ * which additionally verifies the resolved default can launch on THIS machine,
+ * warns and falls through when it can't, and regenerates or creates one.
+ *
+ * `start` is the only command that launches a browser, so it is the only one
+ * that may do those things; routing a filter-only command through this would
+ * warn about, and rewrite, config the user never asked it to touch.
+ *
+ * Throws when no profile exists and no supported browser is installed —
+ * `ensureDefaultBrowserProfile`'s actionable "install one of …" error.
+ */
+export declare function resolveProfileRefForStart(ref?: string): Promise<string>;
 export declare function ensureDefaultBrowserProfile(): Promise<BrowserProfile>;
 /**
  * Compute the LOCAL port a profile will occupy at runtime:
@@ -133,7 +206,7 @@ export declare function padColumn(text: string, width: number): string;
  * Two things used to be called "default" in this listing with no way to tell
  * them apart (RUSH-2710): the profile literally NAMED `default` (the
  * auto-detected one), and whichever profile this machine resolves a bare
- * `agents browser start` to (`agents config set browser.profile <name>`). They
+ * `agents browser start` to (`agents browser use <name>`). They
  * are frequently different profiles. Now only the second is a marker — a `*` in
  * a leading column, explained by a legend line — so the name column carries just
  * the name and `default` in it always means the profile of that name.

package/dist/lib/browser/profiles.js

@@ -3,7 +3,31 @@ import { getBrowserRuntimeDir as getBrowserRuntimeDirRoot, readMeta, updateMeta,
 import { getConfigValue } from '../device-config.js';
 import { findBrowserPath, findFirstInstalledBrowser, isPortInUse } from './chrome.js';
 import { DEFAULT_VIEWPORT } from './devices.js';
-export const DEFAULT_BROWSER_PROFILE_NAME = 'default';
+/**
+ * Name of the profile `ensureDefaultBrowserProfile` auto-detects and pins.
+ *
+ * It is `auto-chrome`, NOT `default`, since RUSH-2709: `default` used to be
+ * both this concrete profile AND the alias meaning "whatever profile the user
+ * configured", so `--profile default` landed on a literal auto-detected Chrome
+ * on one command and on the user's configured Comet on another. The alias now
+ * lives alone in {@link DEFAULT_PROFILE_ALIAS} and resolves in exactly one
+ * place ({@link resolveProfileRef}).
+ */
+export const DEFAULT_BROWSER_PROFILE_NAME = 'auto-chrome';
+/**
+ * What older builds named the auto-detected profile. Still honored everywhere:
+ * a user whose machine already carries a `default` profile keeps using it (and
+ * its running browser + runtime dirs) rather than having a second one created
+ * beside it.
+ */
+export const LEGACY_DEFAULT_BROWSER_PROFILE_NAME = 'default';
+/**
+ * The reserved ALIAS. `--profile default` (and a `browser.profile` config value
+ * of `default`) means "the configured default profile", not a profile called
+ * `default` — unless a profile literally named `default` exists, which still
+ * wins, so no existing config breaks.
+ */
+export const DEFAULT_PROFILE_ALIAS = 'default';
 /**
  * True for a profile whose contents only make sense on THIS machine, so it must
  * live in the per-machine doc rather than the fleet-synced agents.yaml.
@@ -21,11 +45,11 @@ export const DEFAULT_BROWSER_PROFILE_NAME = 'default';
  * into central from being written back there by {@link updateProfile}.
  */
 function isMachineLocalProfile(name) {
-    return name === DEFAULT_BROWSER_PROFILE_NAME;
+    return name === DEFAULT_BROWSER_PROFILE_NAME || name === LEGACY_DEFAULT_BROWSER_PROFILE_NAME;
 }
 /**
  * The device-local configured default profile name (set via
- * `agents browser profiles set-default`), or undefined when unset. When set, it
+ * `agents browser use`), or undefined when unset. When set, it
  * is the profile `agents browser start` resolves to for BOTH the no-`--profile`
  * path and an explicit `--profile default`. Stored as this machine's
  * `browser.profile` device-config key (the per-device doc's `config:` block —
@@ -165,7 +189,7 @@ export function isProfileLaunchableHere(profile) {
  * set-default <name>`) when it names an existing profile that can launch here;
  * (2) an existing `default` profile that can launch here; (3) auto-pick the
  * first installed Chromium-family browser per the platform priority list in
- * chrome.ts (macOS: chrome > brave > edge > chromium > comet; Linux: chrome >
+ * chrome.ts (macOS: chrome > brave > edge > chromium > comet > arc; Linux: chrome >
  * chromium > brave > edge; Windows: edge > chrome > brave > comet) and pin a
  * `default` profile to it. Throws an actionable error if none of those binaries
  * are installed.
@@ -178,33 +202,118 @@ export function isProfileLaunchableHere(profile) {
  * that no longer exists, or can't launch here, warns and falls through — never a
  * hard fail.
  */
+/**
+ * The auto-detected profile this machine already carries, under either name —
+ * the current `auto-chrome` or the `default` an older build wrote. Callers that
+ * ask "is a default profile set up here?" MUST use this rather than probing one
+ * name, or a machine that predates the RUSH-2709 rename grows a second one.
+ */
+export async function getAutoDetectedProfile() {
+    return ((await getProfile(DEFAULT_BROWSER_PROFILE_NAME)) ??
+        (await getProfile(LEGACY_DEFAULT_BROWSER_PROFILE_NAME)));
+}
+/**
+ * Resolve what a caller typed after `--profile` to a real, BARE profile name.
+ * Every command — stop, status, navigate, tab, use, and (through
+ * {@link resolveProfileRefForStart}) start — routes through this one function,
+ * which is the whole point: before RUSH-2709 only `start` honored the reserved
+ * `default` alias, so `--profile default` meant three different profiles across
+ * three commands.
+ *
+ * Order:
+ *   1. A profile that literally bears the given name always wins — including
+ *      one a user genuinely named `default`, which resolves to itself.
+ *   2. `default` (the alias) or no argument at all → the configured
+ *      `browser.profile` for this machine, if it names a profile that exists.
+ *   3. → the auto-detected profile ({@link DEFAULT_BROWSER_PROFILE_NAME}), or
+ *      its legacy `default`-named predecessor when that is what is on disk.
+ *   4. Otherwise the input is returned unchanged (so the caller reports its own
+ *      `Profile "x" not found`), or `undefined` when nothing was passed.
+ *
+ * It never creates a profile, never warns, and never checks whether the profile
+ * can launch HERE. That is deliberate: for most callers `--profile` is a FILTER
+ * (`status`, `tasks`, `navigate --task`), where an absent flag means "no filter"
+ * and rewriting or warning about the user's config would be wrong. Note the
+ * corollary at those call sites — pass a ref only when the user gave one; do not
+ * resolve `undefined` into a concrete profile, or an unscoped listing silently
+ * becomes a scoped one.
+ */
+export async function resolveProfileRef(ref) {
+    if (ref && ref !== DEFAULT_PROFILE_ALIAS) {
+        return ref;
+    }
+    if (ref === DEFAULT_PROFILE_ALIAS && (await getProfile(ref))) {
+        // A profile the user literally named `default` outranks the alias.
+        return ref;
+    }
+    const configured = getConfiguredDefaultProfileName();
+    if (configured && configured !== DEFAULT_PROFILE_ALIAS && (await getProfile(configured))) {
+        return configured;
+    }
+    if (await getProfile(DEFAULT_BROWSER_PROFILE_NAME))
+        return DEFAULT_BROWSER_PROFILE_NAME;
+    if (await getProfile(LEGACY_DEFAULT_BROWSER_PROFILE_NAME)) {
+        return LEGACY_DEFAULT_BROWSER_PROFILE_NAME;
+    }
+    return ref;
+}
+/**
+ * `start`'s resolver. Same order as {@link resolveProfileRef} for an explicit
+ * name, but the IMPLICIT path (no `--profile`, or the bare `default` alias with
+ * no profile of that name) goes through {@link ensureDefaultBrowserProfile} —
+ * which additionally verifies the resolved default can launch on THIS machine,
+ * warns and falls through when it can't, and regenerates or creates one.
+ *
+ * `start` is the only command that launches a browser, so it is the only one
+ * that may do those things; routing a filter-only command through this would
+ * warn about, and rewrite, config the user never asked it to touch.
+ *
+ * Throws when no profile exists and no supported browser is installed —
+ * `ensureDefaultBrowserProfile`'s actionable "install one of …" error.
+ */
+export async function resolveProfileRefForStart(ref) {
+    if (ref && ref !== DEFAULT_PROFILE_ALIAS)
+        return ref;
+    // A profile the user literally named `default` still outranks the alias.
+    if (ref === DEFAULT_PROFILE_ALIAS && (await getProfile(ref)))
+        return ref;
+    return (await ensureDefaultBrowserProfile()).name;
+}
 export async function ensureDefaultBrowserProfile() {
     const configured = getConfiguredDefaultProfileName();
-    if (configured) {
+    if (configured && configured !== DEFAULT_PROFILE_ALIAS) {
         const chosen = await getProfile(configured);
         if (chosen && isProfileLaunchableHere(chosen))
             return chosen;
         console.warn(chosen
             ? `warning: configured default browser profile "${configured}" can't launch on this ` +
                 `machine (its browser/binary isn't installed here); falling back to auto-detect. ` +
-                `Fix with: agents browser profiles set-default <name>  (or --unset)`
+                `Fix with: agents browser use <name>  (or --unset)`
             : `warning: configured default browser profile "${configured}" no longer exists; ` +
-                `falling back to auto-detect. Fix with: agents browser profiles set-default <name>  (or --unset)`);
+                `falling back to auto-detect. Fix with: agents browser use <name>  (or --unset)`);
     }
-    const existing = await getProfile(DEFAULT_BROWSER_PROFILE_NAME);
+    // Prefer whichever auto-detected profile this machine already carries: the
+    // current `auto-chrome`, else the `default` an older build wrote. Reusing the
+    // legacy one is what keeps a currently-running browser (and its runtime dirs,
+    // keyed `default@endpoint-0`) attached after the rename.
+    const existing = (await getProfile(DEFAULT_BROWSER_PROFILE_NAME)) ??
+        (await getProfile(LEGACY_DEFAULT_BROWSER_PROFILE_NAME));
     if (existing && isProfileLaunchableHere(existing))
         return existing;
     const detected = findFirstInstalledBrowser();
     if (!detected) {
-        throw new Error('No supported browser found. Install one of: Chrome, Brave, Edge, Chromium, or Comet, ' +
+        throw new Error('No supported browser found. Install one of: Chrome, Brave, Edge, Chromium, Comet, or Arc, ' +
             'then re-run `agents browser start`. Or create a profile explicitly with ' +
-            '`agents browser profiles create <name> --browser <chrome|comet|chromium|brave|edge|custom>`. ' +
+            '`agents browser profiles create <name> --browser <chrome|comet|chromium|brave|edge|arc|custom>`. ' +
             'Note: Safari and Firefox are not supported — agents browser drives over the ' +
             'Chrome DevTools Protocol, which they don\'t implement.');
     }
     const freePort = await findFreeProfilePort();
     const profile = {
-        name: DEFAULT_BROWSER_PROFILE_NAME,
+        // Regenerate under the name that is already on disk when there is one, so a
+        // stale legacy `default` is repaired in place instead of leaving the user
+        // with two auto-detected profiles.
+        name: existing?.name ?? DEFAULT_BROWSER_PROFILE_NAME,
         description: `Auto-detected ${detected.browserType} profile`,
         browser: detected.browserType,
         binary: detected.binary,
@@ -431,7 +540,7 @@ export function padColumn(text, width) {
  * Two things used to be called "default" in this listing with no way to tell
  * them apart (RUSH-2710): the profile literally NAMED `default` (the
  * auto-detected one), and whichever profile this machine resolves a bare
- * `agents browser start` to (`agents config set browser.profile <name>`). They
+ * `agents browser start` to (`agents browser use <name>`). They
  * are frequently different profiles. Now only the second is a marker — a `*` in
  * a leading column, explained by a legend line — so the name column carries just
  * the name and `default` in it always means the profile of that name.

package/dist/lib/browser/runtime-state.d.ts

@@ -1,4 +1,5 @@
 import { type ProfileScope } from './profiles.js';
+import { type ProfileName } from './types.js';
 /**
  * Per-profile runtime files we persist under
  * `~/.agents/.cache/browser/<composite>/`:
@@ -55,12 +56,16 @@ export declare function clearProfileRuntime(profileName: string): void;
  */
 export declare function removeProfileCache(profileName: string): void;
 /**
- * Find every cache directory belonging to a given profile. The composite
- * naming (`<name>@<endpoint>`) means a single agents-cli profile can have
- * multiple runtime dirs side by side; this finds them all plus the legacy
+ * Find every cache directory belonging to a given profile. A runtime dir name
+ * IS a connection key (`<name>@<endpoint>[.<fork>]`), so a single agents-cli
+ * profile can have several side by side; this finds them all, plus the legacy
  * non-composite dir from older builds.
+ *
+ * Membership is decided by {@link keyBelongsToProfile} — the same single rule
+ * `status`, `stopProfile`, and `findTask` use (RUSH-2709), so a fork dir is no
+ * longer missed here while being matched there.
  */
-export declare function listProfileCacheDirs(profileName: string): string[];
+export declare function listProfileCacheDirs(profileName: ProfileName): string[];
 /**
  * `process.kill(pid, 0)` answers "is a process with this id alive?" — but
  * pid reuse is real on long-uptime machines, and a stale cache pointing
@@ -162,7 +167,8 @@ export declare const PRUNE_REASON_TEXT: Record<PruneReason, string>;
  *   - **in use** — a live browser, SSH tunnel, or open task on any of its dirs.
  *   - **the configured default** — this machine resolves a bare
  *     `agents browser start` to it; removing it breaks that command.
- *   - **`default`** — auto-regenerated by `ensureDefaultBrowserProfile`, so
+ *   - **the auto-detected profile** (`auto-chrome`, or the `default` an older
+ *     build wrote) — auto-regenerated by `ensureDefaultBrowserProfile`, so
  *     pruning it is pure churn.
  *   - **fleet-synced** — deleting one removes it from EVERY machine, so it takes
  *     the explicit `includeFleet` opt-in.

package/dist/lib/browser/runtime-state.js

@@ -1,7 +1,8 @@
 import * as fs from 'fs';
 import * as path from 'path';
 import { execFileSync } from 'child_process';
-import { getProfileRuntimeDir, getBrowserRuntimeDir, listProfilesWithScope, getConfiguredDefaultProfileName, isProfileLaunchableHere, deleteProfile, DEFAULT_BROWSER_PROFILE_NAME, } from './profiles.js';
+import { getProfileRuntimeDir, getBrowserRuntimeDir, listProfilesWithScope, getConfiguredDefaultProfileName, isProfileLaunchableHere, deleteProfile, DEFAULT_BROWSER_PROFILE_NAME, LEGACY_DEFAULT_BROWSER_PROFILE_NAME, } from './profiles.js';
+import { keyBelongsToProfile } from './types.js';
 const PID_FILE = 'pid';
 const PORT_FILE = 'port';
 const COMMAND_FILE = 'command';
@@ -106,10 +107,14 @@ export function removeProfileCache(profileName) {
     catch { /* gone */ }
 }
 /**
- * Find every cache directory belonging to a given profile. The composite
- * naming (`<name>@<endpoint>`) means a single agents-cli profile can have
- * multiple runtime dirs side by side; this finds them all plus the legacy
+ * Find every cache directory belonging to a given profile. A runtime dir name
+ * IS a connection key (`<name>@<endpoint>[.<fork>]`), so a single agents-cli
+ * profile can have several side by side; this finds them all, plus the legacy
  * non-composite dir from older builds.
+ *
+ * Membership is decided by {@link keyBelongsToProfile} — the same single rule
+ * `status`, `stopProfile`, and `findTask` use (RUSH-2709), so a fork dir is no
+ * longer missed here while being matched there.
  */
 export function listProfileCacheDirs(profileName) {
     const root = getBrowserRuntimeDir();
@@ -117,9 +122,7 @@ export function listProfileCacheDirs(profileName) {
         return [];
     const matches = [];
     for (const entry of fs.readdirSync(root)) {
-        if (entry === profileName)
-            matches.push(path.join(root, entry));
-        else if (entry.startsWith(`${profileName}@`))
+        if (keyBelongsToProfile(entry, profileName))
             matches.push(path.join(root, entry));
     }
     return matches;
@@ -292,7 +295,8 @@ export const PRUNE_REASON_TEXT = {
  *   - **in use** — a live browser, SSH tunnel, or open task on any of its dirs.
  *   - **the configured default** — this machine resolves a bare
  *     `agents browser start` to it; removing it breaks that command.
- *   - **`default`** — auto-regenerated by `ensureDefaultBrowserProfile`, so
+ *   - **the auto-detected profile** (`auto-chrome`, or the `default` an older
+ *     build wrote) — auto-regenerated by `ensureDefaultBrowserProfile`, so
  *     pruning it is pure churn.
  *   - **fleet-synced** — deleting one removes it from EVERY machine, so it takes
  *     the explicit `includeFleet` opt-in.
@@ -310,7 +314,7 @@ export function planProfilePrune(profiles, opts = {}) {
             keep('fleet-synced (pass --fleet to include it)');
             continue;
         }
-        if (name === DEFAULT_BROWSER_PROFILE_NAME) {
+        if (name === DEFAULT_BROWSER_PROFILE_NAME || name === LEGACY_DEFAULT_BROWSER_PROFILE_NAME) {
             keep('the auto-detected default profile');
             continue;
         }