/**
 * Browser Auth Command
 *
 * Sets up browser auth for browser-based connectors by launching a dedicated
 * Chrome with remote debugging and storing its CDP endpoint on the auth
 * profile. The connector attaches over CDP at sync time (and harvests fresh
 * cookies from that live session for the headless fallback). There is no
 * profile-cookie copying — attaching to a real, logged-in Chrome is the only
 * capture path.
 */
/**
 * The auth_data payload we write to the auth profile after a successful
 * CDP launch. Extracted so the unit test can pin its shape without
 * spawning Chrome — see cli-ux.test.ts. The crucial invariant is that
 * `user_data_dir` is NOT present: the connector-side cascade
 * (acquire.ts / browser-network.ts / browser-scraper-utils.ts) prefers
 * userDataDir over cdp_url and tries Playwright launchPersistentContext,
 * which can't open a profile dir held by the dedicated Chrome we just
 * launched. cdp_url alone keeps sync attaching live.
 */
export declare function buildBrowserAuthData(opts: {
    cdpUrl: string;
    profileName: string;
    capturedAt: string;
}): {
    cdp_url: string;
    captured_at: string;
    captured_via: "cli";
    browser_profile: string;
};
export interface BrowserAuthOptions {
    connector: string;
    domains?: string;
    authProfileSlug?: string;
    remoteDebugPort?: string;
    dedicatedProfile?: string;
    check?: boolean;
}
export declare function captureBrowserAuth(opts: BrowserAuthOptions): Promise<void>;
//# sourceMappingURL=browser-auth-cmd.d.ts.map