@mastra/mcp-docs-server 0.13.37 → 0.13.38

package/.docs/raw/memory/storage/memory-with-upstash.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Example: Memory with Upstash | Memory | Mastra Docs"
+title: "Memory with Upstash | Memory | Mastra Docs"
 description: Example for how to use Mastra's memory system with Upstash Redis storage and vector capabilities.
 ---
 
@@ -11,7 +11,7 @@ This example demonstrates how to use Mastra's memory system with Upstash as the
 
 This example uses the `openai` model and requires both Upstash Redis and Upstash Vector services. Make sure to add the following to your `.env` file:
 
-```bash filename=".env" copy
+```bash title=".env" copy
 OPENAI_API_KEY=<your-api-key>
 UPSTASH_REDIS_REST_URL=<your-redis-url>
 UPSTASH_REDIS_REST_TOKEN=<your-redis-token>
@@ -31,7 +31,7 @@ npm install @mastra/upstash
 
 To add Upstash memory to an agent use the `Memory` class and create a new `storage` key using `UpstashStore` and a new `vector` key using `UpstashVector`. The configuration can point to either a remote service or a local setup.
 
-```typescript filename="src/mastra/agents/example-upstash-agent.ts" showLineNumbers copy
+```typescript title="src/mastra/agents/example-upstash-agent.ts" showLineNumbers copy
 import { Memory } from "@mastra/memory";
 import { Agent } from "@mastra/core/agent";
 import { openai } from "@ai-sdk/openai";
@@ -39,23 +39,21 @@ import { UpstashStore } from "@mastra/upstash";
 
 export const upstashAgent = new Agent({
   name: "upstash-agent",
-  instructions: "You are an AI agent with the ability to automatically recall memories from previous interactions.",
+  instructions:
+    "You are an AI agent with the ability to automatically recall memories from previous interactions.",
   model: openai("gpt-4o"),
   memory: new Memory({
     storage: new UpstashStore({
       url: process.env.UPSTASH_REDIS_REST_URL!,
-      token: process.env.UPSTASH_REDIS_REST_TOKEN!
+      token: process.env.UPSTASH_REDIS_REST_TOKEN!,
     }),
     options: {
-      threads: {
-        generateTitle: true
-      }
-    }
-  })
+      generateTitle: true,
+    },
+  }),
 });
 ```
 
-
 ## Local embeddings with fastembed
 
 Embeddings are numeric vectors used by memory’s `semanticRecall` to retrieve related messages by meaning (not keywords). This setup uses `@mastra/fastembed` to generate vector embeddings.
@@ -68,7 +66,7 @@ npm install @mastra/fastembed
 
 Add the following to your agent:
 
-```typescript filename="src/mastra/agents/example-upstash-agent.ts" showLineNumbers copy
+```typescript title="src/mastra/agents/example-upstash-agent.ts" showLineNumbers copy
 import { Memory } from "@mastra/memory";
 import { Agent } from "@mastra/core/agent";
 import { openai } from "@ai-sdk/openai";
@@ -77,26 +75,27 @@ import { fastembed } from "@mastra/fastembed";
 
 export const upstashAgent = new Agent({
   name: "upstash-agent",
-  instructions: "You are an AI agent with the ability to automatically recall memories from previous interactions.",
+  instructions:
+    "You are an AI agent with the ability to automatically recall memories from previous interactions.",
   model: openai("gpt-4o"),
   memory: new Memory({
     storage: new UpstashStore({
       url: process.env.UPSTASH_REDIS_REST_URL!,
-      token: process.env.UPSTASH_REDIS_REST_TOKEN!
+      token: process.env.UPSTASH_REDIS_REST_TOKEN!,
     }),
     vector: new UpstashVector({
       url: process.env.UPSTASH_VECTOR_REST_URL!,
-      token: process.env.UPSTASH_VECTOR_REST_TOKEN!
+      token: process.env.UPSTASH_VECTOR_REST_TOKEN!,
     }),
     embedder: fastembed,
     options: {
       lastMessages: 10,
       semanticRecall: {
         topK: 3,
-        messageRange: 2
-      }
-    }
-  })
+        messageRange: 2,
+      },
+    },
+  }),
 });
 ```
 
@@ -104,7 +103,7 @@ export const upstashAgent = new Agent({
 
 Use `memoryOptions` to scope recall for this request. Set `lastMessages: 5` to limit recency-based recall, and use `semanticRecall` to fetch the `topK: 3` most relevant messages, including `messageRange: 2` neighboring messages for context around each match.
 
-```typescript filename="src/test-upstash-agent.ts" showLineNumbers copy
+```typescript title="src/test-upstash-agent.ts" showLineNumbers copy
 import "dotenv/config";
 
 import { mastra } from "./mastra";
@@ -117,8 +116,8 @@ const agent = mastra.getAgent("upstashAgent");
 const message = await agent.stream("My name is Mastra", {
   memory: {
     thread: threadId,
-    resource: resourceId
-  }
+    resource: resourceId,
+  },
 });
 
 await message.textStream.pipeTo(new WritableStream());
@@ -126,15 +125,15 @@ await message.textStream.pipeTo(new WritableStream());
 const stream = await agent.stream("What's my name?", {
   memory: {
     thread: threadId,
-    resource: resourceId
+    resource: resourceId,
   },
   memoryOptions: {
     lastMessages: 5,
     semanticRecall: {
       topK: 3,
-      messageRange: 2
-    }
-  }
+      messageRange: 2,
+    },
+  },
 });
 
 for await (const chunk of stream.textStream) {
@@ -144,4 +143,4 @@ for await (const chunk of stream.textStream) {
 
 ## Related
 
-- [Calling Agents](../agents/calling-agents.mdx)
+- [Calling Agents](/examples/agents/calling-agents)

package/.docs/raw/memory/threads-and-resources.mdx

@@ -1,10 +1,8 @@
 ---
-title: "Memory Threads and Resources | Memory | Mastra Docs"
+title: "Memory threads and resources | Memory | Mastra Docs"
 description: "Learn how Mastra's memory system works with working memory, conversation history, and semantic recall."
 ---
 
-import { Callout } from "nextra/components";
-
 # Memory threads and resources
 
 Mastra organizes memory into threads, which are records that group related interactions, using two identifiers:
@@ -12,26 +10,28 @@ Mastra organizes memory into threads, which are records that group related inter
 1. **`thread`**: A globally unique ID representing the conversation (e.g., `support_123`). Must be unique across all resources.
 2. **`resource`**: The user or entity that owns the thread (e.g., `user_123`, `org_456`).
 
-The `resource` is especially important for [resource-scoped memory](./working-memory.mdx#resource-scoped-memory), which allows memory to persist across all threads associated with the same user or entity.
+The `resource` is especially important for [resource-scoped memory](./working-memory#resource-scoped-memory), which allows memory to persist across all threads associated with the same user or entity.
 
 ```typescript {4} showLineNumbers
 const stream = await agent.stream("message for agent", {
   memory: {
     thread: "user-123",
-    resource: "test-123"
-  }
+    resource: "test-123",
+  },
 });
 ```
 
-<Callout type="warning">
+:::warning
+
 Even with memory configured, agents won’t store or recall information unless both `thread` and `resource` are provided.
-</Callout>
+
+:::
 
 > Mastra Playground sets `thread` and `resource` IDs automatically. In your own application, you must provide them manually as part of each `.generate()` or `.stream()` call.
 
 ### Thread title generation
 
-Mastra can automatically generate descriptive thread titles based on the user's first message. Enable this by setting `generateTitle` to `true`. This improves organization and makes it easier to display conversations in your UI.
+Mastra can automatically generate descriptive thread titles based on the user's first message. Enable it by setting `generateTitle` to `true`. This improves organization and makes it easier to display conversations in your UI.
 
 ```typescript {3-7} showLineNumbers
 export const testAgent = new Agent({
@@ -41,11 +41,11 @@ export const testAgent = new Agent({
         generateTitle: true,
       }
     },
-  })
+  }),
 });
 ```
 
-> Title generation runs asynchronously after the agent responds and does not affect response time. See the [full configuration reference](../../reference/memory/Memory.mdx#thread-title-generation) for details and examples.
+> Title generation runs asynchronously after the agent responds and does not affect response time. See the [full configuration reference](/reference/memory/memory-class) for details and examples.
 
 #### Optimizing title generation
 
@@ -59,11 +59,12 @@ export const testAgent = new Agent({
       threads: {
         generateTitle: {
           model: openai("gpt-4.1-nano"),
-          instructions: "Generate a concise title based on the user's first message",
+          instructions:
+            "Generate a concise title based on the user's first message",
         },
       },
-    }
-  })
+    },
+  }),
 });
 ```
 
@@ -80,15 +81,17 @@ export const testAgent = new Agent({
         generateTitle: {
           model: ({ runtimeContext }) => {
             const userTier = runtimeContext.get("userTier");
-            return userTier === "premium" ? openai("gpt-4.1") : openai("gpt-4.1-nano");
+            return userTier === "premium"
+              ? openai("gpt-4.1")
+              : openai("gpt-4.1-nano");
           },
           instructions: ({ runtimeContext }) => {
             const language = runtimeContext.get("userLanguage") || "English";
             return `Generate a concise, engaging title in ${language} based on the user's first message.`;
-          }
-        }
-      }
-    }
-  })
+          },
+        },
+      },
+    },
+  }),
 });
 ```

package/.docs/raw/memory/working-memory.mdx

@@ -3,23 +3,23 @@ title: "Working Memory | Memory | Mastra Docs"
 description: "Learn how to configure working memory in Mastra to store persistent user data, preferences."
 ---
 
-import YouTube from "@/components/youtube";
+import Youtube from "@site/src/components/YouTube-player";
 
 # Working Memory
 
-While [conversation history](/docs/memory/overview#conversation-history) and [semantic recall](./semantic-recall.mdx) help agents remember conversations, working memory allows them to maintain persistent information about users across interactions.
+While [conversation history](/docs/memory/conversation-history) and [semantic recall](./semantic-recall) help agents remember conversations, working memory allows them to maintain persistent information about users across interactions.
 
 Think of it as the agent's active thoughts or scratchpad – the key information they keep available about the user or task. It's similar to how a person would naturally remember someone's name, preferences, or important details during a conversation.
 
 This is useful for maintaining ongoing state that's always relevant and should always be available to the agent.
 
 Working memory can persist at two different scopes:
+
 - **Thread-scoped** (default): Memory is isolated per conversation thread
 - **Resource-scoped**: Memory persists across all conversation threads for the same user
 
 **Important:** Switching between scopes means the agent won't see memory from the other scope - thread-scoped memory is completely separate from resource-scoped memory.
 
-
 ## Quick Start
 
 Here's a minimal example of setting up an agent with working memory:
@@ -90,13 +90,11 @@ const memory = new Memory({
   options: {
     workingMemory: {
       enabled: true,
-      scope: 'resource', // Memory persists across all user threads
+      scope: "thread", // Memory is isolated per thread
       template: `# User Profile
 - **Name**:
-- **Location**:
 - **Interests**:
-- **Preferences**:
-- **Long-term Goals**:
+- **Current Goal**:
 `,
     },
   },
@@ -104,27 +102,17 @@ const memory = new Memory({
 ```
 
 **Use cases:**
-- Personal assistants that remember user preferences
-- Customer service bots that maintain customer context
-- Educational applications that track student progress
-
-### Usage with Agents
-
-When using resource-scoped memory, make sure to pass the `resourceId` parameter:
 
-```typescript
-// Resource-scoped memory requires resourceId
-const response = await agent.generate("Hello!", {
-  threadId: "conversation-123",
-  resourceId: "user-alice-456" // Same user across different threads
-});
-```
+- Different conversations about separate topics
+- Temporary or session-specific information
+- Workflows where each thread needs working memory but threads are ephemeral and not related to each other
 
 ## Storage Adapter Support
 
 Resource-scoped working memory requires specific storage adapters that support the `mastra_resources` table:
 
 ### ✅ Supported Storage Adapters
+
 - **LibSQL** (`@mastra/libsql`)
 - **PostgreSQL** (`@mastra/pg`)
 - **Upstash** (`@mastra/upstash`)
@@ -222,18 +210,20 @@ Working memory can also be defined using a structured schema instead of a Markdo
 ### Example: Schema-Based Working Memory
 
 ```typescript
-import { z } from 'zod';
-import { Memory } from '@mastra/memory';
+import { z } from "zod";
+import { Memory } from "@mastra/memory";
 
 const userProfileSchema = z.object({
   name: z.string().optional(),
   location: z.string().optional(),
   timezone: z.string().optional(),
-  preferences: z.object({
-    communicationStyle: z.string().optional(),
-    projectGoal: z.string().optional(),
-    deadlines: z.array(z.string()).optional(),
-  }).optional(),
+  preferences: z
+    .object({
+      communicationStyle: z.string().optional(),
+      projectGoal: z.string().optional(),
+      deadlines: z.array(z.string()).optional(),
+    })
+    .optional(),
 });
 
 const memory = new Memory({
@@ -311,7 +301,7 @@ While agents typically update working memory through the `updateWorkingMemory` t
 
 When creating a thread, you can provide initial working memory through the metadata's `workingMemory` key:
 
-```typescript filename="src/app/medical-consultation.ts" showLineNumbers copy
+```typescript title="src/app/medical-consultation.ts" showLineNumbers copy
 // Create a thread with initial working memory
 const thread = await memory.createThread({
   threadId: "thread-123",
@@ -324,14 +314,14 @@ const thread = await memory.createThread({
 - Allergies: Penicillin
 - Current Medications: None
 - Medical History: Hypertension (controlled)
-`
-  }
+`,
+  },
 });
 
 // The agent will now have access to this information in all messages
 await agent.generate("What's my blood type?", {
   threadId: thread.id,
-  resourceId: "user-456"
+  resourceId: "user-456",
 });
 // Response: "Your blood type is O+."
 ```
@@ -340,7 +330,7 @@ await agent.generate("What's my blood type?", {
 
 You can also update an existing thread's working memory:
 
-```typescript filename="src/app/medical-consultation.ts" showLineNumbers copy
+```typescript title="src/app/medical-consultation.ts" showLineNumbers copy
 // Update thread metadata to add/modify working memory
 await memory.updateThread({
   id: "thread-123",
@@ -353,8 +343,8 @@ await memory.updateThread({
 - Allergies: Penicillin, Ibuprofen  // Updated
 - Current Medications: Lisinopril 10mg daily  // Added
 - Medical History: Hypertension (controlled)
-`
-  }
+`,
+  },
 });
 ```
 
@@ -362,17 +352,16 @@ await memory.updateThread({
 
 Alternatively, use the `updateWorkingMemory` method directly:
 
-```typescript filename="src/app/medical-consultation.ts" showLineNumbers copy
+```typescript title="src/app/medical-consultation.ts" showLineNumbers copy
 await memory.updateWorkingMemory({
   threadId: "thread-123",
   resourceId: "user-456", // Required for resource-scoped memory
-  workingMemory: "Updated memory content..."
+  workingMemory: "Updated memory content...",
 });
 ```
 
 ## Examples
 
-- [Basic working memory](/examples/memory/working-memory-basic)
 - [Working memory with template](/examples/memory/working-memory-template)
 - [Working memory with schema](/examples/memory/working-memory-schema)
 - [Per-resource working memory](https://github.com/mastra-ai/mastra/tree/main/examples/memory-per-resource-example) - Complete example showing resource-scoped memory persistence

package/.docs/raw/observability/ai-tracing/exporters/arize.mdx

@@ -3,8 +3,6 @@ title: "Arize Exporter | AI Tracing | Observability | Mastra Docs"
 description: "Send AI traces to Arize Phoenix or Arize AX using OpenTelemetry and OpenInference"
 ---
 
-import { Callout } from "nextra/components";
-
 # Arize Exporter
 
 [Arize](https://arize.com/) provides observability platforms for AI applications through [Phoenix](https://phoenix.arize.com/) (open-source) and [Arize AX](https://arize.com/generative-ai/) (enterprise). The Arize exporter sends AI traces using OpenTelemetry and [OpenInference](https://github.com/Arize-ai/openinference/tree/main/spec) semantic conventions, compatible with any OpenTelemetry platform that supports OpenInference.
@@ -12,6 +10,7 @@ import { Callout } from "nextra/components";
 ## When to Use Arize
 
 Arize is ideal when you need:
+
 - **OpenInference standards** - Industry-standard semantic conventions for AI traces
 - **Flexible deployment** - Self-hosted Phoenix or managed Arize AX
 - **OpenTelemetry compatibility** - Works with any OTLP-compatible platform
@@ -37,7 +36,7 @@ Phoenix is an open-source observability platform that can be self-hosted or used
 3. **API Key**: Optional for unauthenticated instances, required for Phoenix Cloud
 4. **Environment Variables**: Set your configuration
 
-```bash filename=".env"
+```bash title=".env"
 PHOENIX_ENDPOINT=http://localhost:6006/v1/traces  # Or your Phoenix Cloud URL
 PHOENIX_API_KEY=your-api-key  # Optional for local instances
 PHOENIX_PROJECT_NAME=mastra-service  # Optional, defaults to 'mastra-service'
@@ -45,7 +44,7 @@ PHOENIX_PROJECT_NAME=mastra-service  # Optional, defaults to 'mastra-service'
 
 #### Basic Setup
 
-```typescript filename="src/mastra/index.ts"
+```typescript title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 import { ArizeExporter } from "@mastra/arize";
 
@@ -53,7 +52,7 @@ export const mastra = new Mastra({
   observability: {
     configs: {
       arize: {
-        serviceName: process.env.PHOENIX_PROJECT_NAME || 'mastra-service',
+        serviceName: process.env.PHOENIX_PROJECT_NAME || "mastra-service",
         exporters: [
           new ArizeExporter({
             endpoint: process.env.PHOENIX_ENDPOINT!,
@@ -67,7 +66,8 @@ export const mastra = new Mastra({
 });
 ```
 
-<Callout type="info">
+:::info
+
 **Quick Start with Docker**
 
 Test locally with an in-memory Phoenix instance:
@@ -79,7 +79,8 @@ docker run --pull=always -d --name arize-phoenix -p 6006:6006 \
 ```
 
 Set `PHOENIX_ENDPOINT=http://localhost:6006/v1/traces` and run your Mastra agent to see traces at [localhost:6006](http://localhost:6006).
-</Callout>
+
+:::
 
 ### Arize AX Setup
 
@@ -92,7 +93,7 @@ Arize AX is an enterprise observability platform with advanced features for prod
 3. **API Key**: Generate in Arize AX settings
 4. **Environment Variables**: Set your credentials
 
-```bash filename=".env"
+```bash title=".env"
 ARIZE_SPACE_ID=your-space-id
 ARIZE_API_KEY=your-api-key
 ARIZE_PROJECT_NAME=mastra-service  # Optional
@@ -100,7 +101,7 @@ ARIZE_PROJECT_NAME=mastra-service  # Optional
 
 #### Basic Setup
 
-```typescript filename="src/mastra/index.ts"
+```typescript title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 import { ArizeExporter } from "@mastra/arize";
 
@@ -108,7 +109,7 @@ export const mastra = new Mastra({
   observability: {
     configs: {
       arize: {
-        serviceName: process.env.ARIZE_PROJECT_NAME || 'mastra-service',
+        serviceName: process.env.ARIZE_PROJECT_NAME || "mastra-service",
         exporters: [
           new ArizeExporter({
             apiKey: process.env.ARIZE_API_KEY!,
@@ -131,31 +132,31 @@ The Arize exporter supports advanced configuration for fine-tuning OpenTelemetry
 ```typescript
 new ArizeExporter({
   // Phoenix Configuration
-  endpoint: 'https://your-collector.example.com/v1/traces',  // Required for Phoenix
+  endpoint: "https://your-collector.example.com/v1/traces", // Required for Phoenix
 
   // Arize AX Configuration
-  spaceId: 'your-space-id',  // Required for Arize AX
+  spaceId: "your-space-id", // Required for Arize AX
 
   // Shared Configuration
-  apiKey: 'your-api-key',  // Required for authenticated endpoints
-  projectName: 'mastra-service',  // Optional project name
+  apiKey: "your-api-key", // Required for authenticated endpoints
+  projectName: "mastra-service", // Optional project name
 
   // Optional OTLP settings
   headers: {
-    'x-custom-header': 'value',  // Additional headers for OTLP requests
+    "x-custom-header": "value", // Additional headers for OTLP requests
   },
 
   // Debug and performance tuning
-  logLevel: 'debug',  // Logging: debug | info | warn | error
-  batchSize: 512,     // Batch size before exporting spans
-  timeout: 30000,     // Timeout in ms before exporting spans
+  logLevel: "debug", // Logging: debug | info | warn | error
+  batchSize: 512, // Batch size before exporting spans
+  timeout: 30000, // Timeout in ms before exporting spans
 
   // Custom resource attributes
   resourceAttributes: {
-    'deployment.environment': process.env.NODE_ENV,
-    'service.version': process.env.APP_VERSION,
+    "deployment.environment": process.env.NODE_ENV,
+    "service.version": process.env.APP_VERSION,
   },
-})
+});
 ```
 
 ### Batch Processing Options
@@ -168,9 +169,9 @@ new ArizeExporter({
   apiKey: process.env.PHOENIX_API_KEY,
 
   // Batch processing configuration
-  batchSize: 512,    // Number of spans to batch (default: 512)
-  timeout: 30000,    // Max time in ms to wait before export (default: 30000)
-})
+  batchSize: 512, // Number of spans to batch (default: 512)
+  timeout: 30000, // Max time in ms to wait before export (default: 30000)
+});
 ```
 
 ### Resource Attributes
@@ -181,12 +182,12 @@ Add custom attributes to all exported spans:
 new ArizeExporter({
   endpoint: process.env.PHOENIX_ENDPOINT!,
   resourceAttributes: {
-    'deployment.environment': process.env.NODE_ENV,
-    'service.namespace': 'production',
-    'service.instance.id': process.env.HOSTNAME,
-    'custom.attribute': 'value',
+    "deployment.environment": process.env.NODE_ENV,
+    "service.namespace": "production",
+    "service.instance.id": process.env.HOSTNAME,
+    "custom.attribute": "value",
   },
-})
+});
 ```
 
 ## OpenInference Semantic Conventions

package/.docs/raw/observability/ai-tracing/exporters/braintrust.mdx

@@ -3,8 +3,6 @@ title: "Braintrust Exporter | AI Tracing | Observability | Mastra Docs"
 description: "Send AI traces to Braintrust for evaluation and monitoring"
 ---
 
-import { Callout } from "nextra/components";
-
 # Braintrust Exporter
 
 [Braintrust](https://www.braintrust.dev/) is an evaluation and monitoring platform that helps you measure and improve LLM application quality. The Braintrust exporter sends your AI traces to Braintrust, enabling systematic evaluation, scoring, and experimentation.
@@ -12,6 +10,7 @@ import { Callout } from "nextra/components";
 ## When to Use Braintrust
 
 Braintrust excels at:
+
 - **Evaluation workflows** - Systematic quality measurement
 - **Experiment tracking** - Compare model versions and prompts
 - **Dataset management** - Curate test cases and golden datasets
@@ -33,14 +32,14 @@ npm install @mastra/braintrust
 3. **API Key**: Generate in Braintrust Settings → API Keys
 4. **Environment Variables**: Set your credentials:
 
-```bash filename=".env"
+```bash title=".env"
 BRAINTRUST_API_KEY=sk-xxxxxxxxxxxxxxxx
 BRAINTRUST_PROJECT_NAME=my-project  # Optional, defaults to 'mastra-tracing'
 ```
 
 ### Basic Setup
 
-```typescript filename="src/mastra/index.ts"
+```typescript title="src/mastra/index.ts"
 import { Mastra } from "@mastra/core";
 import { BraintrustExporter } from "@mastra/braintrust";
 
@@ -48,7 +47,7 @@ export const mastra = new Mastra({
   observability: {
     configs: {
       braintrust: {
-        serviceName: 'my-service',
+        serviceName: "my-service",
         exporters: [
           new BraintrustExporter({
             apiKey: process.env.BRAINTRUST_API_KEY,
@@ -69,10 +68,10 @@ new BraintrustExporter({
   apiKey: process.env.BRAINTRUST_API_KEY!,
 
   // Optional settings
-  projectName: 'my-project',          // Default: 'mastra-tracing'
-  endpoint: 'https://api.braintrust.dev',  // Custom endpoint if needed
-  logLevel: 'info',                   // Diagnostic logging: debug | info | warn | error
-})
+  projectName: "my-project", // Default: 'mastra-tracing'
+  endpoint: "https://api.braintrust.dev", // Custom endpoint if needed
+  logLevel: "info", // Diagnostic logging: debug | info | warn | error
+});
 ```
 
 ## Related