chat-agent-toolkit 1.2.379 → 1.2.381

package/README.md

@@ -4,7 +4,7 @@
 
 <!-- template-git-repo:badges:start -->
 <p align="center">
-    <a href="https://qwksearch.com/api/docs"><img src="https://img.shields.io/badge/Docs-blue?logo=ReadTheDocs&logoColor=white" alt="Documentation" /></a>
+    <a href="https://qwksearch.com/api"><img src="https://img.shields.io/badge/Docs-blue?logo=ReadTheDocs&logoColor=white" alt="Documentation" /></a>
     <br />
     <a href="https://github.com/OpenSourceAGI/qwksearch-research-agent/stargazers"><img src="https://img.shields.io/github/stars/OpenSourceAGI/qwksearch-research-agent" alt="GitHub Stars" /></a>
     <a href="https://www.npmjs.com/package/chat-agent-toolkit"><img src="https://img.shields.io/npm/dm/chat-agent-toolkit.svg" alt="NPM Monthly Downloads" /></a>

package/dist/chat-agent-toolkit/src/tools/qwksearch-api-tools.d.ts

@@ -81,8 +81,8 @@ export declare const AGENT_TOOLS: ({
         bypassCaptcha: z.ZodDefault<z.ZodOptional<z.ZodBoolean>>;
         sessionId: z.ZodDefault<z.ZodOptional<z.ZodString>>;
         format: z.ZodDefault<z.ZodOptional<z.ZodEnum<{
-            html: "html";
             json: "json";
+            html: "html";
         }>>>;
         scraperUrl: z.ZodOptional<z.ZodString>;
         scraperApiKey: z.ZodOptional<z.ZodString>;

package/dist/chat-agent-toolkit/src/tools/search/doc-utils.d.ts

@@ -35,11 +35,42 @@ export type UploadFileLoader = (fileId: string) => Promise<LoadedUpload | null>;
  * the S3-credentials fallback.
  */
 export declare function registerUploadFileLoader(loader: UploadFileLoader): void;
+/**
+ * Resolves every uploaded fileId once, in order.
+ *
+ * Two things here are deliberate, and both are about the 128MB an edge isolate
+ * gets. An attachment arrives as a JSON object whose `image` field is a data
+ * URL, so an 8MB picture is ~11MB of base64 that exists twice while it is
+ * parsed — and a request may carry ten of them. So: resolved **sequentially**,
+ * to keep one raw payload live at a time rather than ten; and resolved **once**
+ * per request, with the result shared by the reranker and the image loader,
+ * which between them used to fetch and parse every attachment twice over.
+ *
+ * Duplicate ids in the list collapse to one fetch. A file that cannot be
+ * resolved is dropped, exactly as before.
+ */
+export declare function loadUploads(fileIds: string[], r2Credentials?: R2CredentialsInput): Promise<LoadedUpload[]>;
+/**
+ * Picks the image attachments out of already-resolved uploads, ready to be
+ * passed to the LLM as image content parts. Documents and images stored
+ * without inline data carry no `image`, so they drop out here.
+ */
+export declare function selectUploadImages(uploads: LoadedUpload[]): UploadImageAttachment[];
 /**
  * Resolves image attachments for the given uploaded fileIds so they can be
  * passed to the LLM as image content parts. Non-image uploads (documents) and
  * images stored without inline data are skipped.
+ *
+ * Pass `preloaded` when the uploads have already been resolved for this
+ * request — {@link loadUploads} explains why fetching them twice is worth
+ * avoiding.
+ */
+export declare function loadUploadImages(fileIds: string[], r2Credentials?: R2CredentialsInput, preloaded?: LoadedUpload[]): Promise<UploadImageAttachment[]>;
+/**
+ * Builds the answer context: uploaded file content first, then web results.
+ *
+ * Pass `preloaded` when the uploads have already been resolved for this
+ * request — see {@link loadUploads}.
  */
-export declare function loadUploadImages(fileIds: string[], r2Credentials?: R2CredentialsInput): Promise<UploadImageAttachment[]>;
-export declare function rerankDocs(query: string, docs: Document[], fileIds: string[], optimizationMode: "speed" | "balanced" | "quality", r2Credentials?: R2CredentialsInput): Promise<Document[]>;
+export declare function rerankDocs(query: string, docs: Document[], fileIds: string[], optimizationMode: "speed" | "balanced" | "quality", r2Credentials?: R2CredentialsInput, preloaded?: LoadedUpload[]): Promise<Document[]>;
 export declare function processDocs(docs: Document[]): string;

package/dist/chat-agent-toolkit/src/tools/search/index.d.ts

@@ -3,11 +3,11 @@
  * @description Meta search agent tools for AI-powered web search and research
  */
 export { default as MetaSearchAgent } from './metaSearchAgent';
-export type { MetaSearchAgentType, Config, ChatTurnMessage, SearchingEvent, FewShotExample } from './meta-search-types';
+export type { MetaSearchAgentType, Config, ChatTurnMessage, DrainableEmitter, SearchingEvent, FewShotExample } from './meta-search-types';
 export { searchHandlers, createSearchHandlers } from './search-handlers';
 export { default as generateSuggestions } from './suggestionGeneratorAgent';
 export { groupAndSummarizeDocs } from './link-summarizer';
 export type { Document } from './document';
 export { splitTextIntoChunks } from './document';
-export { buildFallbackDocs, rerankDocs, processDocs, normalizeSourcesOutput, registerUploadFileLoader, loadUploadImages } from './doc-utils';
+export { buildFallbackDocs, rerankDocs, processDocs, normalizeSourcesOutput, registerUploadFileLoader, loadUploads, loadUploadImages, selectUploadImages } from './doc-utils';
 export type { UploadFileLoader, LoadedUpload, UploadImageAttachment } from './doc-utils';

package/dist/chat-agent-toolkit/src/tools/search/meta-search-types.d.ts

@@ -7,10 +7,23 @@ export interface ChatTurnMessage {
 }
 /** A `[role, content]` tuple used for few-shot prompt examples. */
 export type FewShotExample = [role: "user" | "assistant", content: string];
+/**
+ * The pipeline's event emitter, plus the hook a consumer uses to push back.
+ *
+ * `emit()` is synchronous, so the answer loop would otherwise pull the entire
+ * model stream into memory at the model's pace while the consumer writes it
+ * out at the client's pace. A consumer that can be slow (an HTTP response
+ * stream, say) assigns `waitForDrain`; the loop awaits it between chunks and
+ * so advances no faster than the consumer does. Leaving it unset keeps the
+ * unthrottled behaviour, which is what an in-process consumer wants.
+ */
+export interface DrainableEmitter extends EventEmitter {
+    waitForDrain?: () => Promise<void>;
+}
 export interface MetaSearchAgentType {
     searchAndAnswer: (message: string, history: ChatTurnMessage[], llm: LanguageModel, optimizationMode: "speed" | "balanced" | "quality", fileIds: string[], systemInstructions: string, category?: string, sourceExtractionEnabled?: boolean, thinkingTimeLimit?: number, 
     /** User-authored replacement for the focus mode's query-expansion prompt. */
-    queryExpansionPrompt?: string) => Promise<EventEmitter>;
+    queryExpansionPrompt?: string) => Promise<DrainableEmitter>;
 }
 /** Emitted on the EventEmitter data channel to report live search progress. */
 export interface SearchingEvent {

package/dist/chat-agent-toolkit/src/tools/search/metaSearchAgent.d.ts

@@ -1,7 +1,7 @@
 import { LanguageModel } from 'ai';
 import { default as EventEmitter } from 'events';
 import { Config, ChatTurnMessage, MetaSearchAgentType } from './meta-search-types';
-export type { MetaSearchAgentType, Config } from './meta-search-types';
+export type { MetaSearchAgentType, Config, DrainableEmitter } from './meta-search-types';
 declare class MetaSearchAgent implements MetaSearchAgentType {
     private config;
     constructor(config: Config);