import type { VendoTheme } from "../../core/apps/index.js";
import type { ReactNode } from "react";
export interface VendoTriggerProps {
    /** The prompt preloaded into the conversation composer — prefilled, never
     *  auto-sent, so a trigger is safe even on destructive prompts. */
    prompt: string;
    /** Optional context appended to the prompt (blank-line separated) — the
     *  record or state on screen, so the agent starts oriented. */
    context?: string;
    /** Button label. Default "Ask Vendo". */
    children?: ReactNode;
    /**
     * This surface's own brand tokens, merged group by group over the provider's
     * resolved theme — the same merge `VendoProvider` does over
     * `defaultVendoTheme`, so with no provider above this merges over the
     * defaults.
     *
     * FRAME ONLY: it styles Vendo's own chrome. A mounted generated view keeps
     * the PROVIDER theme — an iframe-served app is themed over the app
     * transport, and a natively rendered one restates the provider tokens on its
     * own surface root.
     */
    theme?: Partial<VendoTheme>;
}
/**
 * The shelf's "do it with AI" button (ui-usage-dx §2): every host affordance
 * that hands a task to the agent is this piece. Activation opens the most
 * recently mounted conversation surface (the VendoOverlay) with the prompt
 * seeded into the composer.
 *
 * Hosts that want their own element as the trigger skip this component and
 * call `openVendoConversation({ prompt })` from it directly — the same
 * programmatic seam this button uses (the repo's idiom; there is deliberately
 * no render-prop API on chrome, ui-usage-dx §4).
 */
export declare function VendoTrigger({ prompt, context, children, theme }: VendoTriggerProps): import("react").JSX.Element;