/**
 * Detect the current IDE from environment variables.
 * Returns the IDE key (e.g., "vscode", "cursor") or null if unknown.
 *
 * Detection strategy (in priority order):
 *   1. Explicit env vars set only by a specific IDE (most reliable)
 *   2. process.execPath / argv[0] inspection for VS Code forks
 *   3. PATH / VSCODE_CWD string matching (fallback, fragile)
 */
export declare function detectCurrentIde(): string | null;
/**
 * Resolve the effective list of global config file paths for an IDE.
 * For most IDEs this is just `ide.scopes.global`.
 * For IDEs with `resolveGlobalPaths` (e.g. Android Studio with versioned dirs)
 * that function is called instead, returning all discovered install paths.
 */
export declare function resolveIdeGlobalPaths(ide: import("./ide-configs.js").IdeDefinition): string[];
/**
 * Scan all IDE_CONFIGS to find which IDEs appear to be installed on this machine.
 *
 * FLAW-9 FIX: The old code treated "parent dir exists" as a detection signal,
 * causing false positives for:
 *   - Visual Studio: ~/.mcp.json parent is HOME — always exists
 *   - Cline: parent is %APPDATA%\Code\... which exists when VS Code is installed
 *
 * New rule: an IDE is detected only when:
 *   (a) Its config file itself exists (previously configured), OR
 *   (b) Its parent dir is at least 2 path segments deeper than a known root
 *       (HOME or APPDATA) AND exists — this filters out shallow paths like
 *       ~/.mcp.json whose parent is just the home directory.
 *
 * An IDE is considered present if any of its global paths passes these checks.
 */
export declare function detectInstalledIdes(): string[];
//# sourceMappingURL=ide-detector.d.ts.map