import { execFileSync } from "child_process";
import { type ProviderName } from "./providers";
export declare const isWindows: boolean;
export declare function clearClaudeExeCache(): void;
export declare function resolveClaudeExe(): string;
export declare function clearCodexExeCache(): void;
export declare function resolveCodexExe(): string;
export declare function clearCursorExeCache(): void;
export declare function resolveCursorExe(): string;
/**
 * Where `exe` — a resolver's output — actually lives, or null if nowhere.
 *
 * A value carrying a path separator is checked directly; a bare command name is
 * searched along PATH exactly the way execvp will search it. node-pty inherits
 * the streamer's own environment (`buildSpawnEnv`), so the PATH walked here is
 * the PATH the spawned child gets — which is what makes this predictive of the
 * spawn rather than merely correlated with it.
 */
export declare function locateExecutable(exe: string): string | null;
/** Where this provider's CLI lives on this machine, or null if it is absent. */
export declare function locateProviderExe(provider: ProviderName): string | null;
type SyncOptions = Parameters<typeof execFileSync>[2];
export declare function execHidden(file: string, args: string[], opts?: SyncOptions & {
    encoding: "utf-8";
}): string;
export {};
//# sourceMappingURL=platform.d.ts.map