@phnx-labs/agents-cli 1.22.38 → 1.22.40

package/dist/lib/hosts/reconcile.js

@@ -1,7 +1,7 @@
 /**
  * Reconcile a local host-task record against the remote run's ground truth.
  *
- * A detached `--host` run outlives the local follower: it keeps running and
+ * A detached `--device` run outlives the local follower: it keeps running and
  * writes its exit code to `<id>.exit` on the host even if the laptop sleeps or
  * the SSH connection drops mid-follow. When that happens the local record is
  * left at `status:'running'` forever, because the only path that finalizes it

package/dist/lib/hosts/reconnect.d.ts

@@ -99,7 +99,7 @@ export declare function remoteExitNotice(sessionId: string, host: string): strin
  * {@link REMOTE_EXIT_255_REMAPPED} before the wrapper exits — see the file
  * header for why. Every other code (0, 1, …) passes through unchanged. This
  * carries no PATH bootstrap of its own — `ensureHostReady`/`readyProbe` already
- * gates every `--host` dispatch on `bash -lc 'agents --version'` succeeding
+ * gates every `--device` dispatch on `bash -lc 'agents --version'` succeeding
  * before a run is attempted at all, so the peer's login shell resolving `agents`
  * is an established precondition here too. Pure string-building, so it is
  * unit-tested without SSH (and, since the constructed script is ordinary POSIX,

package/dist/lib/hosts/reconnect.js

@@ -1,5 +1,5 @@
 /**
- * Auto-reconnect for an interactive `agents run --device/--host` session whose
+ * Auto-reconnect for an interactive `agents run --device` session whose
  * SSH link dropped.
  *
  * A remote interactive agent runs in a DETACHED tmux session on the peer (see
@@ -174,7 +174,7 @@ export function remoteExitNotice(sessionId, host) {
  * {@link REMOTE_EXIT_255_REMAPPED} before the wrapper exits — see the file
  * header for why. Every other code (0, 1, …) passes through unchanged. This
  * carries no PATH bootstrap of its own — `ensureHostReady`/`readyProbe` already
- * gates every `--host` dispatch on `bash -lc 'agents --version'` succeeding
+ * gates every `--device` dispatch on `bash -lc 'agents --version'` succeeding
  * before a run is attempted at all, so the peer's login shell resolving `agents`
  * is an established precondition here too. Pure string-building, so it is
  * unit-tested without SSH (and, since the constructed script is ordinary POSIX,

package/dist/lib/hosts/registry.d.ts

@@ -58,7 +58,7 @@ export interface MatchHostOptions {
     resolveAuto?: () => DeviceAffinityPlan;
 }
 /**
- * The one place a `--host` / `--device` token becomes a resolved host. Reads the
+ * The one place a `--device` / `--device` token becomes a resolved host. Reads the
  * devices registry, the agents.yaml overlay, and ssh_config, and merges them
  * per-field (see {@link deviceHost}). One grammar for every caller: `name`,
  * `user@name`, a tailnet FQDN, an ssh_config alias, and a literal `user@host`
@@ -77,8 +77,8 @@ export declare function matchHost(name: string, opts?: MatchHostOptions): Promis
  * with it). Provider order still decides the base row (`local` first). */
 export declare function listAllHosts(): Promise<Host[]>;
 /**
- * Resolve a `--host`/`--device` token for DISPATCH — the shape every offload
- * caller consumes (`run --host`, the generic passthrough, teams placement, the
+ * Resolve a `--device`/`--device` token for DISPATCH — the shape every offload
+ * caller consumes (`run --device`, the generic passthrough, teams placement, the
  * cloud host provider, doctor, funnel, remote secrets). Grammar and merge come
  * from {@link matchHost}; on top, this layer applies the device-only dispatch
  * refusals so they hold even when an inline overlay shadows the device:
@@ -88,11 +88,11 @@ export declare function listAllHosts(): Promise<Host[]>;
  *   - an addressless device has nothing to dial.
  *
  * A bare unknown name returns null so capability-tag routing (`resolveHostByCap`,
- * e.g. `--host gpu`) stays reachable, and an ad-hoc `user@host` still resolves.
+ * e.g. `--device gpu`) stays reachable, and an ad-hoc `user@host` still resolves.
  */
 export declare function resolveHost(name: string): Promise<Host | null>;
 /**
- * Resolve a host by capability tag (e.g. `--host gpu`). Returns the single
+ * Resolve a host by capability tag (e.g. `--device gpu`). Returns the single
  * matching host, or throws on 0 or >1 matches unless `any` is set (then first).
  */
 export declare function resolveHostByCap(cap: string, any?: boolean): Promise<Host>;

package/dist/lib/hosts/registry.js

@@ -141,7 +141,7 @@ function literalHost(token, host, user) {
     };
 }
 /**
- * The one place a `--host` / `--device` token becomes a resolved host. Reads the
+ * The one place a `--device` / `--device` token becomes a resolved host. Reads the
  * devices registry, the agents.yaml overlay, and ssh_config, and merges them
  * per-field (see {@link deviceHost}). One grammar for every caller: `name`,
  * `user@name`, a tailnet FQDN, an ssh_config alias, and a literal `user@host`
@@ -236,8 +236,8 @@ export async function listAllHosts() {
     return [...byName.values()].sort((a, b) => a.name.localeCompare(b.name));
 }
 /**
- * Resolve a `--host`/`--device` token for DISPATCH — the shape every offload
- * caller consumes (`run --host`, the generic passthrough, teams placement, the
+ * Resolve a `--device`/`--device` token for DISPATCH — the shape every offload
+ * caller consumes (`run --device`, the generic passthrough, teams placement, the
  * cloud host provider, doctor, funnel, remote secrets). Grammar and merge come
  * from {@link matchHost}; on top, this layer applies the device-only dispatch
  * refusals so they hold even when an inline overlay shadows the device:
@@ -247,7 +247,7 @@ export async function listAllHosts() {
  *   - an addressless device has nothing to dial.
  *
  * A bare unknown name returns null so capability-tag routing (`resolveHostByCap`,
- * e.g. `--host gpu`) stays reachable, and an ad-hoc `user@host` still resolves.
+ * e.g. `--device gpu`) stays reachable, and an ad-hoc `user@host` still resolves.
  */
 export async function resolveHost(name) {
     const host = await matchHost(name);
@@ -267,7 +267,7 @@ export async function resolveHost(name) {
     return host;
 }
 /**
- * Resolve a host by capability tag (e.g. `--host gpu`). Returns the single
+ * Resolve a host by capability tag (e.g. `--device gpu`). Returns the single
  * matching host, or throws on 0 or >1 matches unless `any` is set (then first).
  */
 export async function resolveHostByCap(cap, any = false) {

package/dist/lib/hosts/remote-cmd.d.ts

@@ -1,5 +1,5 @@
 /**
- * Pure argv helpers for `--host` passthrough — build the remote `agents …`
+ * Pure argv helpers for `--device` passthrough — build the remote `agents …`
  * invocation and strip the local-only routing flags before forwarding.
  *
  * Kept free of any SSH/process side effects so the two-layer quoting and the
@@ -13,7 +13,7 @@ export interface StripSpec {
     long: string;
     /** Optional single-letter short form without the dash, e.g. `H`. */
     short?: string;
-    /** True when the flag takes a following value token (`--host <name>`). */
+    /** True when the flag takes a following value token (`--device <name>`). */
     takesValue: boolean;
 }
 /**
@@ -26,14 +26,13 @@ export interface StripSpec {
  */
 export declare function stripRoutingFlags(args: string[], specs: StripSpec[]): string[];
 /**
- * The routing flags every `--host`-capable command shares. `--device` is a
- * first-class alias of `--host` (the device registry is the source of truth for
- * machine identity — see `agents devices`), mirroring `agents run --device`.
- * Both are stripped before forwarding so the alias never leaks to the remote
- * binary (which would re-trigger routing).
+ * The routing flags every `--device`-capable command shares. Stripped before
+ * forwarding so the flag never leaks to the remote binary (which would
+ * re-trigger routing). `--host`/`-H` are kept for backward-compat strip only
+ * (they are no longer user-facing routing flags).
  */
 export declare const HOST_ROUTING_SPECS: StripSpec[];
-/** How one `agents run` option behaves when the run is offloaded with `--host`. */
+/** How one `agents run` option behaves when the run is offloaded with `--device`. */
 export type RunOptionForwarding = 
 /** Appended to the remote `agents run` argv — same behavior local or remote. */
 'forward'
@@ -42,7 +41,7 @@ export type RunOptionForwarding =
 /** Consumed by the dispatching side (routing, follow rendering, cwd portability). */
  | 'local-only';
 /**
- * The forwarding contract for `agents run … --host`: every option of the `run`
+ * The forwarding contract for `agents run … --device`: every option of the `run`
  * command is classified here, keyed by its commander attribute name. A
  * commander-introspection test (run-forwarding.test.ts) fails when a run
  * option is missing from this table, so a new option can never silently drop
@@ -161,7 +160,7 @@ export declare function windowsAgentsScript(cmd: WindowsAgentsCommand): string;
 /**
  * Build the `ssh <target> <cmd>` string for one `agents …` invocation on a
  * Windows remote: a `powershell -NoProfile -EncodedCommand <base64>` call. The
- * Windows counterpart of `bash -lc '<...>'`, shared by every `--host` site.
+ * Windows counterpart of `bash -lc '<...>'`, shared by every `--device` site.
  */
 export declare function buildWindowsAgentsCommand(cmd: WindowsAgentsCommand): string;
 /**
@@ -180,4 +179,5 @@ export declare function buildWindowsAgentsCommand(cmd: WindowsAgentsCommand): st
  */
 export declare function buildWindowsStdinImportCommand(bundle: string, opts?: {
     force?: boolean;
+    policyNever?: boolean;
 }): string;

package/dist/lib/hosts/remote-cmd.js

@@ -1,5 +1,5 @@
 /**
- * Pure argv helpers for `--host` passthrough — build the remote `agents …`
+ * Pure argv helpers for `--device` passthrough — build the remote `agents …`
  * invocation and strip the local-only routing flags before forwarding.
  *
  * Kept free of any SSH/process side effects so the two-layer quoting and the
@@ -39,19 +39,18 @@ export function stripRoutingFlags(args, specs) {
     return out;
 }
 /**
- * The routing flags every `--host`-capable command shares. `--device` is a
- * first-class alias of `--host` (the device registry is the source of truth for
- * machine identity — see `agents devices`), mirroring `agents run --device`.
- * Both are stripped before forwarding so the alias never leaks to the remote
- * binary (which would re-trigger routing).
+ * The routing flags every `--device`-capable command shares. Stripped before
+ * forwarding so the flag never leaks to the remote binary (which would
+ * re-trigger routing). `--host`/`-H` are kept for backward-compat strip only
+ * (they are no longer user-facing routing flags).
  */
 export const HOST_ROUTING_SPECS = [
+    { long: 'device', short: 'D', takesValue: true },
     { long: 'host', short: 'H', takesValue: true },
-    { long: 'device', takesValue: true },
     { long: 'remote-cwd', takesValue: true },
 ];
 /**
- * The forwarding contract for `agents run … --host`: every option of the `run`
+ * The forwarding contract for `agents run … --device`: every option of the `run`
  * command is classified here, keyed by its commander attribute name. A
  * commander-introspection test (run-forwarding.test.ts) fails when a run
  * option is missing from this table, so a new option can never silently drop
@@ -104,7 +103,6 @@ export const RUN_OPTION_FORWARDING = {
     raw: 'local-only', // interactive builder forwards --raw itself
     tmux: 'local-only',
     disableTmux: 'local-only',
-    host: 'local-only',
     device: 'local-only',
     where: 'local-only', // expands into host/lease before dispatch; never re-forwarded
     on: 'local-only',
@@ -120,7 +118,7 @@ export const RUN_OPTION_FORWARDING = {
     tailscale: 'local-only', // --tailscale/--no-tailscale gate the lease net mode; never forwarded
     copyCreds: 'local-only', // copies creds TO the host before dispatch — local concern only
     // Cloud placement: chosen and dispatched from THIS machine via the provider
-    // registry; mutually exclusive with --host (placement conflict dies before
+    // registry; mutually exclusive with --device (placement conflict dies before
     // dispatch), so these never have a remote argv to ride.
     cloud: 'local-only',
     provider: 'local-only',
@@ -135,19 +133,27 @@ export const RUN_OPTION_FORWARDING = {
     notify: 'local-only',
     // Deprecated alias for --device auto; resolved on the launching box before SSH.
     smart: 'local-only',
+    // Broadcast mode (agents run --broadcast) is its own fan-out dispatch — mutually
+    // exclusive with --host. All broadcast options are local-only; exec.ts handles them
+    // before any SSH dispatch path is reached.
+    broadcast: 'local-only',
+    task: 'local-only',
+    listTasks: 'local-only',
+    results: 'local-only',
+    concurrency: 'local-only',
 };
 /** Actionable messages for value-aware rejections, keyed by attribute name. */
 export const RUN_OPTION_REJECT_MESSAGES = {
-    terminal: '--terminal opens a tab on THIS machine; it cannot be combined with --host. ' +
-        'Drop --terminal to dispatch to the host, or drop --host to open the tab here. ' +
-        'To watch a remote run in a terminal, dispatch it and follow with `agents sessions resume <id>`.',
+    terminal: '--terminal opens a tab on THIS machine; it cannot be combined with --device. ' +
+        'Drop --terminal to dispatch to the device, or drop --device to open the tab here. ' +
+        'To watch a remote run in a terminal, dispatch it and follow with `agents sessions focus <id>`.',
     secrets: '--secrets cannot cross the SSH boundary — Keychain values are never sent to a host implicitly. ' +
-        'Provision the bundle on the host first (agents secrets export --host <name>), then run without --secrets; ' +
+        'Provision the bundle on the host first (agents secrets export --device <name>), then run without --secrets; ' +
         'workflow frontmatter secrets resolve from the HOST\'s own keychain.',
     secretsKeys: '--secrets-keys applies to --secrets bundles, which cannot cross the SSH boundary (see --secrets).',
     allowExpired: '--allow-expired applies to --secrets bundles, which cannot cross the SSH boundary (see --secrets).',
     resumeCheckpoint: '--resume-checkpoint reads a local checkpoint.json — it cannot resume a run on another machine. Run it locally, or start a fresh --loop run on the host.',
-    resumeBare: '--resume with no id opens the interactive picker, which cannot run across a detached host dispatch. Pass a concrete session id: agents run <agent> --resume <id> --host <name>.',
+    resumeBare: '--resume with no id opens the interactive picker, which cannot run across a detached host dispatch. Pass a concrete session id: agents run <agent> --resume <id> --device <name>.',
 };
 /**
  * Build the single command string for `ssh <target> <cmd>`. The forwarded args
@@ -298,7 +304,7 @@ export function windowsAgentsScript(cmd) {
 /**
  * Build the `ssh <target> <cmd>` string for one `agents …` invocation on a
  * Windows remote: a `powershell -NoProfile -EncodedCommand <base64>` call. The
- * Windows counterpart of `bash -lc '<...>'`, shared by every `--host` site.
+ * Windows counterpart of `bash -lc '<...>'`, shared by every `--device` site.
  */
 export function buildWindowsAgentsCommand(cmd) {
     return `powershell -NoProfile -EncodedCommand ${encodePowershell(windowsAgentsScript(cmd))}`;
@@ -319,18 +325,19 @@ export function buildWindowsAgentsCommand(cmd) {
  */
 export function buildWindowsStdinImportCommand(bundle, opts = {}) {
     const force = opts.force ? ' --force' : '';
+    const policy = opts.policyNever ? ' --policy never --i-understand' : '';
     // Create AND write the temp file INSIDE the try so its finally always cleans
     // up: if GetTempFileName succeeds but WriteAllText (or the import) then throws,
     // the secret-bearing temp file would otherwise be left behind (RUSH-1764). $tmp
     // starts null so a GetTempFileName that itself throws leaves nothing to remove.
     const script = [
         // Same CLIXML guard as windowsAgentsScript — this builder also runs `& agents …`
-        // and its raw stderr is printed to the user on failure (secrets export --host <win>).
+        // and its raw stderr is printed to the user on failure (secrets export --device <win>).
         POWERSHELL_PROGRESS_SILENCE,
         '$in = [Console]::In.ReadToEnd()',
         '$tmp = $null',
         `try { $tmp = [System.IO.Path]::GetTempFileName(); [System.IO.File]::WriteAllText($tmp, $in); ` +
-            `& agents secrets import ${powershellQuote(bundle)} --from $tmp${force}; $code = $LASTEXITCODE } ` +
+            `& agents secrets import ${powershellQuote(bundle)} --from $tmp${force}${policy}; $code = $LASTEXITCODE } ` +
             `finally { if ($tmp) { Remove-Item -LiteralPath $tmp -Force -ErrorAction SilentlyContinue } }`,
         'if ($null -eq $code) { $code = 1 }',
         'exit $code',

package/dist/lib/hosts/remote-os.d.ts

@@ -4,9 +4,9 @@
  * in `remote-cmd.ts` for how the string is consumed.
  *
  * Three sources, in priority order:
- *   1. The central config `platform` key (`fleet.devices.<name>.config.platform`
- *      in agents.yaml) — the operator's explicit override, set with
- *      `agents devices config <name> platform <os>`.
+ *   1. The config `platform` key (the per-device doc's config.platform,
+ *      over the `fleet.defaults.config` fleet default) — the operator's
+ *      explicit override, set with `agents devices config <name> platform <os>`.
  *   2. The device registry `platform` (`windows`/`linux`/`macos`), which is
  *      populated fleet-wide by Tailscale sync — the reliable answer for a box
  *      like `win-mini` that was discovered, not hand-enrolled.
@@ -14,7 +14,7 @@
  *      when the overlay entry was written), for hosts that live only in that overlay.
  *
  * Missing/unknown from all three → `undefined`, which `remoteShellFor` maps to
- * POSIX. Kept synchronous so the sync `agents sessions --host` fan-out can use it.
+ * POSIX. Kept synchronous so the sync `agents sessions --device` fan-out can use it.
  */
 /** Resolve the OS/platform string for a host name, or undefined if unknown. */
 export declare function resolveRemoteOsSync(name: string): string | undefined;

package/dist/lib/hosts/remote-os.js

@@ -4,9 +4,9 @@
  * in `remote-cmd.ts` for how the string is consumed.
  *
  * Three sources, in priority order:
- *   1. The central config `platform` key (`fleet.devices.<name>.config.platform`
- *      in agents.yaml) — the operator's explicit override, set with
- *      `agents devices config <name> platform <os>`.
+ *   1. The config `platform` key (the per-device doc's config.platform,
+ *      over the `fleet.defaults.config` fleet default) — the operator's
+ *      explicit override, set with `agents devices config <name> platform <os>`.
  *   2. The device registry `platform` (`windows`/`linux`/`macos`), which is
  *      populated fleet-wide by Tailscale sync — the reliable answer for a box
  *      like `win-mini` that was discovered, not hand-enrolled.
@@ -14,7 +14,7 @@
  *      when the overlay entry was written), for hosts that live only in that overlay.
  *
  * Missing/unknown from all three → `undefined`, which `remoteShellFor` maps to
- * POSIX. Kept synchronous so the sync `agents sessions --host` fan-out can use it.
+ * POSIX. Kept synchronous so the sync `agents sessions --device` fan-out can use it.
  */
 import { loadDevicesSync } from '../devices/registry.js';
 import { readDeviceConfigValues } from '../device-config.js';

package/dist/lib/hosts/remote-session-id.d.ts

@@ -1,7 +1,7 @@
 /**
- * Resolve a remote-created session id back to an interactive `--host` launcher.
+ * Resolve a remote-created session id back to an interactive `--device` launcher.
  *
- * A headless `--host` run captures the remote-coined id from the followed log
+ * A headless `--device` run captures the remote-coined id from the followed log
  * (the `--emit-session-id` marker — see session-marker.ts). An INTERACTIVE run
  * has no followed log: the local TTY is wired straight through `sshStream`
  * (stdio:'inherit'), so nothing can tap the stream for a marker without breaking

package/dist/lib/hosts/remote-session-id.js

@@ -1,7 +1,7 @@
 /**
- * Resolve a remote-created session id back to an interactive `--host` launcher.
+ * Resolve a remote-created session id back to an interactive `--device` launcher.
  *
- * A headless `--host` run captures the remote-coined id from the followed log
+ * A headless `--device` run captures the remote-coined id from the followed log
  * (the `--emit-session-id` marker — see session-marker.ts). An INTERACTIVE run
  * has no followed log: the local TTY is wired straight through `sshStream`
  * (stdio:'inherit'), so nothing can tap the stream for a marker without breaking

package/dist/lib/hosts/routing-flag.d.ts

@@ -10,11 +10,11 @@
  * `flagValue` lives here (not in passthrough.ts) for the same reason: the gate
  * and the function body that later reads flag values share one implementation.
  */
-/** Pull the value of `--host`/`-H`/`--remote-cwd` (any form) out of an argv. */
+/** Pull the value of `--device`/`-D`/`--remote-cwd` (any form) out of an argv. */
 export declare function flagValue(args: string[], long: string, short?: string): string | undefined;
 /**
- * True when argv carries any host/device routing flag that {@link maybeRunOnHost}
- * inspects: `--host`/`-H`, `--device`, `--hosts`, `--devices` (space, `=`, or
+ * True when argv carries any device routing flag that {@link maybeRunOnHost}
+ * inspects: `--device`/`-D`, `--hosts`, `--devices` (space, `=`, or
  * glued short form).
  *
  * Presence-only — does not validate values. Used by bootstrap before loading

package/dist/lib/hosts/routing-flag.js

@@ -10,7 +10,7 @@
  * `flagValue` lives here (not in passthrough.ts) for the same reason: the gate
  * and the function body that later reads flag values share one implementation.
  */
-/** Pull the value of `--host`/`-H`/`--remote-cwd` (any form) out of an argv. */
+/** Pull the value of `--device`/`-D`/`--remote-cwd` (any form) out of an argv. */
 export function flagValue(args, long, short) {
     for (let i = 0; i < args.length; i++) {
         const a = args[i];
@@ -26,16 +26,15 @@ export function flagValue(args, long, short) {
     return undefined;
 }
 /**
- * True when argv carries any host/device routing flag that {@link maybeRunOnHost}
- * inspects: `--host`/`-H`, `--device`, `--hosts`, `--devices` (space, `=`, or
+ * True when argv carries any device routing flag that {@link maybeRunOnHost}
+ * inspects: `--device`/`-D`, `--hosts`, `--devices` (space, `=`, or
  * glued short form).
  *
  * Presence-only — does not validate values. Used by bootstrap before loading
  * passthrough, and by `maybeRunStandaloneOnHost` before strip/route work.
  */
 export function hasHostRoutingFlag(args) {
-    return (flagValue(args, 'host', 'H') !== undefined ||
-        flagValue(args, 'device') !== undefined ||
+    return (flagValue(args, 'device', 'D') !== undefined ||
         flagValue(args, 'hosts') !== undefined ||
         flagValue(args, 'devices') !== undefined);
 }

package/dist/lib/hosts/run-target.d.ts

@@ -1,12 +1,12 @@
 /**
  * Shared host-run dispatch — the one path every surface uses to run an agent on
- * another machine: `agents run --host` (commands/exec.ts), the `host` cloud
+ * another machine: `agents run --device` (commands/exec.ts), the `host` cloud
  * provider (`agents cloud run --provider host`), and host-placed routines.
  *
  * Wraps the two steps every caller needs and previously lived inline in
- * exec.ts's `--host` branch:
+ * exec.ts's `--device` branch:
  *   1. resolution — name → capability tag → error, with the same fall-through
- *      semantics as `agents run --host` (only "Multiple hosts tagged…" is a
+ *      semantics as `agents run --device` (only "Multiple hosts tagged…" is a
  *      resolution verdict; "no host tagged" degrades to unknown-host), and
  *   2. headless dispatch — session-id mint (Claude only), detached SSH launch,
  *      and LOCAL session-index registration so the run shows in `agents sessions`.
@@ -26,7 +26,7 @@ export declare class HostResolutionError extends Error {
     constructor(message: string);
 }
 /**
- * Resolve a `--host` value the way `agents run` does: exact name (providers →
+ * Resolve a `--device` value the way `agents run` does: exact name (providers →
  * devices → `user@host`), then capability tag. Throws `HostResolutionError`
  * for an ambiguous tag or an unknown name; lets `DeviceOffloadUnsupportedError`
  * (password-auth device) propagate untouched for the top-level catch.

package/dist/lib/hosts/run-target.js

@@ -1,12 +1,12 @@
 /**
  * Shared host-run dispatch — the one path every surface uses to run an agent on
- * another machine: `agents run --host` (commands/exec.ts), the `host` cloud
+ * another machine: `agents run --device` (commands/exec.ts), the `host` cloud
  * provider (`agents cloud run --provider host`), and host-placed routines.
  *
  * Wraps the two steps every caller needs and previously lived inline in
- * exec.ts's `--host` branch:
+ * exec.ts's `--device` branch:
  *   1. resolution — name → capability tag → error, with the same fall-through
- *      semantics as `agents run --host` (only "Multiple hosts tagged…" is a
+ *      semantics as `agents run --device` (only "Multiple hosts tagged…" is a
  *      resolution verdict; "no host tagged" degrades to unknown-host), and
  *   2. headless dispatch — session-id mint (Claude only), detached SSH launch,
  *      and LOCAL session-index registration so the run shows in `agents sessions`.
@@ -30,7 +30,7 @@ export class HostResolutionError extends Error {
     }
 }
 /**
- * Resolve a `--host` value the way `agents run` does: exact name (providers →
+ * Resolve a `--device` value the way `agents run` does: exact name (providers →
  * devices → `user@host`), then capability tag. Throws `HostResolutionError`
  * for an ambiguous tag or an unknown name; lets `DeviceOffloadUnsupportedError`
  * (password-auth device) propagate untouched for the top-level catch.

package/dist/lib/hosts/session-index.d.ts

@@ -1,5 +1,5 @@
 /**
- * Register host-dispatched runs (`agents run --host <h>`) into the LOCAL session
+ * Register host-dispatched runs (`agents run --device <h>`) into the LOCAL session
  * index so they show up in `agents sessions` and are resolvable by id — even
  * though the transcript itself lives on the remote host.
  *
@@ -19,7 +19,7 @@
 import type { SessionMeta } from '../session/types.js';
 import { type HostTask } from './tasks.js';
 export interface HostSessionContext {
-    /** Local directory the `agents run --host` was invoked from. */
+    /** Local directory the `agents run --device` was invoked from. */
     cwd: string;
     /** Prompt the run was launched with, used for the session topic. */
     prompt: string;

package/dist/lib/hosts/session-index.js

@@ -1,5 +1,5 @@
 /**
- * Register host-dispatched runs (`agents run --host <h>`) into the LOCAL session
+ * Register host-dispatched runs (`agents run --device <h>`) into the LOCAL session
  * index so they show up in `agents sessions` and are resolvable by id — even
  * though the transcript itself lives on the remote host.
  *

package/dist/lib/hosts/session-marker.d.ts

@@ -1,7 +1,7 @@
 /**
  * Relate a remote-created session id back to the launching agent.
  *
- * A host dispatch (`agents run --host`) launches `agents run` on the remote box.
+ * A host dispatch (`agents run --device`) launches `agents run` on the remote box.
  * Only Claude accepts a forced `--session-id`, so for every OTHER agent the
  * remote run coins its OWN session id (via its SessionStart hook) and the
  * launcher never learns it — the run is orphaned in `agents sessions`.

package/dist/lib/hosts/session-marker.js

@@ -1,7 +1,7 @@
 /**
  * Relate a remote-created session id back to the launching agent.
  *
- * A host dispatch (`agents run --host`) launches `agents run` on the remote box.
+ * A host dispatch (`agents run --device`) launches `agents run` on the remote box.
  * Only Claude accepts a forced `--session-id`, so for every OTHER agent the
  * remote run coins its OWN session id (via its SessionStart hook) and the
  * launcher never learns it — the run is orphaned in `agents sessions`.

package/dist/lib/hosts/types.d.ts

@@ -19,7 +19,7 @@ export interface Host extends HostEntry {
     enrolled?: boolean;
     status?: HostStatus;
     /**
-     * False when the host is listed for honesty but can't carry a `--host` run
+     * False when the host is listed for honesty but can't carry a `--device` run
      * (today: password-auth devices — offload rides BatchMode=yes ssh). Absent
      * means dispatchable. Cap routing and target pickers filter on this.
      */
@@ -29,7 +29,7 @@ export interface Host extends HostEntry {
  * Thrown when a device resolves but can't be used as an offload target because
  * it authenticates with a password. The offload path runs over `sshExec`, whose
  * `SSH_OPTS` force `BatchMode=yes` (no password prompts), so only key / ssh-config
- * auth can carry a `--host` run. Named so the top-level catch prints the message
+ * auth can carry a `--device` run. Named so the top-level catch prints the message
  * cleanly instead of a stack trace. (Lives here, not registry.ts, so providers
  * can throw it without a circular import; registry.ts re-exports it.)
  */

package/dist/lib/hosts/types.js

@@ -12,13 +12,13 @@
  * Thrown when a device resolves but can't be used as an offload target because
  * it authenticates with a password. The offload path runs over `sshExec`, whose
  * `SSH_OPTS` force `BatchMode=yes` (no password prompts), so only key / ssh-config
- * auth can carry a `--host` run. Named so the top-level catch prints the message
+ * auth can carry a `--device` run. Named so the top-level catch prints the message
  * cleanly instead of a stack trace. (Lives here, not registry.ts, so providers
  * can throw it without a circular import; registry.ts re-exports it.)
  */
 export class DeviceOffloadUnsupportedError extends Error {
     constructor(name) {
-        super(`Device "${name}" uses password auth, which --host offload can't use yet ` +
+        super(`Device "${name}" uses password auth, which --device offload can't use yet ` +
             `(runs go over ssh with BatchMode=yes). Switch it to key auth with ` +
             `\`agents devices config ${name} ssh.auth key\`.`);
         this.name = 'DeviceOffloadUnsupportedError';

package/dist/lib/import.js

@@ -21,7 +21,7 @@ import * as os from 'os';
 import * as path from 'path';
 import { AGENTS, resolveNativeBinaryPath } from './agents.js';
 import { getUserAgentsDir, getVersionsDir } from './state.js';
-import { setGlobalDefault } from './versions.js';
+import { setGlobalDefault } from './installations/versions.js';
 import { createShim, createVersionedAlias, ensureShimCurrent, switchHomeFileSymlinks, assertIsolationBoundary } from './shims.js';
 const IMPORT_VERSION_RE = /^(?:latest|[A-Za-z0-9._+-]{1,64})$/;
 export function isValidImportVersion(version) {

package/dist/lib/{migrate.d.ts → installations/migrate.d.ts}

@@ -4,7 +4,7 @@
  * Called from postinstall and as a command-time fallback from agents view/use/pull.
  * Each migration is guarded by an existence check so re-running is safe.
  */
-export { foldLegacySystemRepo } from './migrate-fold.js';
+export { foldLegacySystemRepo } from '../migrate-fold.js';
 /**
  * Migrate a legacy single-repo agents.yaml into ~/.agents/agents.yaml.
  *
@@ -58,6 +58,42 @@ export declare function foldBrowserSessionsIntoProfiles(browserDir?: string): vo
  * can drive a fixture tree without touching the user's ~/.agents.
  */
 export declare function repairSelfReferentialBinShims(versionsRoot?: string, shimsDir?: string, historyDir?: string): void;
+/**
+ * Move the auto-detected `default` browser profile OUT of the committed central
+ * agents.yaml and into this machine's per-device file.
+ *
+ * `browser` is a CENTRAL key because named profiles a user creates are real fleet
+ * config, but the ONE `default` entry inside it is machine-local: its `binary` is
+ * an OS-specific path and its endpoint is a locally-chosen free port.
+ * `createProfile`/`updateProfile` already route that entry to `deviceBrowser`
+ * (`isMachineLocalProfile`, browser/profiles.ts) — but nothing ever removed the
+ * copy older versions had already written into the shared file, and
+ * `serializeCentral` cannot: it deletes whole KEYS that are device-scoped, and
+ * `browser` is not one.
+ *
+ * So the entry sat in the committed file and every box rewrote it with its own
+ * browser. Measured 2026-08-13, all three boxes on 1.22.38 (which HAS the writer
+ * fix) with an empty `deviceBrowser` and a machine-specific `default` in central:
+ *
+ *   zion         browser: chrome    binary: /Applications/Google Chrome.app/...
+ *   yosemite-s1  browser: brave     binary: /opt/brave.com/brave/brave
+ *   mark-1       (same shape)
+ *
+ * `agents repos pull user` refuses when an incoming change touches a locally
+ * modified path, so agents.yaml being permanently dirty wedged the fleet config
+ * sync outright — those boxes sat 5, 8 and 79 commits behind. (RUSH-2161)
+ *
+ * Idempotent: no-op once central carries no `default` entry. The device file is
+ * written FIRST so a crash between the two writes can never lose the profile,
+ * and an entry already in the device file wins (this machine's live value is
+ * newer than the stale central copy by construction).
+ *
+ * Central is edited through a `yaml.Document` rather than re-stringified, so the
+ * hand-written comments in the committed agents.yaml survive — a plain
+ * `yaml.stringify` would drop every one of them and rewrite the whole file,
+ * which is the same churn this migration exists to stop (see `serializeCentral`).
+ */
+export declare function migrateMachineLocalBrowserProfileOutOfCentral(userDir?: string, machine?: string): void;
 /**
  * Rename the legacy `extras-extras/` plugin-marketplace dir to `agents-extras/`
  * inside every installed agent version-home, and rewrite cross-references in
@@ -179,5 +215,17 @@ export declare function seedActiveCursorLoginPerVersion(): void;
  * `foo.yaml` beside it. Idempotent; a no-op once the dirs are clean.
  */
 export declare function migrateKimiSubagentsToMarkdown(versionsDir?: string): void;
+/**
+ * Remove the compiled "project" ruleset the compiler used to write into $HOME
+ * (RUSH-2725). `compileRulesForProject` treated any cwd with `.agents/rules`
+ * as a project — and the user layer at ~/.agents satisfies that test — so it
+ * wrote ~/AGENTS.md plus per-agent symlinks, and every session under $HOME
+ * then loaded the entire ruleset twice (global memory + "project" memory).
+ * The compiler now refuses reserved roots; this removes the artifact already
+ * on disk. Only files we provably own are touched: an AGENTS.md carrying the
+ * compiled-project header, symlinks pointing at it, and copy-fallback files
+ * (symlink-less filesystems) carrying the same header.
+ */
+export declare function removeHomeCompiledProjectRules(homeDir?: string): void;
 /** Run all idempotent migrations. Safe to call multiple times. */
 export declare function runMigration(): Promise<void>;