new: Add Lab 3.8 release notes and docs update (#1523)

Co-authored-by: Matea Pesic <80577904+matea16@users.noreply.github.com>

Author: tonilastre

pages/memgraph-lab/features/custom-configuration.mdx

@@ -198,6 +198,10 @@ settings:
       value: 250000
     maxEdgeCount:
       value: 500000
+  query:
+    maxRecordCount:
+      value: 5000
+      isLocked: true
   graphRendering:
     maxNodeCount:
       value: 3500
@@ -709,6 +713,10 @@ settings:
     maxEdgeCount:
       value: 500000
       isLocked: false
+  query:
+    maxRecordCount:
+      value: 5000
+      isLocked: false
   graphRendering:
     maxNodeCount:
       value: 3500

pages/memgraph-lab/features/graphchat.mdx

@@ -28,8 +28,9 @@ authentication and usage settings. Each connection includes details like the
 endpoint, headers, retry logic, and model configurations.
 
 2. [**Add MCP connections (optional)**](#mcp-servers): Register
-remote MCP server connections in the Lab so GraphChat can use tools, elicitations,
-and samplings from those MCP servers to get additional context.
+remote MCP server connections in the Lab so GraphChat can use tools, prompts,
+resources, instructions, elicitations, and samplings from those MCP servers
+to get additional context.
 
 3. [**Create an agent**](#create-an-agent): Create an agent that uses any of
 the created LLM models and any number of registered MCP servers. You can also
@@ -330,8 +331,8 @@ GraphChat MCP integration supports:
 * Elicitations
 * Sampling
 * Instructions
-* Prompts (*Coming soon*)
-* Resources (*Coming soon*)
+* Prompts
+* Resources
 
 <Callout type="info">
 **Elicitation, sampling and instructions are supported from Lab 3.7.**
@@ -342,7 +343,14 @@ Agents will also use any **MCP instructions** provided by the server.
 These instructions can guide the agent's behavior or responses
 and are incorporated automatically whenever agent tools
 from an MCP server are active.
+</Callout>
+
+<Callout type="info">
+**Prompts and resources are supported from Lab 3.8.**
 
+Starting with Lab 3.8.0, GraphChat displays available
+prompts and resources from connected MCP servers, enabling
+you to incorporate them into your agentic workflows.
 </Callout>
 
 ![mcp-servers-settings](/pages/data-visualization/features/graphchat/mcp-servers-settings.png)
@@ -425,6 +433,33 @@ you can follow along in real time.
 
 ![chat-response-tool-call](/pages/data-visualization/features/graphchat/llm-response-tool-run.png)
 
+{<h4 className="custom-header">Prompts</h4>}
+
+Prompts are pre-built templates provided by your connected MCP
+servers that can be quickly used within GraphChat.
+
+These templates make it faster and easier to form questions or
+run common operations by reusing best-practice prompt patterns,
+which saves time and helps ensure your inquiries are more precise
+and effective.
+
+You can select a prompt from the available list and fill in the
+required details - or quickly open the prompt selection by
+typing `/` in the question input box—allowing you to get
+meaningful results with minimal effort.
+
+{<h4 className="custom-header">Resources</h4>}
+
+Resources are additional supporting information or snippets
+contributed by your connected MCP servers. They can enrich the
+context of your questions and provide useful background or
+predefined inputs for the GraphChat agent.
+
+You can browse available resources from your MCP servers and add
+them directly to your question, helping the agent generate even
+more relevant and accurate answers by leveraging specific examples,
+documentation, or configuration fragments.
+
 {<h4 className="custom-header">Sampling (LLM interaction requests)</h4>}
 
 Some MCP servers support **sampling** requests, which let
@@ -436,6 +471,23 @@ approval before they are processed. This means you stay in
 control, and your LLM connection can be harnessed for
 advanced agent tasks, safely and transparently.
 
+From **Lab 3.8** onward, you can enable automatic approvals for
+sampling requests to streamline your workflow. When a sampling
+request appears, you will see options to:
+
+- **Approve in this conversation**: This approves all future sampling
+  requests from that MCP server only within the current conversation
+  thread.
+- **Approve for this agent**: This approves any future sampling request
+  from that MCP server across all conversation threads associated with
+  the current agent.
+
+If you choose to approve for an agent, you can always revisit the agent's
+settings later to turn automatic approval for sampling requests on or off
+for each connected MCP server. This gives you granular control, letting
+you change permissions at any time to suit your preferences and security
+requirements.
+
 ![chat-response-sampling](/pages/data-visualization/features/graphchat/llm-response-sampling.png)
 
 {<h4 className="custom-header">Elicitation (Clarification requests)</h4>}

pages/memgraph-lab/querying.mdx

@@ -21,6 +21,10 @@ You can run Cypher queries in Memgraph Lab from several sections:
     - Edit the Graph Style Script (GSS) to control how results are visualized.
     - Set custom parameters for your queries.
     - Share queries with your team.
+    - View query results as either tabular data or in the graph view, allowing
+      you to inspect nodes, relationships, and paths.
+    - Access the query summary, which provides query statistics, a runtime breakdown,
+      and insights into the query's performance.
 2. [Run history](/memgraph-lab/features/run-history): Access and re-run
    previously executed queries. Each query opens in the Query execution view for
    further editing or inspection.
@@ -49,7 +53,6 @@ in Memgraph Lab. It includes:
 - [Query summary](#query-summary) – Get a breakdown of execution details,
   including runtime and metadata.
 
-
 ## Cypher editor
 
 The **Cypher editor** is the interface for writing and executing queries in
@@ -135,43 +138,55 @@ also improves performance by enabling query plan caching.
 
 ![](/pages/data-visualization/querying/parameters.png)
 
-
 ## Query status bar
 
 The **Query status bar** in Memgraph Lab provides real-time feedback and essential
-information about your queries.
+information about your query results.
 
 ![](/pages/data-visualization/querying/status-bar.png)
 
 The bar shows the following:
 
 - **Query execution status** - When the query has executed or failed, below the
-Cypher editor, you can see a *Query successful* message or an error.
-- [**Execution times**](#execution-times) - Lab full roundtrip time (ms) and
-  Memgraph execution time (ms)
+  Cypher editor, you can see a *Query successful* message or an error.
+- [**Execution times**](#execution-times) - Memgraph execution time (ms), with
+  the option to click the information icon for a full breakdown. This detailed
+  view shows how much time Memgraph Lab spent fetching results from the database
+  and how much was spent displaying them in the UI.
+
+![status-bar-runtime](/pages/data-visualization/querying/status-bar-runtime.png)
+
 - **Returned objects count** - The query status bar also shows the number of
-rows the query generated as well as nodes and relationships count the query
-returned (if any).
+  rows the query generated as well as nodes and relationships count the query
+  returned (if any).
+
+<Callout type="info">
+By default, Memgraph Lab displays a maximum of **5000 rows** per query result.
+
+If your query exceeds this limit, you'll see an indication that the results shown
+have been truncated. The status bar will also show the actual total row count your
+query would return. If needed, you can adjust this maximum row display limit in
+the Lab settings at any time.
+</Callout>
+
+![query-results-limit](/pages/data-visualization/querying/query-results-limit.png)
+
 - **Query actions** - From the Query status bar you can also copy the query to
-your clipboard or add it to an existing or new
-[collection](/memgraph-lab/features/collections).
+  your clipboard or add it to an existing or new [collection](/memgraph-lab/features/collections).
 
 When executing **multiple queries simultaneously**, the status bar allows you to
 navigate through each result set, ensuring you can efficiently manage and
 analyze multiple outputs.​
 
-![query-1](/pages/data-visualization/querying/query-1.png)
-
-![query-2](/pages/data-visualization/querying/query-2.png)
-
+![multiple-queries](/pages/data-visualization/querying/multiple-queries.png)
 
 ### Execution times
 
 In the case of successful execution, the Lab returns the query execution times -
 how much it took Lab to send the query to Memgraph and show results, and how
 long it took Memgraph to execute the query.
 
-![](/pages/data-visualization/lab-user-manual/execution-times.png)
+![status-bar-runtime](/pages/data-visualization/querying/status-bar-runtime.png)
 
 The **Lab full roundtrip time** indicates the total time from sending the query
 to receiving and rendering the results in Memgraph Lab. This metric is crucial

pages/release-notes.mdx

@@ -351,39 +351,41 @@ triggers with `SECURITY DEFINER`. Triggers now report the definer's identity
 correctly for auditing and role-based logic.
 [#3768](https://github.com/memgraph/memgraph/pull/3768)
 
-### Lab v3.8.0
+### Lab v3.8.0 - February 11th, 2026
+
+<LabReleasesClient version="3.8.0" />
 
 ## Previous releases
 
 ### Memgraph v3.7.2 - December 23rd, 2025
 
 {<h4 className="custom-header"> 🐞 Bug fixes</h4>}
 
-- Vector index recovery can now run in parallel, with additional improvements to 
-  index resizing and safer entry removal logic. This results in faster startup 
-  and schema recovery for databases with large vector indexes. Users can enable 
-  this behavior by starting Memgraph with 
-  `--storage-parallel-schema-recovery=true`. 
+- Vector index recovery can now run in parallel, with additional improvements to
+  index resizing and safer entry removal logic. This results in faster startup
+  and schema recovery for databases with large vector indexes. Users can enable
+  this behavior by starting Memgraph with
+  `--storage-parallel-schema-recovery=true`.
   [#3562](https://github.com/memgraph/memgraph/pull/3562)
-- Complete shutdown of coordinators and Settings held locally under main(). 
-  Avoids segfaults while destroying static objects in an uncontrolled order. 
-  Avoids unexpected errors from nuraft while shutting down or exiting. 
+- Complete shutdown of coordinators and Settings held locally under main().
+  Avoids segfaults while destroying static objects in an uncontrolled order.
+  Avoids unexpected errors from nuraft while shutting down or exiting.
   [#3567](https://github.com/memgraph/memgraph/pull/3567)
-- Fixed a bug where using SSO modules would cause username+password users to 
-  have wrong permissions. 
+- Fixed a bug where using SSO modules would cause username+password users to
+  have wrong permissions.
   [#3492](https://github.com/memgraph/memgraph/pull/3492)
-- Text index recovery now works correctly from snapshots even when the index 
-  directories are missing, allowing users to restore full-text indexes using 
-  only a snapshot, which was not possible before. Additionally, the Clear() 
-  function used during DROP GRAPH has been made safer to prevent intermediate 
+- Text index recovery now works correctly from snapshots even when the index
+  directories are missing, allowing users to restore full-text indexes using
+  only a snapshot, which was not possible before. Additionally, the Clear()
+  function used during DROP GRAPH has been made safer to prevent intermediate
   system states in case of failures.
   [#3570](https://github.com/memgraph/memgraph/pull/3570)
-- Snapshots can now be created on replicas too manually by user or by the 
-  scheduler thread. Users can expect a faster recovery on replica from a 
-  snapshot compared to a recovery from sequential WAL files only. 
+- Snapshots can now be created on replicas too manually by user or by the
+  scheduler thread. Users can expect a faster recovery on replica from a
+  snapshot compared to a recovery from sequential WAL files only.
   [#3420](https://github.com/memgraph/memgraph/pull/3420)
-- Fixed an AddressSanitizer-detected memory leak in HTTP POST requests by 
-  properly freeing the curl headers list. 
+- Fixed an AddressSanitizer-detected memory leak in HTTP POST requests by
+  properly freeing the curl headers list.
   [#3586](https://github.com/memgraph/memgraph/pull/3586)
 
 ### MAGE v3.7.2 - December 23rd, 2025