@tyvm/knowhow 0.0.89 → 0.0.90

package/ts_build/src/processors/tools/tailToolResponse.d.ts

@@ -2,5 +2,7 @@ import { Tool } from "../../clients";
 export interface TailOptions {
     lines?: number;
 }
-export declare function executeTail(data: string, toolCallId: string, availableIds: string[], options?: TailOptions): Promise<string>;
+export declare function executeTail(data: string, toolCallId: string, availableIds: string[], options?: TailOptions, toolNameMap?: {
+    [toolCallId: string]: string;
+}): Promise<string>;
 export declare const tailToolResponseDefinition: Tool;

package/ts_build/src/processors/tools/tailToolResponse.js

@@ -1,9 +1,15 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.tailToolResponseDefinition = exports.executeTail = void 0;
-async function executeTail(data, toolCallId, availableIds, options) {
+async function executeTail(data, toolCallId, availableIds, options, toolNameMap) {
     if (data === null || data === undefined) {
-        return `Error: No tool response found for toolCallId "${toolCallId}". Available IDs: ${availableIds.join(", ")}`;
+        const idList = availableIds
+            .map((id) => {
+            const name = toolNameMap?.[id];
+            return name ? `${id} (${name})` : id;
+        })
+            .join("\n  - ");
+        return `Error: No tool response found for toolCallId "${toolCallId}". Call listStoredToolResponses to see all available responses with their tool names.\n\nAvailable toolCallIds:\n  - ${idList || "(none)"}`;
     }
     try {
         const lines = data.split("\n");

package/ts_build/src/processors/tools/tailToolResponse.js.map

@@ -1 +1 @@
-{"version":3,"file":"tailToolResponse.js","sourceRoot":"","sources":["../../../../src/processors/tools/tailToolResponse.ts"],"names":[],"mappings":";;;AASO,KAAK,UAAU,WAAW,CAC/B,IAAY,EACZ,UAAkB,EAClB,YAAsB,EACtB,OAAqB;IAErB,IAAI,IAAI,KAAK,IAAI,IAAI,IAAI,KAAK,SAAS,EAAE;QACvC,OAAO,iDAAiD,UAAU,qBAAqB,YAAY,CAAC,IAAI,CACtG,IAAI,CACL,EAAE,CAAC;KACL;IAED,IAAI;QACF,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;QAC/B,MAAM,QAAQ,GAAG,OAAO,EAAE,KAAK,IAAI,EAAE,CAAC;QAGtC,IAAI,QAAQ,IAAI,CAAC,EAAE;YACjB,OAAO,EAAE,CAAC;SACX;QAGD,MAAM,QAAQ,GAAG,IAAI,CAAC,GAAG,CAAC,CAAC,EAAE,KAAK,CAAC,MAAM,GAAG,QAAQ,CAAC,CAAC;QACtD,MAAM,SAAS,GAAG,KAAK,CAAC,KAAK,CAAC,QAAQ,CAAC,CAAC;QAGxC,MAAM,SAAS,GAAG,SAAS,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,GAAG,EAAE,EAAE;YAC5C,MAAM,OAAO,GAAG,QAAQ,GAAG,GAAG,GAAG,CAAC,CAAC;YACnC,OAAO,GAAG,OAAO,KAAK,IAAI,EAAE,CAAC;QAC/B,CAAC,CAAC,CAAC;QAEH,OAAO,SAAS,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;KAC7B;IAAC,OAAO,KAAU,EAAE;QACnB,OAAO,eAAe,KAAK,CAAC,OAAO,EAAE,CAAC;KACvC;AACH,CAAC;AAnCD,kCAmCC;AAEY,QAAA,0BAA0B,GAAS;IAC9C,IAAI,EAAE,UAAU;IAChB,QAAQ,EAAE;QACR,IAAI,EAAE,kBAAkB;QACxB,WAAW,EACT,8MAA8M;QAChN,UAAU,EAAE;YACV,IAAI,EAAE,QAAQ;YACd,UAAU,EAAE,IAAI;YAChB,UAAU,EAAE;gBACV,UAAU,EAAE;oBACV,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,4CAA4C;iBAC1D;gBACD,OAAO,EAAE;oBACP,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,8FAA8F;oBAC3G,UAAU,EAAE;wBACV,KAAK,EAAE;4BACL,IAAI,EAAE,QAAQ;4BACd,WAAW,EAAE,sDAAsD;yBACpE;qBACF;iBACF;aACF;YACD,QAAQ,EAAE,CAAC,YAAY,CAAC;SACzB;KACF;CACF,CAAC"}
+{"version":3,"file":"tailToolResponse.js","sourceRoot":"","sources":["../../../../src/processors/tools/tailToolResponse.ts"],"names":[],"mappings":";;;AASO,KAAK,UAAU,WAAW,CAC/B,IAAY,EACZ,UAAkB,EAClB,YAAsB,EACtB,OAAqB,EACrB,WAA8C;IAE9C,IAAI,IAAI,KAAK,IAAI,IAAI,IAAI,KAAK,SAAS,EAAE;QACvC,MAAM,MAAM,GAAG,YAAY;aACxB,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE;YACV,MAAM,IAAI,GAAG,WAAW,EAAE,CAAC,EAAE,CAAC,CAAC;YAC/B,OAAO,IAAI,CAAC,CAAC,CAAC,GAAG,EAAE,KAAK,IAAI,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC;QACvC,CAAC,CAAC;aACD,IAAI,CAAC,QAAQ,CAAC,CAAC;QAClB,OAAO,iDAAiD,UAAU,wHAAwH,MAAM,IAAI,QAAQ,EAAE,CAAC;KAChN;IAED,IAAI;QACF,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;QAC/B,MAAM,QAAQ,GAAG,OAAO,EAAE,KAAK,IAAI,EAAE,CAAC;QAGtC,IAAI,QAAQ,IAAI,CAAC,EAAE;YACjB,OAAO,EAAE,CAAC;SACX;QAGD,MAAM,QAAQ,GAAG,IAAI,CAAC,GAAG,CAAC,CAAC,EAAE,KAAK,CAAC,MAAM,GAAG,QAAQ,CAAC,CAAC;QACtD,MAAM,SAAS,GAAG,KAAK,CAAC,KAAK,CAAC,QAAQ,CAAC,CAAC;QAGxC,MAAM,SAAS,GAAG,SAAS,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,GAAG,EAAE,EAAE;YAC5C,MAAM,OAAO,GAAG,QAAQ,GAAG,GAAG,GAAG,CAAC,CAAC;YACnC,OAAO,GAAG,OAAO,KAAK,IAAI,EAAE,CAAC;QAC/B,CAAC,CAAC,CAAC;QAEH,OAAO,SAAS,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;KAC7B;IAAC,OAAO,KAAU,EAAE;QACnB,OAAO,eAAe,KAAK,CAAC,OAAO,EAAE,CAAC;KACvC;AACH,CAAC;AAxCD,kCAwCC;AAEY,QAAA,0BAA0B,GAAS;IAC9C,IAAI,EAAE,UAAU;IAChB,QAAQ,EAAE;QACR,IAAI,EAAE,kBAAkB;QACxB,WAAW,EACT,8MAA8M;QAChN,UAAU,EAAE;YACV,IAAI,EAAE,QAAQ;YACd,UAAU,EAAE,IAAI;YAChB,UAAU,EAAE;gBACV,UAAU,EAAE;oBACV,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,4CAA4C;iBAC1D;gBACD,OAAO,EAAE;oBACP,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,8FAA8F;oBAC3G,UAAU,EAAE;wBACV,KAAK,EAAE;4BACL,IAAI,EAAE,QAAQ;4BACd,WAAW,EAAE,sDAAsD;yBACpE;qBACF;iBACF;aACF;YACD,QAAQ,EAAE,CAAC,YAAY,CAAC;SACzB;KACF;CACF,CAAC"}

package/autodoc/chat.mdx

@@ -1,20 +0,0 @@
-This command line tool allows users to provide various inputs to interact with an AI assistant. Here are the key inputs a user can provide:
-
-1. **Commands**: Users can input specific commands to control the tool's behavior. The available commands include:
-   - `agent`: Toggle the use of a specific agent.
-   - `agents`: List and select from available agents.
-   - `debug`: Toggle debug mode.
-   - `multi`: Enable or disable multi-line input.
-   - `search`: Search for embeddings.
-   - `clear`: Clear the chat history.
-   - `exit`: Exit the tool.
-
-2. **Questions or Prompts**: Users can ask questions or provide prompts to the AI assistant. The tool will process these inputs and generate responses based on the provided embeddings and context.
-
-3. **Embedding Options**: When searching for embeddings, users can input options like `next`, `exit`, `embeddings`, and `use` to navigate through and select embeddings.
-
-4. **Agent Selection**: Users can select different agents to handle their queries by listing available agents and choosing one.
-
-5. **Chat History**: Users can view and clear the chat history to manage the context of their interactions.
-
-These inputs allow users to interact with the AI assistant in a flexible and controlled manner, leveraging various commands and options to get the desired responses.

package/autodoc/cli.mdx

@@ -1,11 +0,0 @@
-This command line tool accepts the following inputs (commands):
-
-1. **init**: Initializes the tool.
-2. **generate**: Generates some output.
-3. **embed**: Embeds data.
-4. **upload**: Uploads data.
-5. **download**: Downloads data.
-6. **upload:openai**: Uploads data to OpenAI.
-7. **chat**: Starts a chat session.
-
-If an unknown command is provided, it will display a message listing the valid commands.

package/autodoc/plugins/asana.mdx

@@ -1,47 +0,0 @@
-# Asana Plugin Executive Summary
-
-## Overview
-
-The Asana Plugin is designed to enhance chat interactions by integrating Asana task and project data. It detects and resolves Asana task and project URLs within user prompts, retrieves relevant data, and embeds this information into the chat context. This plugin is particularly useful for teams and individuals who rely on Asana for project management and want to seamlessly incorporate task details into their communication workflows.
-
-## Key Features
-
-### Input Detection and Resolution
-
-- **Task URLs**: The plugin identifies Asana task URLs within user prompts. It extracts these URLs and fetches the corresponding task details from Asana.
-- **Project URLs**: Similarly, the plugin detects Asana project URLs and retrieves all tasks associated with the specified projects.
-
-### Contextual Enhancements
-
-- **Task Details**: For each detected task, the plugin generates a detailed string that includes the task name, description, URL, and completion status. This information is then embedded into the chat, providing users with immediate access to task specifics.
-- **Project Tasks**: When project URLs are detected, the plugin fetches and embeds details for all tasks within the project, offering a comprehensive view of project progress and individual task statuses.
-
-### Embeddings
-
-- **Minimal Embeddings**: The plugin creates minimal embeddings for each task, which include:
-  - **ID**: The unique URL of the task.
-  - **Text**: A formatted string containing task details.
-  - **Metadata**: JSON-encoded task data for additional context.
-
-These embeddings can be used to enrich chat interactions, making it easier for users to reference and discuss specific tasks and projects.
-
-## Environment Variables
-
-To function correctly, the Asana Plugin requires the following environment variable to be set:
-
-- **ASANA_TOKEN**: This token is used to authenticate API requests to Asana. It should be set to a valid Asana access token.
-
-Example:
-```bash
-export ASANA_TOKEN=your_asana_access_token
-```
-
-## Usage
-
-The Asana Plugin can be integrated into chat applications to provide real-time access to Asana task and project data. Users can simply include Asana task or project URLs in their messages, and the plugin will automatically fetch and embed the relevant details. This functionality is particularly useful for:
-
-- **Project Management**: Keeping team members informed about task statuses and project progress.
-- **Collaboration**: Facilitating discussions around specific tasks and projects by providing immediate access to detailed information.
-- **Productivity**: Reducing the need to switch between chat applications and Asana, thereby streamlining workflows.
-
-By leveraging the Asana Plugin, teams can enhance their communication efficiency and ensure that everyone stays on the same page with up-to-date task and project information.

package/autodoc/plugins/downloader/downloader.mdx

@@ -1,38 +0,0 @@
-# Executive Summary: Downloader Plugin
-
-## Overview
-
-The Downloader Plugin is a comprehensive tool designed to facilitate the downloading, chunking, and transcription of audio and video content from various sources. This plugin is particularly useful for users who need to process large media files, extract meaningful information, and integrate this data into chat applications or other systems.
-
-## Key Features
-
-### Input Detection and Resolution
-
-- **URL Input**: The plugin accepts URLs as input, specifically targeting media content from platforms like YouTube.
-- **File Existence Check**: Before downloading, the plugin checks if the file already exists in the specified output directory to avoid redundant downloads.
-- **Media Information Retrieval**: It fetches detailed information about the media content, such as file ID and extension, ensuring accurate processing.
-
-### Contextual Enhancements
-
-- **Chunking Media Files**: The plugin can split large media files into smaller, manageable chunks. This is particularly useful for lengthy audio or video files, making them easier to process and transcribe.
-- **Transcription of Chunks**: Each chunk of the media file is transcribed using OpenAI's Whisper model. This transcription can then be used to add context to chats, making the content searchable and more interactive.
-
-### Embeddings Generation
-
-- **Text Embeddings**: The transcribed text from media chunks can be used to generate embeddings. These embeddings can be integrated into chat applications to enhance search capabilities, provide summaries, or enable other advanced text processing features.
-
-## Environment Variables
-
-To ensure the plugin functions correctly, the following environment variables must be set:
-
-- **OPENAI_KEY**: This variable is required to authenticate requests to the OpenAI API for transcription services.
-
-## Usage Scenarios
-
-- **Content Creators**: Download and transcribe video or audio content to create searchable text archives.
-- **Developers**: Integrate media content into chat applications, enhancing user interaction with contextual information.
-- **Researchers**: Process large volumes of media data, extracting and analyzing transcriptions for insights.
-
-## Conclusion
-
-The Downloader Plugin is a versatile tool that simplifies the process of downloading, chunking, and transcribing media content. By leveraging advanced transcription services and providing detailed media information, it adds significant value to chat applications and other systems requiring rich, contextual data. Ensure the necessary environment variables are set to fully utilize the plugin's capabilities.

package/autodoc/plugins/downloader/plugin.mdx

@@ -1,37 +0,0 @@
-# Downloader Plugin Executive Summary
-
-## Overview
-
-The Downloader Plugin is designed to enhance chat interactions by detecting and resolving URLs within user inputs. It provides additional context to chats by downloading and converting the content of the URLs into text. Furthermore, it generates embeddings from the downloaded content, which can be used for various purposes such as search, recommendation, and analysis.
-
-## Key Features
-
-### URL Detection and Resolution
-- **Input Detection**: The plugin scans user inputs for URLs using a regular expression.
-- **Content Download**: It attempts to download the content from the detected URLs, excluding certain file types (e.g., images like jpg, jpeg, png, gif).
-- **Text Conversion**: The downloaded content is converted into text, which can then be used to provide additional context in chats.
-
-### Contextual Enhancements
-- **Transcript Generation**: The plugin generates a transcript of the downloaded content, which can be appended to the chat to provide more information and context.
-- **Error Handling**: If a URL cannot be downloaded or processed, the plugin logs the error and continues processing other URLs.
-
-### Embedding Generation
-- **Minimal Embeddings**: The plugin generates minimal embeddings from the text content of the downloaded URLs. These embeddings include:
-  - **ID**: The URL of the content.
-  - **Text**: The converted text from the downloaded content.
-  - **Metadata**: Additional metadata (currently empty but can be extended).
-
-## Environment Variables
-
-The following environment variables are required for the plugin to function correctly:
-
-- **`process.env.DOWNLOAD_DIR`**: Specifies the directory where the downloaded files will be stored. Default is set to `.knowhow/downloads/`.
-
-## Usage
-
-The Downloader Plugin can be used in various scenarios where additional context from external URLs is beneficial. For example:
-- **Customer Support**: Automatically fetch and display relevant documentation or resources linked in customer queries.
-- **Content Aggregation**: Collect and summarize information from multiple sources for research or reporting purposes.
-- **Knowledge Management**: Enhance internal knowledge bases by embedding content from external URLs.
-
-By integrating the Downloader Plugin, users can significantly enrich their chat interactions with relevant and contextual information derived from external sources.

package/autodoc/plugins/downloader/types.mdx

@@ -1,42 +0,0 @@
-# Executive Summary: Audio and Video Download Plugin
-
-## Overview
-
-This plugin is designed to facilitate the detection, resolution, and contextual enhancement of audio and video downloads. It provides a comprehensive set of features that allow users to manage and process multimedia content efficiently. The plugin is particularly useful for applications that require detailed metadata extraction, format resolution, and embedding generation for audio and video files.
-
-## Key Features
-
-### Input Detection and Resolution
-
-- **Audio and Video Formats**: The plugin can detect various audio and video formats, including their extensions, resolutions, bitrates, and codecs.
-- **Download Information**: It provides detailed information about the downloadable content, such as title, description, thumbnail, age limit, and available formats.
-- **Protocol and Headers**: The plugin supports different protocols and can handle HTTP headers required for downloading content.
-
-### Contextual Enhancements
-
-- **Metadata Extraction**: Extracts comprehensive metadata from audio and video files, including subtitles, extractor details, and webpage URLs.
-- **Subtitles and Playlists**: Supports the extraction and management of subtitles and playlist information.
-- **DRM Detection**: Identifies whether the content has Digital Rights Management (DRM) protection.
-
-### Embedding Generation
-
-- **Audio and Video Embeddings**: Generates embeddings for audio and video content, which can be used for various applications such as content recommendation, search optimization, and more.
-- **Format-Specific Embeddings**: Provides embeddings based on specific formats, ensuring that the content is optimized for different use cases.
-
-## Environment Variables
-
-To ensure the plugin functions correctly, certain environment variables need to be set. These variables are crucial for configuring the plugin and enabling its features. Below are the required environment variables:
-
-- **`process.env.API_KEY`**: The API key required for accessing certain functionalities of the plugin.
-- **`process.env.DOWNLOAD_PATH`**: The path where downloaded content will be stored.
-- **`process.env.LOG_LEVEL`**: The level of logging detail (e.g., `info`, `debug`, `error`).
-
-## Usage
-
-This plugin can be integrated into applications that require robust audio and video processing capabilities. It is particularly useful for:
-
-- **Content Management Systems (CMS)**: Enhancing multimedia content with detailed metadata and embeddings.
-- **Media Players**: Providing rich context and format resolution for better playback experience.
-- **Data Analysis Tools**: Extracting and analyzing multimedia content for insights and trends.
-
-By leveraging this plugin, users can significantly improve the efficiency and effectiveness of their multimedia content management and processing workflows.

package/autodoc/plugins/embedding.mdx

@@ -1,41 +0,0 @@
-# Executive Summary: Embedding Plugin
-
-## Overview
-
-The Embedding Plugin is designed to enhance chat interactions by detecting and resolving user prompts, adding relevant context to conversations, and generating sophisticated embeddings. This plugin is particularly useful for applications that require contextual understanding and retrieval of information from a knowledge base.
-
-## Key Features
-
-### Input Detection and Resolution
-
-- **User Prompt Handling**: The plugin is capable of detecting user prompts and processing them to retrieve relevant information.
-- **Contextual Responses**: By analyzing the user input, the plugin can provide contextually appropriate responses, enhancing the overall user experience.
-
-### Context Addition
-
-- **Knowledge Base Integration**: The plugin integrates with a pre-configured knowledge base to fetch relevant information.
-- **Contextual Embedding**: It adds extra context to chats by retrieving and presenting the most relevant pieces of information from the knowledge base.
-- **Response Formatting**: The plugin formats the retrieved information into a coherent response that can be easily understood by the user.
-
-### Embedding Generation
-
-- **Configured Embeddings**: The plugin utilizes pre-configured embeddings to process and understand user prompts.
-- **Query Embedding**: It queries the embeddings to find the most relevant information that matches the user prompt.
-- **Result Presentation**: The plugin presents the top results, excluding the vector data, to provide a clean and concise response.
-
-## Environment Variables
-
-To ensure the proper functioning of the Embedding Plugin, certain environment variables need to be set. These variables are crucial for configuring the embeddings and querying the knowledge base. The required environment variables include:
-
-- **EMBEDDING_API_KEY**: This variable is used to authenticate and access the embedding service.
-- **KNOWLEDGE_BASE_URL**: This variable specifies the URL of the knowledge base that the plugin will query for information.
-
-## Usage
-
-The Embedding Plugin can be used in various applications where contextual understanding and information retrieval are essential. It is particularly useful in:
-
-- **Customer Support**: Enhancing automated responses by providing relevant information from a knowledge base.
-- **Virtual Assistants**: Improving the accuracy and relevance of responses by adding contextual information.
-- **Educational Tools**: Assisting in providing detailed and contextually appropriate answers to user queries.
-
-By integrating the Embedding Plugin, applications can significantly improve their interaction quality, providing users with more accurate and contextually relevant information.

package/autodoc/plugins/figma.mdx

@@ -1,45 +0,0 @@
-# Figma Plugin Executive Summary
-
-## Overview
-
-The Figma Plugin is designed to enhance user interactions by integrating Figma file data into chat environments. It detects and resolves Figma file URLs from user prompts, fetches relevant data from these files, and provides enriched context to the chat. Additionally, it generates embeddings based on the extracted Figma data, which can be used for various downstream applications such as search, recommendation, and more.
-
-## Key Features
-
-### Input Detection and Resolution
-
-- **URL Extraction**: The plugin identifies Figma file URLs embedded within user prompts.
-- **Data Fetching**: It retrieves detailed information from the specified Figma files, including images, components, styles, and more.
-- **Error Handling**: The plugin gracefully handles errors during data fetching, ensuring robust performance.
-
-### Context Enrichment
-
-- **Image Descriptions**: By leveraging AI (e.g., GPT Vision), the plugin generates descriptive text for images found within Figma files. This provides users with a richer understanding of the visual content.
-- **Structured Data**: The plugin formats and presents Figma data in a structured manner, making it easier for users to comprehend and utilize the information.
-
-### Embedding Generation
-
-- **Minimal Embeddings**: The plugin creates minimal embeddings from the Figma data, which include:
-  - **ID**: Unique identifier for the Figma file.
-  - **Text**: A JSON string representation of the Figma data.
-  - **Metadata**: Additional metadata associated with the Figma file.
-
-These embeddings can be used for various purposes, such as improving search relevance, enhancing recommendations, and more.
-
-## Environment Variables
-
-To function correctly, the Figma Plugin requires the following environment variable to be set:
-
-- **FIGMA_API_KEY**: This is the personal access token used to authenticate requests to the Figma API. It must be set in the environment where the plugin is running.
-
-## Usage
-
-The Figma Plugin can be integrated into chat applications to provide users with enhanced interactions involving Figma files. Here’s how it can be used:
-
-1. **Detect Figma URLs**: The plugin scans user prompts for Figma file URLs.
-2. **Fetch Figma Data**: It retrieves data from the identified Figma files, including images and other relevant components.
-3. **Generate Descriptions**: Using AI, the plugin generates descriptive text for images within the Figma files.
-4. **Embed Data**: It creates minimal embeddings from the Figma data, which can be used for various downstream applications.
-5. **Enrich Chat Context**: The plugin adds enriched context to the chat, providing users with detailed information about the Figma files.
-
-By integrating this plugin, chat applications can offer users a more interactive and informative experience when dealing with Figma files.

package/autodoc/plugins/github.mdx

@@ -1,40 +0,0 @@
-# GitHub Plugin Executive Summary
-
-## Overview
-
-The GitHub Plugin is designed to enhance chat interactions by detecting and resolving GitHub pull request URLs within user prompts. It provides additional context by embedding detailed information about the changes in the pull requests. This plugin is particularly useful for teams and individuals who frequently discuss code changes and need quick access to the specifics of those changes.
-
-## Key Features
-
-### Input Detection and Resolution
-
-- **Pull Request URL Detection**: The plugin scans user prompts for GitHub pull request URLs. It uses a regex pattern to identify URLs that match the format `https://github.com/{owner}/{repo}/pull/{pull_number}`.
-- **Diff Retrieval**: Once a pull request URL is detected, the plugin retrieves the diff associated with that pull request. This includes all the changes made in the pull request, formatted as a diff.
-
-### Contextual Enhancements
-
-- **Parsed Diffs**: The plugin parses the diffs to filter out large changes, ensuring that only manageable and relevant changes are included. This helps in focusing on the most significant parts of the pull request.
-- **Formatted Output**: The diffs are formatted in a readable manner, often in Markdown, making it easy to understand the changes directly within the chat interface.
-
-### Embeddings
-
-- **Minimal Embeddings**: The plugin generates minimal embeddings for the detected pull request URLs. Each embedding includes:
-  - **ID**: The URL of the pull request.
-  - **Text**: A JSON string representation of the parsed diff.
-  - **Metadata**: Additional metadata, if any, associated with the diff.
-
-## Environment Variables
-
-To function correctly, the GitHub Plugin requires the following environment variable to be set:
-
-- **GITHUB_TOKEN**: This is a personal access token used to authenticate with the GitHub API. It must be set in the environment where the plugin is running. The token should have sufficient permissions to read pull request data from the repositories of interest.
-
-## Usage
-
-The GitHub Plugin can be used in various scenarios, including:
-
-- **Code Reviews**: Automatically expand pull request URLs in chat to show the changes, facilitating quick reviews and discussions.
-- **Team Collaboration**: Enhance team communication by providing immediate context about code changes without leaving the chat interface.
-- **Automated Reporting**: Generate summaries of pull request changes for reporting purposes or automated notifications.
-
-By integrating this plugin, users can streamline their workflow, reduce context-switching, and improve the efficiency of code-related discussions.

package/autodoc/plugins/jira.mdx

@@ -1,46 +0,0 @@
-# Jira Plugin Executive Summary
-
-## Overview
-
-The Jira Plugin is designed to enhance chat interactions by detecting and resolving Jira issue URLs within user prompts. It provides additional context to chats by embedding detailed information about the referenced Jira issues. This plugin is particularly useful for teams that rely on Jira for project management and need to quickly access and share issue details within their communication channels.
-
-## Key Features
-
-### Input Detection and Resolution
-
-- **URL Extraction**: The plugin scans user prompts for Jira issue URLs based on a predefined pattern.
-- **Issue Retrieval**: It fetches detailed information about the identified Jira issues using the Jira API.
-- **Error Handling**: The plugin gracefully handles errors during the issue retrieval process, ensuring that the chat experience remains smooth even if some issues cannot be fetched.
-
-### Contextual Enhancements
-
-- **Issue Embedding**: The plugin generates embeddings for the detected Jira issues, which include the issue ID, a JSON representation of the issue details, and metadata.
-- **Chat Augmentation**: It enriches chat conversations by providing a structured summary of the Jira issues, including the issue key, summary, URL, and description.
-
-### Embedding Generation
-
-- **Minimal Embedding**: The plugin creates minimal embeddings that encapsulate essential information about each Jira issue. These embeddings can be used to provide quick references or to integrate with other systems that require issue data.
-
-## Environment Variables
-
-To function correctly, the Jira Plugin requires the following environment variables to be set:
-
-- **JIRA_HOST**: The host URL of the Jira instance.
-- **JIRA_USER**: The username for authenticating with the Jira API.
-- **JIRA_PASSWORD**: The password for authenticating with the Jira API.
-
-These environment variables ensure secure and authenticated access to the Jira instance, allowing the plugin to fetch issue details as needed.
-
-## Usage
-
-The Jira Plugin can be integrated into chat systems to automatically detect and resolve Jira issue URLs. When a user includes a Jira issue URL in their message, the plugin will:
-
-1. Extract the URL and identify the corresponding Jira issue.
-2. Fetch detailed information about the issue from the Jira API.
-3. Embed the issue details into the chat, providing a concise summary that includes the issue key, summary, URL, and description.
-
-This functionality allows team members to quickly access and share relevant Jira issue information without leaving their chat environment, thereby improving productivity and collaboration.
-
-## Conclusion
-
-The Jira Plugin is a powerful tool for teams that use Jira for project management. By automatically detecting and resolving Jira issue URLs and embedding detailed issue information into chats, it enhances communication and ensures that team members have quick access to the information they need. Setting the required environment variables ensures secure and seamless integration with your Jira instance.

package/autodoc/plugins/language.mdx

@@ -1,37 +0,0 @@
-# Language Plugin Executive Summary
-
-## Overview
-
-The Language Plugin is designed to enhance user interactions by detecting specific terms within user prompts and providing additional context to enrich the conversation. This plugin integrates with various other plugins and sources to gather relevant information, ensuring that responses are well-informed and contextually accurate.
-
-## Key Features
-
-### Input Detection and Resolution
-
-- **Term Detection**: The plugin scans user prompts for specific terms defined in a language configuration file.
-- **Contextual Expansion**: Upon detecting these terms, the plugin retrieves relevant information from various sources, including files and other integrated plugins.
-
-### Context Addition
-
-- **File Content Retrieval**: The plugin reads and includes content from specified files that are relevant to the detected terms.
-- **Textual Data Inclusion**: It also incorporates predefined textual data associated with the detected terms.
-- **Plugin Integration**: The plugin can call other integrated plugins (e.g., GitHub, Asana, Jira, Linear) to fetch additional context, ensuring a comprehensive response.
-
-### Embeddings Generation
-
-- **Contextual Embeddings**: Although the primary function is to add context, the plugin can generate embeddings based on the user prompt and the gathered contextual information. These embeddings can be used to further refine responses or for other analytical purposes.
-
-## Environment Variables
-
-To function correctly, the Language Plugin requires the following environment variables to be set:
-
-- **`process.env.CONFIG_PATH`**: Path to the main configuration file.
-- **`process.env.LANGUAGE_CONFIG_PATH`**: Path to the language-specific configuration file.
-
-These environment variables ensure that the plugin can access the necessary configuration files to detect terms and gather relevant context.
-
-## Usage
-
-The Language Plugin can be used in any application where enhanced, contextually aware responses are needed. It is particularly useful in customer support, virtual assistants, and any interactive system where understanding and responding to user queries accurately is crucial.
-
-By integrating with other plugins and sources, the Language Plugin ensures that responses are not only relevant but also enriched with additional information, providing a more comprehensive and satisfying user experience.

package/autodoc/plugins/linear.mdx

@@ -1,35 +0,0 @@
-# Linear Plugin Executive Summary
-
-## Overview
-
-The Linear Plugin is designed to enhance chat interactions by detecting and resolving Linear issue URLs within user prompts. It provides additional context to chats by embedding detailed information about the referenced Linear issues. This plugin is particularly useful for teams using Linear for project management, as it allows seamless integration of issue tracking data into chat environments.
-
-## Key Features
-
-### Input Detection and Resolution
-
-- **URL Extraction**: The plugin scans user prompts for Linear issue URLs. It uses a regex pattern to identify URLs that match the Linear issue format.
-- **Issue Data Retrieval**: For each detected URL, the plugin fetches detailed information about the corresponding Linear issue, including its identifier, title, URL, and description.
-
-### Contextual Enhancements
-
-- **Issue Embedding**: The plugin generates embeddings for each detected Linear issue. These embeddings include:
-  - **ID**: The URL of the issue.
-  - **Text**: A formatted string containing the issue's identifier, title, URL, and description.
-  - **Metadata**: Additional metadata (currently empty but can be extended).
-
-### Embedding Generation
-
-- **Minimal Embedding**: The plugin creates minimal embeddings that encapsulate essential information about each Linear issue. These embeddings can be used to enrich chat interactions with relevant issue details, making it easier for team members to discuss and resolve issues directly within the chat environment.
-
-## Environment Variables
-
-To function correctly, the Linear Plugin requires the following environment variable to be set:
-
-- **LINEAR_API_KEY**: This API key is used to authenticate requests to the Linear API. Ensure that this environment variable is set with a valid Linear API key before using the plugin.
-
-## Usage
-
-The Linear Plugin can be integrated into chat applications to provide real-time issue tracking and context. When a user includes a Linear issue URL in their message, the plugin automatically detects the URL, retrieves the issue details, and embeds the information into the chat. This allows team members to quickly access and discuss relevant issue details without leaving the chat environment.
-
-By leveraging the Linear Plugin, teams can improve their workflow efficiency, enhance communication, and maintain better visibility over their project management tasks directly within their chat applications.

package/autodoc/plugins/notion.mdx

@@ -1,38 +0,0 @@
-# Notion Plugin Executive Summary
-
-## Overview
-
-The Notion Plugin is designed to enhance chat interactions by integrating Notion content directly into conversations. It detects Notion URLs within user inputs, retrieves the corresponding Notion pages and their child blocks, and generates embeddings that can be used to provide additional context in chats. This plugin is particularly useful for users who frequently reference Notion documents and wish to seamlessly incorporate their content into discussions.
-
-## Key Features
-
-### Input Detection and Resolution
-
-- **URL Extraction**: The plugin scans user inputs for Notion URLs using a regular expression pattern. It identifies and extracts URLs that point to Notion pages.
-- **Page Retrieval**: For each detected URL, the plugin retrieves the corresponding Notion page and its child blocks. This includes handling nested blocks up to a specified depth.
-
-### Contextual Enhancements
-
-- **Content Embedding**: The plugin generates embeddings from the retrieved Notion pages and their child blocks. These embeddings include the text content and metadata, which can be used to enrich chat interactions with relevant information from Notion.
-- **Hierarchical Data Handling**: The plugin processes hierarchical data structures within Notion pages, ensuring that nested blocks and child pages are included in the embeddings.
-
-### Embedding Generation
-
-- **Minimal Embeddings**: The plugin creates minimal embeddings that encapsulate the essential content and metadata of Notion pages and blocks. These embeddings are structured to facilitate easy integration into chat systems.
-- **Comprehensive Data**: The embeddings include text content extracted from various block types within Notion, ensuring a comprehensive representation of the page's information.
-
-## Environment Variables
-
-To function correctly, the Notion Plugin requires the following environment variable to be set:
-
-- **NOTION_TOKEN**: This token is used to authenticate requests to the Notion API. It must be set in the environment where the plugin is running.
-
-## Usage
-
-The Notion Plugin can be used in various scenarios where integrating Notion content into chat interactions is beneficial. For example:
-
-- **Customer Support**: Support agents can quickly reference and share relevant Notion documentation with customers during chat sessions.
-- **Team Collaboration**: Team members can embed and discuss specific Notion pages within chat platforms, facilitating more informed and context-rich conversations.
-- **Knowledge Management**: Users can pull in detailed information from Notion pages to answer questions or provide explanations in chat environments.
-
-By leveraging the Notion Plugin, users can enhance their chat interactions with rich, contextual information from their Notion workspace, improving communication efficiency and effectiveness.

package/autodoc/plugins/plugins.mdx

@@ -1,59 +0,0 @@
-# Plugin Service Executive Summary
-
-## Overview
-
-The Plugin Service is a comprehensive system designed to enhance chat interactions by detecting and resolving various types of inputs, adding contextual information, and generating embeddings. This service integrates multiple specialized plugins, each contributing unique functionalities to improve user experience and productivity.
-
-## Input Detection and Resolution
-
-The Plugin Service is capable of detecting and resolving a wide range of inputs through its diverse set of plugins. Each plugin is tailored to handle specific types of data and interactions:
-
-- **VimPlugin**: Enhances text editing capabilities with Vim-like commands.
-- **GitHubPlugin**: Manages GitHub repositories, issues, and pull requests.
-- **AsanaPlugin**: Integrates with Asana for task and project management.
-- **LinearPlugin**: Connects with Linear for issue tracking and project management.
-- **JiraPlugin**: Interfaces with Jira for comprehensive project tracking.
-- **NotionPlugin**: Syncs with Notion for note-taking and project organization.
-- **DownloaderPlugin**: Facilitates downloading of files and resources.
-- **FigmaPlugin**: Integrates with Figma for design collaboration.
-- **LanguagePlugin**: Provides language processing capabilities.
-- **EmbeddingPlugin**: Generates embeddings for various types of data.
-
-## Contextual Enhancements
-
-The Plugin Service adds valuable context to chat interactions by leveraging the capabilities of its integrated plugins. For example:
-
-- **GitHubPlugin** can provide context about recent commits, open issues, and pull requests.
-- **AsanaPlugin** and **LinearPlugin** can offer insights into task statuses and project timelines.
-- **JiraPlugin** can deliver updates on project progress and issue resolutions.
-- **NotionPlugin** can share notes and project documentation.
-- **FigmaPlugin** can present design updates and feedback.
-
-These contextual enhancements ensure that users have access to relevant information directly within their chat environment, streamlining workflows and improving decision-making.
-
-## Embedding Generation
-
-The Plugin Service supports the generation of embeddings through the **EmbeddingPlugin**. Embeddings are vector representations of data that can be used for various purposes, such as:
-
-- **Text Embeddings**: Representing textual data in a numerical format for natural language processing tasks.
-- **Image Embeddings**: Converting visual data into vectors for image recognition and analysis.
-- **Custom Embeddings**: Generating embeddings for domain-specific data to enhance search and recommendation systems.
-
-These embeddings enable advanced data processing and machine learning applications, making the Plugin Service a powerful tool for data-driven tasks.
-
-## Environment Variables
-
-To ensure the proper functioning of the Plugin Service, certain environment variables need to be set. These variables are used to configure the plugins and provide necessary credentials and settings. The required environment variables include:
-
-- **GITHUB_TOKEN**: Required for the **GitHubPlugin** to authenticate and interact with GitHub APIs.
-- **ASANA_TOKEN**: Required for the **AsanaPlugin** to access Asana's API.
-- **LINEAR_API_KEY**: Required for the **LinearPlugin** to connect with Linear's services.
-- **JIRA_API_TOKEN**: Required for the **JiraPlugin** to authenticate with Jira.
-- **NOTION_API_KEY**: Required for the **NotionPlugin** to interact with Notion's API.
-- **FIGMA_API_KEY**: Required for the **FigmaPlugin** to access Figma's API.
-
-These environment variables should be set in the system where the Plugin Service is deployed to ensure seamless integration and functionality.
-
-## Conclusion
-
-The Plugin Service is a versatile and powerful system that enhances chat interactions by detecting and resolving various inputs, adding contextual information, and generating embeddings. By integrating with multiple specialized plugins, it provides a comprehensive solution for improving productivity and user experience in chat environments. Proper configuration of environment variables is essential for the optimal performance of the service.