@phnx-labs/agents-cli 1.20.72 → 1.20.73

package/dist/lib/types.d.ts

@@ -508,6 +508,29 @@ export interface VersionResources {
     permissions?: ResourcePattern[];
     mcp?: ResourcePattern[];
 }
+/** Resource-kind selectors controlled by top-level resource profiles. */
+export interface ResourceProfilePreset {
+    description?: string;
+    commands?: ResourcePattern[];
+    skills?: ResourcePattern[];
+    hooks?: ResourcePattern[];
+    subagents?: ResourcePattern[];
+    plugins?: ResourcePattern[];
+    workflows?: ResourcePattern[];
+    permissions?: ResourcePattern[];
+    mcp?: ResourcePattern[];
+    /** Rule preset name to compose while this profile is active. */
+    rules?: string;
+    /** Alias for rules, accepted so YAML can mirror VersionResources naming. */
+    rulesPreset?: string;
+    /** Secrets bundle names, or "*" for every bundle. */
+    secrets?: string[];
+}
+/** Top-level profiles/presets that switch the resolved resource view. */
+export interface ResourceProfilesConfig {
+    active?: string;
+    presets?: Record<string, ResourceProfilePreset>;
+}
 /** A userConfig field declared in a plugin manifest. */
 export interface PluginUserConfigField {
     key: string;
@@ -644,6 +667,28 @@ export interface ExtraRepoConfig {
     path?: string;
     enabled: boolean;
 }
+/**
+ * A white-label brand — a personally-named CLI (e.g. `jack`) that IS agents-cli,
+ * minted by `agents setup mine` / `agents mine`. The brand's shim exports
+ * `AGENTS_BRAND=<name>`; the entrypoint reads it to present under this name and
+ * apply the customization below. Portable user config — rides `agents repo
+ * push/pull`. See lib/brand.ts.
+ */
+export interface BrandConfig {
+    /** The brand name; also the binary name on PATH. */
+    name: string;
+    /** Built-in top-level commands this brand hides/disables (e.g. `["teams"]`). */
+    disabledCommands?: string[];
+    /**
+     * Resource-profile preset this brand pins (a key in `profiles.presets`). When
+     * the CLI runs under this brand, that preset becomes the active profile, so
+     * skills/plugins/mcp/hooks/etc. filter to the brand's curated set. Defaults to
+     * `mine-<name>`.
+     */
+    profile?: string;
+    /** False to keep the config but stop minting/using the brand. */
+    enabled: boolean;
+}
 /** Top-level structure of ~/.agents/.system/agents.yaml -- the CLI's persistent state. */
 export interface Meta {
     agents?: Partial<Record<AgentId, string>>;
@@ -682,6 +727,12 @@ export interface Meta {
         enabled?: BetaFeatureName[];
     };
     registries?: Record<RegistryType, Record<string, RegistryConfig>>;
+    /**
+     * Top-level resource profiles. Activating one filters the resolved resource
+     * set across commands, skills, hooks, rules, MCP, permissions, and secrets.
+     * Model-provider run profiles are separate YAML files under profiles/.
+     */
+    profiles?: ResourceProfilesConfig;
     versions?: Partial<Record<AgentId, Record<string, VersionResources>>>;
     source?: string;
     /**
@@ -696,6 +747,12 @@ export interface Meta {
      * via the `path` field.
      */
     extraRepos?: Record<string, ExtraRepoConfig>;
+    /**
+     * White-label brands keyed by name. Each mints a personally-named binary
+     * (e.g. `jack`) that runs agents-cli under that name with its own disabled
+     * commands + curated resource profile. See lib/brand.ts.
+     */
+    brands?: Record<string, BrandConfig>;
     /**
      * Keys like `skill.hermes` — registries seeded from SEEDED_REGISTRIES exactly
      * once. Tracked so a user `registry remove` won't silently re-seed.
@@ -746,6 +803,22 @@ export interface Meta {
         workerName?: string;
         bucketName?: string;
         domain?: string;
+        /** Cloudflare Web Analytics token injected into published HTML pages. */
+        analyticsToken?: string;
+    };
+    /**
+     * Owner/channel notification config for `agents send` / `agents notify`.
+     * `owner` is the default recipient for `agents notify` (channel + target).
+     * `transports` maps a user-facing channel name to the provider that actually
+     * delivers it — explicit, one provider per channel, no fallback. Omitted keys
+     * default to name-identity (channel `slack` -> provider `slack`).
+     */
+    notify?: {
+        owner?: {
+            channel: string;
+            to: string;
+        };
+        transports?: Record<string, string>;
     };
 }
 /** Persisted agent-host entry in agents.yaml (overlay or inline). */

package/dist/lib/version.d.ts

@@ -1,8 +1,48 @@
+/**
+ * Well-known locations of the `agents` launcher for PATH-less GUI/launchd
+ * processes (the menu-bar helper inherits no login PATH). Also the anchor for
+ * recovering the on-disk install layout when the CLI runs as a Bun single-file
+ * binary — see {@link resolveInstalledLayout}.
+ */
+export declare function resolveAgentsBin(): string | null;
+export interface InstallLayout {
+    /** The install's `dist/` directory (holds `index.js` + `lib/`). */
+    distDir: string;
+    /** The compiled CLI entry, `dist/index.js`. */
+    entryPath: string;
+    /** The shipping `package.json`, `dist/../package.json`. */
+    pkgJsonPath: string;
+}
+/**
+ * Pure derivation (no I/O) of an install's on-disk layout from the realpath of
+ * its `agents` launcher. A launcher lives at `<pkg>/dist/bin/agents`, so two
+ * levels up is `<pkg>/dist`. Exported for unit testing so the dirname chain the
+ * Bun-binary fallback depends on stays locked.
+ */
+export declare function installLayoutFromBin(realBin: string): InstallLayout;
+/**
+ * Resolve the on-disk install layout of the running CLI by following the
+ * `agents` launcher symlink.
+ *
+ * When the CLI runs as a Bun single-file executable, `import.meta.url` points
+ * inside the virtual bundle (`/$bunfs/…`), so sibling-relative resolution can't
+ * see the shipped `package.json`, `dist/index.js`, or `MenubarHelper.app` on
+ * disk. The launcher symlink points at the real files; walk up from it. Returns
+ * null when no launcher is found (dev/tsx runs, or a box without the helper) —
+ * callers keep their in-bundle resolution as the primary path and use this only
+ * as the fallback.
+ */
+export declare function resolveInstalledLayout(): InstallLayout | null;
 /**
  * Resolve the CLI version from the shipping package.json. Used by the daemon
  * to answer `IPCAction: 'version'` and by the client to detect daemon drift —
  * a dev-build CLI talking to a launchd-managed registry daemon would silently
  * get stale behavior without this check.
+ *
+ * Primary read is relative to this module; when that fails (the Bun single-file
+ * binary can't read its own bundled package.json), fall back to the on-disk
+ * install found via the launcher symlink so callers like the menu bar don't see
+ * a bogus `unknown`.
  */
 export declare function getCliVersion(): string;
 /**

package/dist/lib/version.js

@@ -1,28 +1,111 @@
 import * as fs from 'fs';
+import * as os from 'os';
 import * as path from 'path';
 import { fileURLToPath } from 'url';
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = path.dirname(__filename);
 let cached = null;
+/** Read a `version` string from a package.json, or null if unreadable. */
+function readVersionAt(pkgPath) {
+    try {
+        const pkg = JSON.parse(fs.readFileSync(pkgPath, 'utf-8'));
+        return String(pkg.version || '') || null;
+    }
+    catch {
+        return null;
+    }
+}
+/**
+ * Well-known locations of the `agents` launcher for PATH-less GUI/launchd
+ * processes (the menu-bar helper inherits no login PATH). Also the anchor for
+ * recovering the on-disk install layout when the CLI runs as a Bun single-file
+ * binary — see {@link resolveInstalledLayout}.
+ */
+export function resolveAgentsBin() {
+    const home = os.homedir();
+    const candidates = [
+        path.join(home, '.local', 'bin', 'agents'),
+        '/opt/homebrew/bin/agents',
+        '/usr/local/bin/agents',
+        path.join(home, '.npm-global', 'bin', 'agents'),
+    ];
+    for (const c of candidates) {
+        try {
+            fs.accessSync(c, fs.constants.X_OK);
+            return c;
+        }
+        catch {
+            /* try next */
+        }
+    }
+    return null;
+}
+/**
+ * Pure derivation (no I/O) of an install's on-disk layout from the realpath of
+ * its `agents` launcher. A launcher lives at `<pkg>/dist/bin/agents`, so two
+ * levels up is `<pkg>/dist`. Exported for unit testing so the dirname chain the
+ * Bun-binary fallback depends on stays locked.
+ */
+export function installLayoutFromBin(realBin) {
+    const distDir = path.dirname(path.dirname(realBin)); // <pkg>/dist/bin/agents -> <pkg>/dist
+    return {
+        distDir,
+        entryPath: path.join(distDir, 'index.js'),
+        pkgJsonPath: path.join(distDir, '..', 'package.json'),
+    };
+}
+/**
+ * Resolve the on-disk install layout of the running CLI by following the
+ * `agents` launcher symlink.
+ *
+ * When the CLI runs as a Bun single-file executable, `import.meta.url` points
+ * inside the virtual bundle (`/$bunfs/…`), so sibling-relative resolution can't
+ * see the shipped `package.json`, `dist/index.js`, or `MenubarHelper.app` on
+ * disk. The launcher symlink points at the real files; walk up from it. Returns
+ * null when no launcher is found (dev/tsx runs, or a box without the helper) —
+ * callers keep their in-bundle resolution as the primary path and use this only
+ * as the fallback.
+ */
+export function resolveInstalledLayout() {
+    const bin = resolveAgentsBin();
+    if (!bin)
+        return null;
+    try {
+        const layout = installLayoutFromBin(fs.realpathSync(bin));
+        // Validate we landed on a real dist (guards an unexpected launcher layout).
+        if (fs.existsSync(layout.entryPath))
+            return layout;
+    }
+    catch {
+        /* ignore */
+    }
+    return null;
+}
 /**
  * Resolve the CLI version from the shipping package.json. Used by the daemon
  * to answer `IPCAction: 'version'` and by the client to detect daemon drift —
  * a dev-build CLI talking to a launchd-managed registry daemon would silently
  * get stale behavior without this check.
+ *
+ * Primary read is relative to this module; when that fails (the Bun single-file
+ * binary can't read its own bundled package.json), fall back to the on-disk
+ * install found via the launcher symlink so callers like the menu bar don't see
+ * a bogus `unknown`.
  */
 export function getCliVersion() {
     if (cached)
         return cached;
-    try {
-        const pkgPath = path.join(__dirname, '..', '..', 'package.json');
-        const pkg = JSON.parse(fs.readFileSync(pkgPath, 'utf-8'));
-        cached = String(pkg.version || 'unknown');
-    }
-    catch {
-        cached = 'unknown';
-    }
+    cached =
+        readVersionAt(path.join(__dirname, '..', '..', 'package.json')) ??
+            readInstalledPackageVersion() ??
+            'unknown';
     return cached;
 }
+/** Version from the on-disk install (Bun-binary fallback). */
+function readInstalledPackageVersion() {
+    const layout = resolveInstalledLayout();
+    return layout ? readVersionAt(layout.pkgJsonPath) : null;
+}
 /**
  * Read the version from package.json on disk every call, bypassing the cache.
  *
@@ -34,12 +117,7 @@ export function getCliVersion() {
  * 'unknown' on any error.
  */
 export function getCliVersionFresh() {
-    try {
-        const pkgPath = path.join(__dirname, '..', '..', 'package.json');
-        const pkg = JSON.parse(fs.readFileSync(pkgPath, 'utf-8'));
-        return String(pkg.version || 'unknown');
-    }
-    catch {
-        return 'unknown';
-    }
+    return (readVersionAt(path.join(__dirname, '..', '..', 'package.json')) ??
+        readInstalledPackageVersion() ??
+        'unknown');
 }

package/dist/lib/versions.d.ts

@@ -415,6 +415,17 @@ export declare function verifyInstalledBinaryLaunches(agent: AgentId, version: s
  *   4. Nothing runnable installed → install `latest`, pin it, return it.
  *   5. Give up → return null (caller surfaces a clear error).
  *
+ * Isolation boundary (both directions — steps 3/4 are the only mutating ones):
+ *   - An ISOLATED target gets step 2 and nothing else. Falling back would let
+ *     `agents run <agent>@<isolated>` silently repoint the user's NORMAL default,
+ *     and installing `latest` would materialize a version they never asked for.
+ *     A failed repair returns null so the caller says so plainly.
+ *   - An isolated version is never a fallback CANDIDATE either, whatever the
+ *     target is: promoting one to the global default is exactly what `agents use`
+ *     refuses and what removeVersion's promotion filter excludes, so it must not
+ *     happen here by the back door (the daemon's launch-health pass calls this
+ *     unattended every ~6h).
+ *
  * Gated to npm-package agents: their native binary ships as an optional per-arch
  * dependency whose tarball can extract partially (interrupted/raced install) —
  * the exact failure this repairs. Agents with a global/native binary (grok,