fix(setup): register a stable launcher when run through bunx (#1731)

Setup run through bunx or bun x registered the bin inside bun's temporary
package cache. Detect bun's package-runner launch from npm_command=exec
with a bun user agent and register the pinned bunx launcher, wrapped in
cmd.exe on Windows like the npx launcher. Doctor, update maintenance and
uninstall recognize it as REA-owned, and setup's printed commands name
the runner that launched it.

Read the runner variables case-insensitively on Windows, where the CLI
environment snapshot upper-cases variable names and setup run through
npx also fell back to the cache path.

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>
This commit is contained in:
xeropresence
2026-10-11 19:17:15 +08:00
committed by GitHub
co-authored by morluto
parent 3a17882cc4
commit d412def722
14 changed files with 317 additions and 98 deletions
+5 -2
View File
@@ -16,6 +16,7 @@ import type {
SetupResult,
} from "../application/SetupTypes.js";
import { SUPPORTED_CLIENT_DEFINITIONS } from "../application/SupportedClients.js";
import { invokingPackageRunner } from "../application/ClientRegistrationIdentity.js";
const clientDisplayNames: ReadonlyMap<string, string> = new Map(
SUPPORTED_CLIENT_DEFINITIONS.map(({ name, displayName }) => [
@@ -224,8 +225,10 @@ const renderKeyboardHelp = (accessible: boolean): void => {
);
};
const cliInvocation = (environment: Readonly<NodeJS.ProcessEnv>): string =>
environment.npm_command === "exec" ? "npx rea-agents" : "rea";
const cliInvocation = (environment: Readonly<NodeJS.ProcessEnv>): string => {
const runner = invokingPackageRunner(environment);
return runner === undefined ? "rea" : `${runner} rea-agents`;
};
const renderReadyCapabilities = (
result: SetupResult,