@phnx-labs/agents-cli 1.22.84 → 1.22.86

package/dist/lib/fleet/auth-sync.js

@@ -138,9 +138,10 @@ export const FLEET_LOGIN_FLOWS = {
     // claude: interactive `/login` inside the TUI is a loopback browser flow, and
     // the token is keychain-bound on macOS. That native login stays per-box and
     // is never copied. The shareable `claude setup-token` mint is a different
-    // credential class — wired as `agents accounts mint claude` / `agents auth mint`
-    // (`lib/auth-mint.ts`), not as a fleet-login device-code flow (a setup-token
-    // is account-scoped, not per-machine).
+    // credential class — minted by `agents accounts add claude [name]` /
+    // `agents accounts login claude#<name>` (`lib/auth-mint.ts`), not as a
+    // fleet-login device-code flow (a setup-token is account-scoped, not
+    // per-machine).
     claude: {
         loginCommand: 'claude',
         flowType: 'loopback',

package/dist/lib/fleet-shared-repo-sync.js

@@ -267,15 +267,12 @@ async function performFleetSharedRepoSync(root, device, timeoutMs) {
     }
     const ownedFile = fleetSharedStatePath(device, root);
     const relativeOwnedFile = path.relative(root, ownedFile).split(path.sep).join('/');
-    // The central `agents.yaml` is fleet-shared state too — `agents accounts label`
-    // writes version-scoped native account rows there (lib/state.ts writeMetaUnlocked),
-    // as a plain file write with no commit. Publishing only the per-device file and
-    // then `rebase --autostash`-ing over a dirty central file silently destroyed
-    // those labels: every box lost its account labels on its next daemon publish
-    // (PHNX-3887). Commit it alongside the device doc so the rebase carries the
-    // rows instead of stashing them, which is also what `accounts label --help`
-    // already promises ("labels live on the central account rows in agents.yaml,
-    // which repo push/pull already syncs fleet-wide").
+    // The central `agents.yaml` is fleet-shared state too — native account rows
+    // land there (lib/state.ts writeMetaUnlocked) as a plain file write with no
+    // commit. Publishing only the per-device file and then `rebase --autostash`-ing
+    // over a dirty central file silently destroyed those names: every box lost its
+    // account names on its next daemon publish (PHNX-3887). Commit it alongside the
+    // device doc so the rebase carries the rows instead of stashing them.
     const centralFile = path.join(root, 'agents.yaml');
     const publishPaths = [relativeOwnedFile];
     if (fs.existsSync(centralFile))

package/dist/lib/harness/adapter.d.ts

@@ -150,16 +150,16 @@ export interface HarnessAdapter {
     routineModeArgs?(cmd: string[], ctx: RoutineLaunchCtx): void;
 }
 /**
- * The four config-dir env keys a harness pins to its version home. Every
- * per-harness branch in the old buildExecEnv deleted the ones it does NOT set,
- * so its own config pointer never leaks into a foreign harness's invocation.
- * (XDG_CONFIG_HOME / XDG_DATA_HOME — Muse/Cursor — are deliberately absent: the
- * old code sets them but never strips them, and this preserves that exactly.)
+ * Config-dir env keys a harness pins to its slot / version home. Every
+ * per-harness branch in buildExecEnv deletes the ones it does NOT set, so a
+ * slot never inherits another account's dir (PHNX-3940 T5). GROK_HOME,
+ * OPENCODE_CONFIG_DIR, and the XDG pair were previously omitted, which let a
+ * parent agent's pin leak into a sibling slot.
  */
-export declare const CONFIG_DIR_ENV_KEYS: readonly ["CLAUDE_CONFIG_DIR", "CODEX_HOME", "COPILOT_HOME", "KIMI_CODE_HOME"];
+export declare const CONFIG_DIR_ENV_KEYS: readonly ["CLAUDE_CONFIG_DIR", "CODEX_HOME", "COPILOT_HOME", "KIMI_CODE_HOME", "GROK_HOME", "OPENCODE_CONFIG_DIR", "XDG_CONFIG_HOME", "XDG_DATA_HOME"];
 /**
  * Strip every config-dir env key except the one(s) this harness sets. `keep=[]`
- * (the default / no-config-dir harness) deletes all four — the old `else` arm.
+ * (the default / no-config-dir harness) deletes all of them — the old `else` arm.
  */
 export declare function stripForeignConfigDir(result: NodeJS.ProcessEnv, keep?: readonly string[]): void;
 export declare function registerHarnessAdapter(adapter: HarnessAdapter): void;

package/dist/lib/harness/adapter.js

@@ -1,19 +1,23 @@
 /**
- * The four config-dir env keys a harness pins to its version home. Every
- * per-harness branch in the old buildExecEnv deleted the ones it does NOT set,
- * so its own config pointer never leaks into a foreign harness's invocation.
- * (XDG_CONFIG_HOME / XDG_DATA_HOME — Muse/Cursor — are deliberately absent: the
- * old code sets them but never strips them, and this preserves that exactly.)
+ * Config-dir env keys a harness pins to its slot / version home. Every
+ * per-harness branch in buildExecEnv deletes the ones it does NOT set, so a
+ * slot never inherits another account's dir (PHNX-3940 T5). GROK_HOME,
+ * OPENCODE_CONFIG_DIR, and the XDG pair were previously omitted, which let a
+ * parent agent's pin leak into a sibling slot.
  */
 export const CONFIG_DIR_ENV_KEYS = [
     'CLAUDE_CONFIG_DIR',
     'CODEX_HOME',
     'COPILOT_HOME',
     'KIMI_CODE_HOME',
+    'GROK_HOME',
+    'OPENCODE_CONFIG_DIR',
+    'XDG_CONFIG_HOME',
+    'XDG_DATA_HOME',
 ];
 /**
  * Strip every config-dir env key except the one(s) this harness sets. `keep=[]`
- * (the default / no-config-dir harness) deletes all four — the old `else` arm.
+ * (the default / no-config-dir harness) deletes all of them — the old `else` arm.
  */
 export function stripForeignConfigDir(result, keep = []) {
     for (const key of CONFIG_DIR_ENV_KEYS) {

package/dist/lib/harness/adapters/grok.js

@@ -1,8 +1,13 @@
-// Grok has no exec-time config-dir env pin (buildExecEnv's `else` strips the
-// foreign keys — the registry fallback preserves that). It DOES relocate its
-// whole config tree via GROK_HOME in the generated shim.
+import * as path from 'path';
+import { stripForeignConfigDir } from '../adapter.js';
 export const grokAdapter = {
     id: 'grok',
+    applyExecConfigEnv(result, ctx) {
+        if (ctx.versionHome) {
+            result.GROK_HOME = path.join(ctx.versionHome, '.grok');
+        }
+        stripForeignConfigDir(result, ['GROK_HOME']);
+    },
     shimConfigEnvBash() {
         return `
 # Grok Build uses GROK_HOME to isolate its entire configuration tree

package/dist/lib/harness/adapters/muse.js

@@ -13,7 +13,7 @@ export const museAdapter = {
             result.XDG_CONFIG_HOME = path.join(ctx.versionHome, '.config');
             result.XDG_DATA_HOME = path.join(ctx.versionHome, '.local', 'share');
         }
-        stripForeignConfigDir(result);
+        stripForeignConfigDir(result, ['XDG_CONFIG_HOME', 'XDG_DATA_HOME']);
     },
     shimConfigEnvBash() {
         return `

package/dist/lib/harness/adapters/opencode.js

@@ -1,8 +1,17 @@
-// OpenCode has no exec-time config-dir env pin (buildExecEnv's `else` strips the
-// foreign keys — the registry fallback preserves that). It reads config-directory
-// resources from OPENCODE_CONFIG_DIR, pinned in the generated shim.
+import * as path from 'path';
+import { stripForeignConfigDir } from '../adapter.js';
+// OpenCode reads plugins/agents/commands from OPENCODE_CONFIG_DIR and auth from
+// $XDG_DATA_HOME/opencode (HARNESS_AUTH.slotEnv). Pin both at the slot / version
+// home so two accounts in one install never share a credential (PHNX-3940 T5).
 export const opencodeAdapter = {
     id: 'opencode',
+    applyExecConfigEnv(result, ctx) {
+        if (ctx.versionHome) {
+            result.OPENCODE_CONFIG_DIR = path.join(ctx.versionHome, '.config', 'opencode');
+            result.XDG_DATA_HOME = path.join(ctx.versionHome, '.local', 'share');
+        }
+        stripForeignConfigDir(result, ['OPENCODE_CONFIG_DIR', 'XDG_DATA_HOME']);
+    },
     shimConfigEnvBash() {
         return `
 # OpenCode reads plugins, agents, commands, and other config-directory

package/dist/lib/harness-auth-capabilities.d.ts

@@ -0,0 +1,61 @@
+/**
+ * Per-harness auth capability table (PHNX-3940).
+ *
+ * One row per `ALL_AGENT_IDS` entry. Governs `accounts add` / connect login
+ * argv, identity strength, the durable worker credential (if any), and the
+ * config-dir env that pins a slot. Completeness is pinned by the test against
+ * `ALL_AGENT_IDS` — a new harness without a row is a type error and a failing
+ * test, never a silent skip.
+ *
+ * Values are taken from evidence-harness-auth.md (2026-09-06) and the adapters
+ * under `lib/harness/adapters/`. `LOGIN_INVOCATIONS` is the connect-era subset
+ * (claude, codex) derived from this table so existing connect callers keep
+ * working until T4 folds connect into `accounts add`.
+ */
+import type { AgentId } from './types.js';
+export type HarnessIdentityKind = 'strong' | 'email' | 'opaque';
+/**
+ * Durable worker credential, or `none` when the harness must log in per box.
+ * Codex is both: an API key (portable, bills the API) OR a per-device
+ * ChatGPT-plan device-auth login (the plan seat; never stored in the reserved
+ * store because it is a rotating session).
+ */
+export type HarnessWorkerKind = 'setup-token' | 'none' | `api-key:${string}` | `per-device${'' | `:${string}`}`;
+export type HarnessWorker = HarnessWorkerKind | HarnessWorkerKind[];
+export interface HarnessAuthCapability {
+    /** argv after the harness binary to start native login, or null when there is no finite login command. */
+    login: string[] | null;
+    /** argv to probe login status, or null when the CLI has no status command. */
+    status: string[] | null;
+    identity: HarnessIdentityKind;
+    worker: HarnessWorker;
+    /** Config-dir env that pins a slot, or null when isolation is HOME-swap only. */
+    slotEnv: string | null;
+}
+export declare const HARNESS_AUTH: Record<AgentId, HarnessAuthCapability>;
+export declare function harnessAuth(agent: AgentId): HarnessAuthCapability;
+/** Worker kinds as a flat list (codex's dual path is two entries). */
+export declare function harnessWorkerKinds(agent: AgentId): HarnessWorkerKind[];
+/**
+ * True when this harness has no portable worker credential and must log in
+ * per box. `worker: 'none'` (kimi, antigravity, …) and a sole `per-device…`
+ * kind both count; a dual path like Codex (API key OR device-auth) does not.
+ */
+export declare function harnessWorkerIsPerDevice(agent: AgentId): boolean;
+/**
+ * Native-login invocation per harness. Only harnesses with a REAL, finite login
+ * COMMAND that connect currently drives — connect fails clearly for anything
+ * else rather than faking a flow that never signs the user in. Verified against
+ * the installed CLIs (PHNX-3940): `claude auth login --help` → "Sign in to your
+ * Anthropic account" with `--email`; `codex login` drives the OAuth flow.
+ * Args are the `HARNESS_AUTH.login` values for the same ids.
+ */
+export interface LoginInvocation {
+    /** argv passed to the installed binary to start the native login. */
+    args: string[];
+    /** Flag that pre-fills the login email (appended as `[emailFlag, email]`), when supported. */
+    emailFlag?: string;
+    /** One-line hint shown before the login flow takes over. */
+    hint?: string;
+}
+export declare const LOGIN_INVOCATIONS: Partial<Record<AgentId, LoginInvocation>>;

package/dist/lib/harness-auth-capabilities.js

@@ -0,0 +1,52 @@
+export const HARNESS_AUTH = {
+    claude: { login: ['auth', 'login'], status: ['auth', 'status'], identity: 'strong', worker: 'setup-token', slotEnv: 'CLAUDE_CONFIG_DIR' },
+    codex: { login: ['login'], status: ['login', 'status'], identity: 'strong', worker: ['api-key:OPENAI_API_KEY', 'per-device:device-auth'], slotEnv: 'CODEX_HOME' },
+    grok: { login: ['login'], status: null, identity: 'strong', worker: 'api-key:XAI_API_KEY', slotEnv: 'GROK_HOME' },
+    // auth.json has no email claim; identity is the sorted provider-id join
+    // (`resolveOpenCodeAccountId`). NATIVE_ACCOUNT_CAPABILITIES.opencode.inspection
+    // is already 'opaque'.
+    opencode: { login: ['auth', 'login'], status: ['auth', 'list'], identity: 'opaque', worker: 'api-key:provider', slotEnv: 'XDG_DATA_HOME' },
+    cursor: { login: ['login'], status: ['status'], identity: 'strong', worker: 'api-key:CURSOR_API_KEY', slotEnv: null },
+    // No finite login argv — launch bare `kimi`, then `/login` in the TUI
+    // (`loginHint('kimi') === 'kimi'`, fleet/auth-sync `loginCommand: 'kimi'`).
+    kimi: { login: null, status: null, identity: 'opaque', worker: 'none', slotEnv: 'KIMI_CODE_HOME' },
+    antigravity: { login: null, status: null, identity: 'opaque', worker: 'none', slotEnv: null },
+    droid: { login: null, status: null, identity: 'opaque', worker: 'api-key:FACTORY_API_KEY', slotEnv: null },
+    gemini: { login: null, status: null, identity: 'email', worker: 'none', slotEnv: null },
+    copilot: { login: null, status: null, identity: 'opaque', worker: 'none', slotEnv: 'COPILOT_HOME' },
+    openclaw: { login: null, status: null, identity: 'opaque', worker: 'none', slotEnv: null },
+    amp: { login: null, status: null, identity: 'opaque', worker: 'none', slotEnv: null },
+    goose: { login: null, status: null, identity: 'opaque', worker: 'none', slotEnv: null },
+    hermes: { login: null, status: null, identity: 'opaque', worker: 'none', slotEnv: null },
+    // Auth lives under $XDG_CONFIG_HOME/muse (adapter pins XDG_CONFIG_HOME +
+    // XDG_DATA_HOME). slotEnv names the config pin; T5 must not HOME-swap.
+    muse: { login: null, status: null, identity: 'email', worker: 'none', slotEnv: 'XDG_CONFIG_HOME' },
+    warp: { login: null, status: null, identity: 'opaque', worker: 'none', slotEnv: null },
+};
+export function harnessAuth(agent) {
+    const cap = HARNESS_AUTH[agent];
+    if (!cap)
+        throw new Error(`No harness-auth capability for '${agent}'.`);
+    return cap;
+}
+/** Worker kinds as a flat list (codex's dual path is two entries). */
+export function harnessWorkerKinds(agent) {
+    const worker = harnessAuth(agent).worker;
+    return Array.isArray(worker) ? worker : [worker];
+}
+/**
+ * True when this harness has no portable worker credential and must log in
+ * per box. `worker: 'none'` (kimi, antigravity, …) and a sole `per-device…`
+ * kind both count; a dual path like Codex (API key OR device-auth) does not.
+ */
+export function harnessWorkerIsPerDevice(agent) {
+    return harnessWorkerKinds(agent).every((kind) => kind === 'none' || kind.startsWith('per-device'));
+}
+export const LOGIN_INVOCATIONS = {
+    claude: {
+        args: HARNESS_AUTH.claude.login,
+        emailFlag: '--email',
+        hint: 'Complete the Claude sign-in in your browser.',
+    },
+    codex: { args: HARNESS_AUTH.codex.login },
+};

package/dist/lib/helper-versions.d.ts

@@ -27,7 +27,7 @@
  * never be derived from `getCliVersion()`.
  */
 /** The helpers that have their own release train. */
-export type HelperName = 'menubar' | 'keychain' | 'computer-mac' | 'computer-win';
+export type HelperName = 'menubar' | 'computer-mac' | 'computer-win';
 /** One helper's release identity. */
 export interface HelperRelease {
     /** Tag prefix — the release is `<tagPrefix>/v<version>`. */
@@ -41,9 +41,11 @@ export interface HelperRelease {
 /**
  * Floors, by helper.
  *
- * `menubar` and `keychain` start at 1.0.0 — the first builds published under
- * their own tags rather than the CLI's. They are not "version 1 of the helper";
- * they are version 1 of its independent release train.
+ * `menubar` starts at 1.0.0 — the first build published under its own tag
+ * rather than the CLI's. It is not "version 1 of the helper"; it is version 1
+ * of its independent release train. The keychain helper moved with the
+ * standalone `secrets` engine (PHNX-3989) — it downloads and verifies its own
+ * helper release now, off this table entirely.
  */
 export declare const HELPER_RELEASES: Readonly<Record<HelperName, HelperRelease>>;
 /** The release tag for one helper at one version, e.g. `menubar/v1.0.0`. */

package/dist/lib/helper-versions.js

@@ -29,13 +29,14 @@
 /**
  * Floors, by helper.
  *
- * `menubar` and `keychain` start at 1.0.0 — the first builds published under
- * their own tags rather than the CLI's. They are not "version 1 of the helper";
- * they are version 1 of its independent release train.
+ * `menubar` starts at 1.0.0 — the first build published under its own tag
+ * rather than the CLI's. It is not "version 1 of the helper"; it is version 1
+ * of its independent release train. The keychain helper moved with the
+ * standalone `secrets` engine (PHNX-3989) — it downloads and verifies its own
+ * helper release now, off this table entirely.
  */
 export const HELPER_RELEASES = {
     menubar: { tagPrefix: 'menubar', floor: '1.0.0' },
-    keychain: { tagPrefix: 'keychain', floor: '1.0.0' },
     'computer-mac': { tagPrefix: 'computer-mac', floor: '1.0.0' },
     // The Windows helper is a bare .exe, not an .app bundle, so it does not share
     // helper-download.ts's zip/codesign/notarize machinery -- but it has the same

package/dist/lib/hosts/credential-transport.d.ts

@@ -0,0 +1,10 @@
+/** The host part of an ssh target (`user@host` -> `host`) for known_hosts matching. */
+export declare function hostKeyLookupName(target: string): string;
+/** Refuse durable credential transfer until the destination SSH key is pinned. */
+export declare function assertCredentialTransportHostPinned(target: string, pinned?: boolean): void;
+/**
+ * Resolve a `--device` value to an ssh target string for a credential-carrying
+ * remote operation. Delegates to the same resolver `run --device` uses; on a
+ * miss, treats the value as a raw ssh target and validates it.
+ */
+export declare function resolveHostSshTarget(nameOrAlias: string): Promise<string>;

package/dist/lib/hosts/credential-transport.js

@@ -0,0 +1,37 @@
+/**
+ * Credential transport policy for a fleet host (agents-owned, PHNX-3989).
+ *
+ * Whether a durable credential may leave this device for a given host is
+ * agents fleet policy, not a secrets-engine concern: it hangs off the managed
+ * `known_hosts` pin and the hosts/devices registry. The standalone `secrets`
+ * CLI only carries the bundle once agents-cli has decided the destination is
+ * trustworthy, so these guards live here and are passed INTO the transport,
+ * never re-implemented on the engine side.
+ */
+import { assertValidSshTarget } from '../ssh-exec.js';
+import { resolveHost } from './registry.js';
+import { sshTargetFor } from './types.js';
+import { isHostPinned } from '../devices/known-hosts.js';
+/** The host part of an ssh target (`user@host` -> `host`) for known_hosts matching. */
+export function hostKeyLookupName(target) {
+    return target.split('@').pop() ?? target;
+}
+/** Refuse durable credential transfer until the destination SSH key is pinned. */
+export function assertCredentialTransportHostPinned(target, pinned = isHostPinned(hostKeyLookupName(target))) {
+    if (pinned)
+        return;
+    throw new Error(`Refusing to transfer provider credentials to '${target}' before its SSH host key is pinned. ` +
+        `Connect once with 'agents ssh ${target}' and verify the host, then retry.`);
+}
+/**
+ * Resolve a `--device` value to an ssh target string for a credential-carrying
+ * remote operation. Delegates to the same resolver `run --device` uses; on a
+ * miss, treats the value as a raw ssh target and validates it.
+ */
+export async function resolveHostSshTarget(nameOrAlias) {
+    const host = await resolveHost(nameOrAlias);
+    if (host)
+        return sshTargetFor(host);
+    assertValidSshTarget(nameOrAlias);
+    return nameOrAlias;
+}

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

@@ -170,6 +170,13 @@ export interface DispatchOptions {
  * (remote-cmd.ts) — keep the two in lockstep; run-forwarding.test.ts asserts
  * the table side.
  */
+/** Compose `agent[@version][#account]` so the peer resolves ITS slot (PHNX-3940 T5). */
+export declare function runAgentSpecArg(opts: {
+    agent: string;
+    version?: string;
+    account?: string;
+    accountPicker?: boolean;
+}): string;
 export declare function buildRunForwardedArgs(opts: DispatchOptions): string[];
 export interface InteractiveDispatchOptions {
     agent: string;

package/dist/lib/hosts/dispatch.js

@@ -359,8 +359,19 @@ async function launchDetached(host, target, opts) {
  * (remote-cmd.ts) — keep the two in lockstep; run-forwarding.test.ts asserts
  * the table side.
  */
+/** Compose `agent[@version][#account]` so the peer resolves ITS slot (PHNX-3940 T5). */
+export function runAgentSpecArg(opts) {
+    if (opts.accountPicker)
+        return `${opts.agent}@`;
+    let spec = opts.agent;
+    if (opts.version)
+        spec += `@${opts.version}`;
+    if (opts.account)
+        spec += `#${opts.account}`;
+    return spec;
+}
 export function buildRunForwardedArgs(opts) {
-    const agentArg = opts.version ? `${opts.agent}@${opts.version}` : opts.agent;
+    const agentArg = runAgentSpecArg(opts);
     const args = ['run', agentArg, opts.prompt, '--quiet'];
     if (opts.mode)
         args.push('--mode', opts.mode);
@@ -427,11 +438,7 @@ export function buildInteractiveRunForwardedArgs(opts) {
     if (opts.version && opts.accountPicker) {
         throw new Error('Interactive host dispatch cannot combine an account picker with a version pin');
     }
-    const agentArg = opts.accountPicker
-        ? `${opts.agent}@`
-        : opts.version
-            ? `${opts.agent}@${opts.version}`
-            : opts.agent;
+    const agentArg = runAgentSpecArg(opts);
     const args = ['run', agentArg];
     if (opts.prompt && opts.forceInteractive)
         args.push(opts.prompt);

package/dist/lib/identity/client.d.ts

@@ -10,9 +10,9 @@
  * here and nothing else.
  *
  * The shape mirrors the seams this repo already proved elsewhere —
- * `SyncBackend` (`lib/secrets/sync-backend.ts`) and `CloudProvider`
- * (`lib/cloud/types.ts`) — so a second identity backend, if one is ever
- * needed, is a swap here rather than a sweep across commands.
+ * the bounded secrets process client (`lib/secrets-client.ts`) and
+ * `CloudProvider` (`lib/cloud/types.ts`) — so a second identity backend, if
+ * one is ever needed, is a swap here rather than a sweep across commands.
  */
 /**
  * Where the account backend lives. Config, never a literal at a call site.

package/dist/lib/identity/client.js

@@ -10,9 +10,9 @@
  * here and nothing else.
  *
  * The shape mirrors the seams this repo already proved elsewhere —
- * `SyncBackend` (`lib/secrets/sync-backend.ts`) and `CloudProvider`
- * (`lib/cloud/types.ts`) — so a second identity backend, if one is ever
- * needed, is a swap here rather than a sweep across commands.
+ * the bounded secrets process client (`lib/secrets-client.ts`) and
+ * `CloudProvider` (`lib/cloud/types.ts`) — so a second identity backend, if
+ * one is ever needed, is a swap here rather than a sweep across commands.
  */
 import * as fs from 'fs';
 import * as path from 'path';

package/dist/lib/installations/index.d.ts

@@ -8,7 +8,7 @@
  * per-installation isolation track consumes exactly this).
  */
 export { type Installation, type InstallationRelease, type UpdateOutcome, type UpdateStrategyId, type UpdatePolicy, } from './types.js';
-export { createInstallation, listInstallations, recordRelease, } from './store.js';
+export { createInstallation, listInstallations, recordRelease, MANAGED_INSTALLATION_LABEL, resolveManagedInstallation, ensureHarnessInstallation, type EnsureHarnessInstallationResult, } from './store.js';
 export { describeInstallation, resolveInstallation, type ResolveInstallationOptions, } from './resolve.js';
 export { selectUpdateStrategy, supportsPinnedUpdate, type UpdateStrategy, } from './strategies.js';
 export { updateInstallation, type UpdateInstallationOptions } from './update.js';

package/dist/lib/installations/index.js

@@ -7,7 +7,7 @@
  * it, so the internal split can change without breaking callers (the Cursor
  * per-installation isolation track consumes exactly this).
  */
-export { createInstallation, listInstallations, recordRelease, } from './store.js';
+export { createInstallation, listInstallations, recordRelease, MANAGED_INSTALLATION_LABEL, resolveManagedInstallation, ensureHarnessInstallation, } from './store.js';
 export { describeInstallation, resolveInstallation, } from './resolve.js';
 export { selectUpdateStrategy, supportsPinnedUpdate, } from './strategies.js';
 export { updateInstallation } from './update.js';

package/dist/lib/installations/migrate.js

@@ -2366,4 +2366,13 @@ export async function runMigration() {
     catch {
         // best-effort — a migration must never fail because tmux wasn't reachable
     }
+    // PHNX-3940 T7: report leftover per-account installations. Dry-run only —
+    // moving homes requires an explicit `agents accounts migrate --apply`.
+    try {
+        const { reportAccountSlotMigrationOnUpgrade } = await import('../accounts/migrate.js');
+        await reportAccountSlotMigrationOnUpgrade();
+    }
+    catch {
+        // best-effort — a corrupt install must not block the rest of upgrade
+    }
 }

package/dist/lib/installations/resolve.js

@@ -21,7 +21,7 @@ export class InstallationNotFoundError extends Error {
         // Nothing installed is a different problem from "your selector missed", and
         // the remedy differs — say which one it is rather than printing an empty list.
         super(available.length === 0
-            ? `No ${AGENTS[agent].name} installations are managed by agents-cli. Install one with: agents add ${agent}@latest`
+            ? `No ${AGENTS[agent].name} installations are managed by agents-cli. Install one with: agents add ${agent}`
             : `No ${AGENTS[agent].name} installation matches '${selector}'. Installed: ${available.map((i) => describeInstallation(i)).join(', ')}`);
         this.agent = agent;
         this.selector = selector;

package/dist/lib/installations/shims.d.ts

@@ -201,6 +201,21 @@ export declare const CONFIG_ENV_ISOLATED_AGENTS: readonly AgentId[];
  * separate from the user's real `~/.<agent>`. See {@link CONFIG_ENV_ISOLATED_AGENTS}.
  */
 export declare function supportsIsolatedInstall(agent: AgentId): boolean;
+/**
+ * Harnesses that isolate by symlink-adopting `~/.<config>` rather than a
+ * config-dir env (PHNX-3940 T5). One active slot per device; `accounts default`
+ * repoints the adopted symlink under the auth-op lock.
+ */
+export declare function isSymlinkAdoptedHarness(agent: AgentId): boolean;
+/**
+ * Repoint this harness's adopted `~/.<config>` symlink at `home`'s config dir.
+ * No-op for env-isolated harnesses. Fails loud when the adopted path is a real
+ * directory rather than a symlink — adopting that is `agents use`, not default.
+ */
+export declare function repointAdoptedConfigToHome(agent: AgentId, home: string): {
+    success: boolean;
+    error?: string;
+};
 /**
  * Generate a versioned alias script that directly execs a specific version.
  * e.g., claude@2.0.65 -> directly runs that version's binary
@@ -343,10 +358,12 @@ export declare function listShimFileNames(): string[];
 /**
  * Prune a stale, orphaned shim: one that is NOT a managed agent shim and NOT a user
  * alias, whose baked `AGENTS_BIN` points at an install that no longer exists. These
- * are legacy `exec "$AGENTS_BIN" <cmd>` command shims (browser/secrets/sessions/…)
- * left behind by a removed install — the current source never generates them, and
- * they either die with `exit 127` or shadow the real package bin on PATH. Only
- * removed when the baked target is gone, so a working shim is never touched.
+ * are `exec "$AGENTS_BIN" <cmd>` command shims (browser/sessions/pty/teams) that
+ * `scripts/postinstall.js` writes for the LIVE install; one baked at a removed
+ * install either dies with `exit 127` or shadows the real package bin on PATH.
+ * Only removed when the baked target is gone, so a working shim is never touched —
+ * except the `LEGACY_SHIMS_ALWAYS_PRUNED` set, which cannot work at all (and which
+ * postinstall no longer writes).
  * Returns true if removed.
  */
 export declare function pruneOrphanedCommandShim(fileName: string): boolean;