export interface FlowNodeSearchFieldProps {
    /** Controlled query string — the app applies dimming/filtering itself (see the `.mdx`). */
    value: string;
    onChange: (value: string) => void;
    /** @default 'Search nodes' — CJO's literal placeholder/aria-label (`CanvasChrome.tsx:69,80`). */
    placeholder?: string;
    /**
     * @default false — the field's own open/closed toggle is uncontrolled, matching CJO's local
     * `searchOpen` (`CanvasChrome.tsx:61`). Closing does not clear `value`.
     */
    defaultOpen?: boolean;
    testId?: string;
}
/**
 * The magnifying-glass button + reveal-on-click search input from CJO's top-left canvas chrome
 * (`src/features/journeys/builder/CanvasChrome.tsx:65-91` — inline there, never a standalone
 * component). A plain anchored control — no `@xyflow/react` import — it lives in a `<Panel>`,
 * not inside a node.
 *
 * This component never touches a node/edge array: it only produces a string. What happens to
 * that string (CJO dims non-matching nodes to 30% opacity via `buildCanvasNodes`, rather than
 * filtering them out) is entirely app-side render logic operating on the app's own node array.
 */
export declare function FlowNodeSearchField({ value, onChange, placeholder, defaultOpen, testId, }: FlowNodeSearchFieldProps): import("react/jsx-runtime").JSX.Element;