import { ButtonProps, ChipProps, IconButtonProps } from '../../components';
export declare const SignalToolApproveButton: import('../../../node_modules/react').ForwardRefExoticComponent<ButtonProps & {
    ownerState?: unknown;
} & import('../../../node_modules/react').RefAttributes<HTMLButtonElement>>;
export declare const SignalToolDenyButton: import('../../../node_modules/react').ForwardRefExoticComponent<ButtonProps & {
    ownerState?: unknown;
} & import('../../../node_modules/react').RefAttributes<HTMLButtonElement>>;
export declare const SignalScrollToBottomButton: import('../../../node_modules/react').ForwardRefExoticComponent<IconButtonProps & {
    ownerState?: unknown;
} & import('../../../node_modules/react').RefAttributes<HTMLButtonElement>>;
/**
 * `Chip`, not `Button` — `ChatSuggestions` items render as rounded pills,
 * and chips are this design system's own idiom for that shape. MUI's `Chip`
 * renders `role="button"` (not a literal `<button>`) once given `onClick`,
 * which is how `SuggestionsRoot` drives it — not a literal DOM `<button>`,
 * but fully accessible and keyboard-operable.
 *
 * `SuggestionItem` passes the suggestion's label as `children` (matching how
 * it'd fill a native `<button>`) — `Chip` only ever renders its `label` prop
 * and explicitly marks `children` unsupported, so map one to the other here
 * or every chip renders empty.
 */
export declare const SignalSuggestionChip: import('../../../node_modules/react').ForwardRefExoticComponent<ChipProps & {
    ownerState?: unknown;
} & import('../../../node_modules/react').RefAttributes<HTMLDivElement>>;