export interface BuildBotmuxCommandInput {
    electronExecPath: string;
    cliPath: string;
    botmuxHome: string;
    args: string[];
    baseEnv: NodeJS.ProcessEnv;
}
export interface BotmuxCommand {
    command: string;
    args: string[];
    env: NodeJS.ProcessEnv;
}
export interface BuildExternalBotmuxCommandInput {
    binPath: string;
    botmuxHome: string;
    args: string[];
    baseEnv: NodeJS.ProcessEnv;
    pathEnv?: string;
}
export interface BuildBundledBotmuxCommandInput {
    nodePath: string;
    cliPath: string;
    botmuxHome: string;
    args: string[];
    baseEnv: NodeJS.ProcessEnv;
    /** Probed user shell PATH (zsh/bash, profile+rc) — see probeShellPathEnv. */
    pathEnv?: string;
}
export declare function buildBotmuxCommand(input: BuildBotmuxCommandInput): BotmuxCommand;
export declare function buildBundledBotmuxCommand(input: BuildBundledBotmuxCommandInput): BotmuxCommand;
export declare function buildExternalBotmuxCommand(input: BuildExternalBotmuxCommandInput): BotmuxCommand;
/**
 * PATH for anything spawned on behalf of the bundled runtime (daemon start and
 * pm2 contact alike — pm2's daemon env sticks and propagates into resurrected
 * apps, so BOTH chains must agree on ordering or which `node` a per-bot CLI
 * gets would depend on pm2 startup order). User shell PATH first: their
 * nvm/fnm node keeps winning like in a terminal; the bundled node dir is only
 * the fallback for `#!/usr/bin/env node` when the user has no node at all.
 * Callers never rely on this PATH to locate node/pm2 themselves — both are
 * invoked via absolute paths.
 */
export declare function buildBundledPath(current: string | undefined, nodePath: string, pathEnv: string | undefined): string;
//# sourceMappingURL=node-command.d.ts.map