/**
 * What the *installed* `agy` build supports, discovered from `agy --help` so the
 * backend adapts to whatever version is on PATH instead of hard-coding 1.0.x
 * assumptions. As upstream fixes print-mode (antigravity-cli#7) these flags
 * appear and we automatically prefer the clean paths — JSON on stdout, a
 * caller-known conversation id — over transcript scraping. That is Phase 3's
 * "self-retiring fallback" in code: nothing here needs editing when agy improves.
 *
 * Detection is a best-effort scan of the help text. Every capability defaults to
 * false, so a missing / slow / unusual `agy --help` leaves us behaving exactly as
 * the Phase 1-2 backend did.
 */
export interface AgyCapabilities {
    /** `--output-format` exists and advertises a json mode → we can skip scraping. */
    outputFormatJson: boolean;
    /** `--conversation <id>` exists → sessions can be addressed explicitly. */
    conversationId: boolean;
    /** `--continue`/`-c` exists → "resume latest" is available. */
    continueFlag: boolean;
    /** `--print-timeout` exists → headless runs can bound their own wait. */
    printTimeout: boolean;
    /** Raw help text, kept for diagnostics. */
    raw: string;
}
export declare const NO_AGY_CAPABILITIES: AgyCapabilities;
/** Parse `agy --help` text into a capability set. Pure — unit tested directly. */
export declare function parseAgyHelp(help: string): AgyCapabilities;
/**
 * Probe (once per process) what the installed agy supports. Fail-safe: any
 * problem yields NO_AGY_CAPABILITIES, i.e. the conservative Phase 1-2 behaviour.
 */
export declare function probeAgyCapabilities(): Promise<AgyCapabilities>;
/** Test seam: pin a capability set (or pass nothing to clear the cache). */
export declare function __setAgyCapabilitiesForTest(caps?: AgyCapabilities): void;
//# sourceMappingURL=agyCapabilities.d.ts.map