import { UIDLAIAssistantChat } from '@teleporthq/teleport-types'; /** * Emits `lib/ai-chat/provider.js` — the chat-completion + embedding shim the * generated AI-chat API routes call. * * Two invariants this file exists to hold: * * 1. **Chat completions follow the chosen provider.** Any provider in the * editor's catalogue can be selected, and each has its own SDK, parameter * names, and — importantly — its own set of parameters it will REJECT. * 2. **Embeddings are always OpenAI.** Knowledge sources are indexed by the * Teleport services worker with OpenAI `text-embedding-3-small` (1536 * dimensions) and stored in `teleport_ai_chat_documents.embedding_json`. * The query vector is compared against those stored vectors, so it has to * come from the same model: a different model with the same width produces * a meaningless similarity, and a different width (Cohere 1024, Gemini 768, * OpenAI large 3072) makes every comparison garbage. Generating embeddings * with the chat provider — which this file used to do for Google, Cohere * and Mistral — silently destroys retrieval. */ export declare function generateProviderCode(chat: UIDLAIAssistantChat): string; /** * ⛔ `openai` is in every entry, not just the OpenAI one: `generateEmbedding` * always calls the OpenAI embeddings API, so the SDK is needed whatever the * chat provider is. */ export declare function getProviderDependencies(provider: string): Record; //# sourceMappingURL=provider-generator.d.ts.map