import { readPersistedSetupPreferencesSync, readPersistedSetupScopeSync } from "./setup-preferences.js";
export declare const readPersistedSetupPreferences: typeof readPersistedSetupPreferencesSync;
export declare const readPersistedSetupScope: typeof readPersistedSetupScopeSync;
export declare function resolveProjectLocalCodexHomeForLaunch(cwd: string, env?: NodeJS.ProcessEnv): string | undefined;
export declare function resolveCodexHomeForLaunch(cwd: string, env?: NodeJS.ProcessEnv): string | undefined;
export declare function resolveCodexConfigPathForLaunch(cwd: string, env?: NodeJS.ProcessEnv): string;
/**
 * Decide what CODEX_HOME, if any, should be exported into a child team
 * worker's environment (issue #3629).
 *
 * - An explicit CODEX_HOME from the caller is authoritative and is passed
 *   through unchanged.
 * - A project-scope home derived from <project>/.codex is NOT exported.
 *   Exporting it makes the worker's own launch treat it as an explicit
 *   CODEX_HOME with no credentials (401) and disables the worker's project
 *   scope resolution. Leaving it unset lets the worker's `omx` process
 *   resolve project scope and seed credential provenance itself, exactly
 *   like a leader launch.
 */
export declare function resolveCodexHomeForChildExport(env?: NodeJS.ProcessEnv): string | undefined;
//# sourceMappingURL=codex-home.d.ts.map