import { OnDestroy, InjectionToken } from '@angular/core';
import { AparteClient, AparteClientOptions } from '@aparte/core';
import * as i0 from "@angular/core";
/**
 * Injection token for AparteClient configuration. Provided by `provideAparte()`;
 * omit it and the service falls back to `{}`.
 */
export declare const APARTE_CLIENT_OPTIONS: InjectionToken<AparteClientOptions>;
/**
 * AparteAiService
 *
 * Angular service to bridge the UI events with AI Providers.
 * Uses the agnostic `AparteClient` under the hood.
 */
export declare class AparteAiService implements OnDestroy {
    private readonly _clientOptions;
    private readonly _client;
    /**
     * The `AparteClient` this service drives — the same object React's
     * `useAparteClient`, Vue's and Svelte's `createAparteClient` return as
     * `{ client, abort }`. Angular alone kept it private, so the instance was
     * unreachable while each service's docblock called itself the others' equivalent.
     */
    get client(): AparteClient;
    /**
     * Start listening to `aparte-send` events globally.
     * This connects the <aparte-chat> components to the AI Providers.
     *
     * `provideAparte()` calls this for you on app init (its `autoConnect`,
     * on by default). Idempotent — a manual call on top of that is a no-op,
     * so it stays the escape hatch when configuring without `provideAparte`.
     */
    connect(): void;
    /**
     * Stop listening. The client also takes its `keyResolver` back off the config,
     * so a paused bridge no longer answers for keys — a model list refreshed while
     * disconnected sees the config's other key sources only.
     */
    disconnect(): void;
    /**
     * Abort the current AI response and all active tool calls.
     */
    abort(): void;
    ngOnDestroy(): void;
    static ɵfac: i0.ɵɵFactoryDeclaration<AparteAiService, never>;
    static ɵprov: i0.ɵɵInjectableDeclaration<AparteAiService>;
}