@larkup/cli 0.1.19 → 0.2.0

package/README.md

@@ -1,58 +1,43 @@
 # Larkup CLI
 
-The official Command Line Interface for **Larkup**. 
-Build, index, and serve a Retrieval-Augmented Generation (RAG) pipeline directly from your terminal.
+Load data, build an index, chat, and deploy Larkup RAG servers from the terminal.
 
-## Installation
-
-You can install the CLI globally via npm or run it via npx:
+## Install
 
 ```bash
 npm install -g @larkup/cli
-# or
-npx @larkup/cli
 ```
 
-## Usage
-
-The CLI provides a set of commands to manage your RAG workspaces, configure vector stores, ingest documents, and query your data.
+## Workflow
 
 ```bash
-larkup <command> [options]
+larkup init product-docs
+larkup index ./knowledge
+larkup generate
+larkup serve
 ```
 
-### Core Commands
-
-- **`init [name]`**: Create a new RAG server (workspace project).
-- **`config`**: Configure vector stores and embedding models for your active workspace.
-- **`add-doc`**: Ingest documents (local files, URLs, or text) into your workspace.
-- **`index`**: Process, chunk, and index your ingested documents into the configured vector database.
-- **`serve`**: Spin up the generated RAG server locally for fast testing and API integration.
-- **`query`**: Test retrieval quality by querying your indexed data directly from the terminal.
-- **`chat`**: Start an interactive chat session with your RAG pipeline in the terminal.
-- **`generate`**: Generate server configurations or boilerplate code.
-- **`settings`**: View or update your global settings and environment variables.
-
-### Managing Workspaces (Servers)
-
-- **`use`**: Switch your active server/workspace context.
+`index` accepts individual files or folders, including text, source code, CSV, JSON, PDF, and Word documents. It streams loading and indexing progress.
 
-## Example Workflow
+Use the dedicated media command for images, audio, and video:
 
 ```bash
-# 1. Initialize a new project
-larkup init my-rag-server
-
-# 2. Add documents to the project
-larkup add-doc ./data/knowledge-base.txt
-
-# 3. Index the documents into the vector store
-larkup index
-
-# 4. Start an interactive chat session with your data
-larkup chat
+larkup marketplace install video-audio
+larkup media ./demo.mp4
 ```
 
-## Documentation
-
-For more detailed guides and information, please refer to the [Larkup Documentation](https://larkup.de/docs) or visit our [Web UI](https://larkup.de).
+## Commands
+
+- `larkup index [sources...]` loads sources and builds the index.
+- `larkup documents` manages and exports corpus documents.
+- `larkup media [sources...]` processes image, audio, and video files.
+- `larkup serve` runs the generated server.
+- `larkup query <question>` retrieves relevant chunks.
+- `larkup chat` starts an interactive terminal chat.
+- `larkup marketplace` manages Marketplace Hub tools.
+- `larkup deploy [target]` prepares Docker, Vercel, local, export, or agent targets.
+- `larkup test` validates configuration, storage, or a deployed endpoint.
+- `larkup open [target]` opens the Web UI or API reference.
+- `larkup update` checks for and installs CLI releases.
+
+Generated servers use `http://localhost:8080` by default. Run `larkup --help` or see the [CLI documentation](https://larkup.de/docs/developer/cli) for all options.

package/dist/analytics-store-JIRW4PQQ.js

@@ -0,0 +1,13 @@
+import {
+  estimateCost,
+  getAnalyticsSummary,
+  readUsageEvents,
+  trackUsageEvent
+} from "./chunk-6IFSA37D.js";
+import "./chunk-3RG5ZIWI.js";
+export {
+  estimateCost,
+  getAnalyticsSummary,
+  readUsageEvents,
+  trackUsageEvent
+};

package/dist/{chroma-GIDEKUIH.js → chroma-NWWTSRG6.js}

@@ -77,6 +77,15 @@ var ChromaAdapter = class {
     }
     this.collection = null;
   }
+  async deleteByDocumentIds(documentIds) {
+    if (documentIds.length === 0) return;
+    try {
+      const collection = await this.getCollection();
+      await collection.delete({ where: { documentId: { $in: documentIds } } });
+    } catch (err) {
+      console.error("Failed to delete vectors by documentIds in Chroma:", err);
+    }
+  }
   // ── Upsert ─────────────────────────────────────────────────────────────────
   async upsert(records) {
     if (records.length === 0) return;
@@ -161,7 +170,7 @@ var ChromaAdapter = class {
   }
   async documentQuery(collection, queryText, topK) {
     const result = await collection.get({
-      whereDocument: { "$contains": queryText },
+      whereDocument: { $contains: queryText },
       limit: topK,
       include: ["documents", "metadatas"]
     });
@@ -175,14 +184,7 @@ var ChromaAdapter = class {
     return ids.map((id, i) => {
       const meta = metadatas[i] ?? {};
       const score = 1;
-      const {
-        title,
-        url,
-        source,
-        documentId,
-        chunkIndex,
-        ...customMetadata
-      } = meta;
+      const { title, url, source, documentId, chunkIndex, ...customMetadata } = meta;
       return {
         id,
         score,
@@ -204,14 +206,7 @@ var ChromaAdapter = class {
       const meta = metadatas[i] ?? {};
       const distance = distances[i] ?? 0;
       const score = 1 / (1 + distance);
-      const {
-        title,
-        url,
-        source,
-        documentId,
-        chunkIndex,
-        ...customMetadata
-      } = meta;
+      const { title, url, source, documentId, chunkIndex, ...customMetadata } = meta;
       return {
         id,
         score,
@@ -236,9 +231,7 @@ var ChromaAdapter = class {
     } catch (err) {
       const msg = err.message ?? "";
       if (msg.includes("401") || msg.includes("Unauthorized") || msg.includes("403") || msg.includes("Forbidden")) {
-        throw new Error(
-          "Invalid Chroma credentials. Please check your auth token or API key."
-        );
+        throw new Error("Invalid Chroma credentials. Please check your auth token or API key.");
       }
       if (msg.includes("ECONNREFUSED") || msg.includes("fetch failed")) {
         throw new Error(