The agent that grows with you
Python aiai-agentai-agentsanthropicchatgptclaudeclaude-codecodexhermeshermes-agentllmnous-researchopenai
export interface RunnableBinaryOptions {
/** Ordered candidate absolute paths, highest preference first. */
candidates: string[]
fileExists: (filePath: string) => boolean
/** Probe: does this candidate actually execute (`<binary> --version`)? */
binaryRuns: (filePath: string) => boolean
}
/**
* Pick the first candidate that both exists on disk and runs, falling back to
* the first that merely exists, then to null.
*
* A file can exist and still be unlaunchable: on macOS an Intel-only binary
* ahead on PATH (Homebrew under Rosetta gone after an OS update) fails at
* spawn time with errno -86 (EBADARCH, "Bad CPU type in executable"), which
* callers then misreport as a network/update-server problem because the
* failure only surfaces when the child is spawned. Existence-only selection
* (`candidates.find(fileExists)`, first PATH hit) commits to the broken
* candidate by construction and never looks at the working one right after it.
*
* The existence-only fallback keeps behaviour unchanged where the probe itself
* cannot run (locked-down execution policy, AV interposing on spawn) rather
* than skipping a binary that would have worked.
*
* Resolution order (first match wins):
* 1. a candidate that exists and runs
* 2. a candidate that merely exists
* 3. null — caller falls back to its own PATH/bare-name resolution
*/
export function selectRunnableBinary(opts: RunnableBinaryOptions): string | null {
const existing = opts.candidates.filter(opts.fileExists)
return existing.find(opts.binaryRuns) || existing[0] || null
}