+ You are reading the documentation for {version}, the latest release. The + main docs follow the development branch and can describe features that are not released + yet.{' '} + + Go to the latest docs + + . +
++ You are reading the frozen documentation for {version}, which is no longer + maintained.{' '} + + Go to the latest docs + + . +
+
+ {t.label}
+ {active.label}
+
+ )
+ }
+
return (
+
+
+## OAuth2
+
+- [Apple](/v0.8.2/docs/configuration/authentication/OAuth2-OIDC/apple)
+- [Discord](/v0.8.2/docs/configuration/authentication/OAuth2-OIDC/discord)
+- [Facebook](/v0.8.2/docs/configuration/authentication/OAuth2-OIDC/facebook)
+- [GitHub](/v0.8.2/docs/configuration/authentication/OAuth2-OIDC/github)
+- [Google](/v0.8.2/docs/configuration/authentication/OAuth2-OIDC/google)
+
+## OpenID Connect
+
+- [Auth0](/v0.8.2/docs/configuration/authentication/OAuth2-OIDC/auth0)
+- [AWS Cognito](/v0.8.2/docs/configuration/authentication/OAuth2-OIDC/aws)
+- [Azure Entra/AD](/v0.8.2/docs/configuration/authentication/OAuth2-OIDC/azure)
+- [Keycloak](/v0.8.2/docs/configuration/authentication/OAuth2-OIDC/keycloak)
+- [Re-use OpenID Tokens for Login Session](/v0.8.2/docs/configuration/authentication/OAuth2-OIDC/token-reuse)
+
+## Troubleshooting OpenID Connect
+
+If you encounter issues with OpenID Connect authentication:
+
+1. **Enable Header Debug Logging**: Set `DEBUG_OPENID_REQUESTS=true` in your environment variables to log request headers in addition to URLs (with sensitive data masked). Note: Request URLs are always logged at debug level
+2. **Check Redirect URIs**: Ensure your callback URL matches exactly between your provider and LibreChat configuration
+3. **Verify Scopes**: Make sure all required scopes are properly configured
+4. **Review Provider Logs**: Check your identity provider's logs for authentication errors
+5. **Validate Tokens**: Ensure your provider is issuing valid tokens with the expected claims
+6. **Ensure _nonce_ is generated**: Some identity providers generate `nonce` url parameter if it's missing in the request. Set `OPENID_GENERATE_NONCE=true` to force the openid-client to generate it.
+
diff --git a/content/docs-archive/v0.8.2/configuration/authentication/OAuth2-OIDC/keycloak.mdx b/content/docs-archive/v0.8.2/configuration/authentication/OAuth2-OIDC/keycloak.mdx
new file mode 100644
index 000000000..7f1289bc8
--- /dev/null
+++ b/content/docs-archive/v0.8.2/configuration/authentication/OAuth2-OIDC/keycloak.mdx
@@ -0,0 +1,70 @@
+---
+title: Keycloak
+icon: KeyRound
+description: Learn how to configure LibreChat to use Keycloak for user authentication.
+---
+
+1. **Access Keycloak Admin Console:**
+- Open the Keycloak Admin Console in your web browser. This is usually
+found at a URL like `http://localhost:8080/auth/admin/`.
+
+2. **Create a Realm (if necessary):**
+- If you don't already have a realm for your application, create one. Click on 'Add Realm' and give it a name.
+
+3. **Create a Client:**
+- Within your realm, click on 'Clients' and then 'Create'.
+- Enter a client ID and select 'openid-connect' as the Client Protocol.
+- Set 'Client Authentication' to 'On'.
+- In 'Valid Redirect URIs', enter `http://localhost:3080/oauth/openid/callback` or the appropriate URI for
+your application.
+
+
+
+
+
+
+
+
+4. **Configure Client:**
+- After creating the client, you will be redirected to its settings page.
+- Note the 'Client ID' and 'Secret' from the 'Credentials' tab – you'll need these for your application.
+
+
+
+
+5. **Add Roles (Optional):**
+If you want to restrict access to users with specific roles, you can define roles in Keycloak and assign them to users.
+- Go to the 'Roles' tab in your client or realm (depending on where you want to define the roles).
+- Create roles that match the value(s) you have in `OPENID_REQUIRED_ROLE`.
+
+
+
+6. **Assign Roles to Users (Optional):**
+- Go to 'Users', select a user, and go to the 'Role Mappings' tab.
+- Assign at least one of the roles specified in `OPENID_REQUIRED_ROLE` to the user.
+
+
+
+7. **Get path of roles list inside token (Optional):**
+- Decode your jwtToken from OpenID provider and determine path for roles list inside access token. For example, if you are
+ using Keycloak, the path is `realm_access.roles`.
+- Put this path in `OPENID_REQUIRED_ROLE_PARAMETER_PATH` variable in `.env` file.
+- By parameter `OPENID_REQUIRED_ROLE_TOKEN_KIND` you can specify which token kind you want to use.
+ Possible values are `access` and `id`.
+
+8. **Update Your Project's Configuration:**
+- Open the `.env` file in your project folder and add the following variables:
+ ```bash filename=".env"
+ OPENID_ISSUER=http://localhost:8080/realms/[YourRealmName]
+ OPENID_CLIENT_ID=[YourClientID]
+ OPENID_CLIENT_SECRET=[YourClientSecret]
+ OPENID_SESSION_SECRET=[JustGenerateARandomSessionSecret]
+ OPENID_CALLBACK_URL=/oauth/openid/callback
+ OPENID_SCOPE="openid profile email"
+ OPENID_REQUIRED_ROLE=[YourRequiredRole] # Single role or comma-separated roles (e.g., role1,role2,admin)
+ OPENID_REQUIRED_ROLE_TOKEN_KIND=(access|id) # that means, `access` or `id`
+ OPENID_REQUIRED_ROLE_PARAMETER_PATH="realm_access.roles"
+
+ # Optional: redirects the user to the end session endpoint after logging out
+ OPENID_USE_END_SESSION_ENDPOINT=true
+ ```
diff --git a/content/docs-archive/v0.8.2/configuration/authentication/OAuth2-OIDC/meta.json b/content/docs-archive/v0.8.2/configuration/authentication/OAuth2-OIDC/meta.json
new file mode 100644
index 000000000..b96081a48
--- /dev/null
+++ b/content/docs-archive/v0.8.2/configuration/authentication/OAuth2-OIDC/meta.json
@@ -0,0 +1,21 @@
+{
+ "title": "OAuth2 & OIDC",
+ "icon": "KeyRound",
+ "pages": [
+ "index",
+ "---OAuth2---",
+ "apple",
+ "discord",
+ "facebook",
+ "github",
+ "google",
+ "---OIDC---",
+ "auth0",
+ "authelia",
+ "authentik",
+ "aws",
+ "azure",
+ "keycloak",
+ "token-reuse"
+ ]
+}
diff --git a/content/docs-archive/v0.8.2/configuration/authentication/OAuth2-OIDC/token-reuse.mdx b/content/docs-archive/v0.8.2/configuration/authentication/OAuth2-OIDC/token-reuse.mdx
new file mode 100644
index 000000000..8640994a7
--- /dev/null
+++ b/content/docs-archive/v0.8.2/configuration/authentication/OAuth2-OIDC/token-reuse.mdx
@@ -0,0 +1,144 @@
+---
+title: OpenID Connect Token Reuse
+icon: Fingerprint
+description: How to configure OpenID Connect token reuse with LibreChat
+---
+
+LibreChat supports reusing access and refresh tokens issued by your OpenID Connect provider (like Azure Entra ID or Auth0) to manage user authentication state. When this feature is active, the refresh token passed to the user as a cookie is issued by your OpenID provider instead of LibreChat, allowing LibreChat servers to refresh it and request access tokens from your provider.
+
+## Prerequisites
+
+- A configured OpenID Connect provider (like Azure Entra ID, Auth0, etc.)
+- Basic OpenID Connect setup completed
+
+## Configuration Steps
+
+1. Set `OPENID_REUSE_TOKENS=true` in your environment variables.
+
+## Provider-Specific Configuration
+
+### Auth0 Configuration
+
+
+ 
+
+
+
+ 
+
+
+
+
+
+## Session Expiry and Refresh Token
+
+- Default values: session expiry: 15 minutes, refresh token expiry: 7 days
+ - For more information: **[GitHub PR #927 - Refresh Token](https://github.com/danny-avila/LibreChat/pull/927)**
+
+
+ 
+
+
+
+ 
+
+
+
+
+## Production Setup
+
+Azure Blob Storage offers scalable, secure object storage that can be used as a CDN for your static assets such as images, CSS, and JavaScript. Follow these steps to configure your Azure Blob Storage for LibreChat.
+
+## 1. Create an Azure Storage Account
+
+1. **Sign in to Azure:**
+ - Open the [Azure Portal](https://portal.azure.com/) and sign in with your Microsoft account.
+
+2. **Create a Storage Account:**
+ - Click on **"Create a resource"** and search for **"Storage account"**.
+ - Click **"Create"** and fill in the required details:
+ - **Subscription & Resource Group:** Choose your subscription and either select an existing resource group or create a new one.
+ - **Storage Account Name:** Enter a unique name (e.g., `mylibrechatstorage`).
+ - **Region:** Select the region closest to your users.
+ - **Performance & Redundancy:** Choose the performance tier and redundancy level that best suit your needs.
+ - Click **"Review + Create"** and then **"Create"**. Wait until the deployment completes.
+
+## 2. Set Up Authentication
+
+You have two options for authenticating with your Azure Storage Account:
+
+### Option A: Using a Connection String
+
+1. **Navigate to Access Keys:**
+ - In your newly created storage account, go to **"Access keys"** in the sidebar.
+
+2. **Copy Connection String:**
+ - Copy one of the connection strings provided. This string includes the credentials required to connect to your Blob Storage account.
+
+### Option B: Using Managed Identity
+
+If your LibreChat application is running on an Azure service that supports Managed Identity (such as an Azure VM, App Service, or AKS), you can use that instead of a connection string.
+
+1. **Assign Managed Identity:**
+ - Ensure your Azure resource (VM, App Service, or AKS) has a system-assigned or user-assigned Managed Identity enabled.
+
+2. **Grant Storage Permissions:**
+ - In your storage account, assign the **Storage Blob Data Contributor** (or a similarly scoped role) to your Managed Identity. This allows your application to access Blob Storage without a connection string.
+
+## 3. Update Your Environment Variables
+
+Create or update your `.env` file in your project’s root with the following configuration:
+
+```bash filename=".env"
+# Option A: Using a Connection String
+AZURE_STORAGE_CONNECTION_STRING=DefaultEndpointsProtocol=https;AccountName=yourAccountName;AccountKey=yourAccountKey;EndpointSuffix=core.windows.net
+
+# Option B: Using Managed Identity (do not set the connection string if using Managed Identity)
+AZURE_STORAGE_ACCOUNT_NAME=yourAccountName
+
+AZURE_STORAGE_PUBLIC_ACCESS=false
+AZURE_CONTAINER_NAME=files
+```
+
+- **AZURE_STORAGE_CONNECTION_STRING:** Set this if you are using Option A.
+- **AZURE_STORAGE_ACCOUNT_NAME:** Set this if you are using Option B (Managed Identity). Do not set both.
+- **AZURE_STORAGE_PUBLIC_ACCESS:** Set to `false` if you do not want your blobs to be publicly accessible by default. Set to `true` if you need public access (for example, for publicly viewable images).
+- **AZURE_CONTAINER_NAME:** This is the container name your application will use (e.g., `files`). The application will automatically create this container if it doesn’t exist.
+
+## 4. Configure LibreChat to Use Azure Blob Storage
+
+Update your LibreChat configuration file (`librechat.yaml`) to specify that the application should use Azure Blob Storage for file handling:
+
+```yaml filename="librechat.yaml"
+version: 1.2.8
+cache: true
+fileStrategy: "azure_blob"
+```
+
+This setting tells LibreChat to use the Azure Blob Storage implementation provided in your code.
+
+---
+
+## Summary
+
+1. **Create a Storage Account:**
+Sign in to the Azure Portal, create a storage account, and wait for deployment to finish.
+
+2. **Set Up Authentication:**
+- **Option A:** Retrieve the connection string from **"Access keys"** in your storage account.
+- **Option B:** Use Managed Identity by enabling it on your Azure resource and granting it appropriate storage permissions.
+
+3. **Update Environment Variables:**
+In your `.env` file, set either:
+- `AZURE_STORAGE_CONNECTION_STRING` (for Option A), or
+- `AZURE_STORAGE_ACCOUNT_NAME` (for Option B), along with:
+- `AZURE_STORAGE_PUBLIC_ACCESS` and
+- `AZURE_CONTAINER_NAME`.
+
+4. **Configure LibreChat:**
+Set `fileStrategy` to `"azure_blob"` in your `librechat.yaml` configuration file.
+
+With these steps, your LibreChat application will automatically create the container (if it doesn't exist) and manage file uploads, downloads, and deletions using Azure Blob Storage as your CDN. Managed Identity provides a secure alternative by eliminating the need for long-term credentials.
+
+## Local Development with Azurite
+
+For local development and testing, you can use [Azurite](https://github.com/Azure/Azurite), an Azure Storage emulator that provides a local environment for testing your Azure Blob Storage integration without needing an actual Azure account.
+
+### 1. Set Up Azurite
+
+You can run Azurite in several ways:
+
+#### Option A: Using VS Code Extension (Recommended for Development)
+
+1. Install the [Azurite extension](https://marketplace.visualstudio.com/items?itemName=Azurite.azurite) for VS Code
+2. Open the command palette (Ctrl+Shift+P or Cmd+Shift+P)
+3. Search for and select "Azurite: Start"
+
+This will start Azurite in the background with default settings.
+
+#### Option B: Using Docker
+
+```bash
+docker run -p 10000:10000 -p 10001:10001 -p 10002:10002 mcr.microsoft.com/azure-storage/azurite
+```
+
+#### Option C: Using npm
+
+```bash
+npm install -g azurite
+azurite --silent --location /path/to/azurite/workspace --debug /path/to/debug/log
+```
+
+### 2. Configure Environment Variables for Local Development
+
+Add the following environment variables to your `.env` file:
+
+```bash filename=".env"
+# Azurite connection string for local development
+AZURE_STORAGE_CONNECTION_STRING="DefaultEndpointsProtocol=http;AccountName=devstoreaccount1;AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==;BlobEndpoint=http://127.0.0.1:10000/devstoreaccount1;"
+AZURE_STORAGE_PUBLIC_ACCESS=true
+AZURE_CONTAINER_NAME=files
+```
+
+Notes:
+- The `AccountKey` value is the default development key used by Azurite
+- The connection uses `http` protocol instead of `https` for local development
+- The `BlobEndpoint` points to the local Azurite instance running on port 10000
+
+### 3. Verify the Connection
+
+To verify that your application can connect to the local Azurite instance:
+
+1. Start your LibreChat application
+2. Attempt to upload a file through the interface
+3. Check the Azurite logs to confirm the connection and operations
+
+If you're using the VS Code extension, you can view the Azurite logs in the Output panel by selecting "Azurite Blob" from the dropdown.
+
+On this page
+ +
+
+
+
+ 
+
+
+
+ 
+
+
+
+
+
+Future updates will streamline configuration further by migrating some settings from your [.env file](/v0.8.2/docs/configuration/dotenv) to `librechat.yaml`.
+
+Stay tuned for ongoing enhancements to customize your LibreChat instance!
+
+**Note:** To verify your YAML config, you can use the [YAML Validator](/toolkit/yaml_checker) or other online tools like [yamlchecker.com](https://yamlchecker.com/)
+
+
+ 
+
+
+
+ 
+
+
+ 
+ - **From Settings Panel**: A dedicated "MCP Settings" section in the right panel lists all MCP servers with definable custom variables. Users can click on a server to open the configuration dialog to set or update their credentials for that specific MCP server.
+ 
+ - These user-provided values are stored securely, associated with the individual user and the specific MCP server, and substituted at runtime.
+- **Example:**
+ ```yaml
+ customUserVars:
+ MY_SERVICE_API_KEY:
+ title: "My Service API Key"
+ description: "Your personal API access key for My Service. Find it at My Service API Settings."
+ SOME_OTHER_VAR:
+ title: "Some Other Variable"
+ description: "The specific value for some other configuration (e.g., a specific path or identifier)."
+ ```
+ Usage in `headers`:
+ ```yaml
+ headers:
+ X-Auth-Token: "{{MY_SERVICE_API_KEY}}"
+ X-Some-Other-Config: "{{SOME_OTHER_VAR}}"
+ ```
+
+#### `oauth`
+
+- **Type:** Object (Optional)
+- **Description:** OAuth2 configuration for authenticating with the MCP server. When configured, users will be prompted to authenticate via OAuth flow before the MCP server can be used. If no client id & client secret is provided, Dynamic Client Registration (DCR) will be used.
+- **Required Subkeys:**
+ - `authorization_url`: String - The OAuth authorization endpoint URL
+ - `token_url`: String - The OAuth token endpoint URL
+ - `client_id`: String - OAuth client identifier
+ - `client_secret`: String - OAuth client secret
+ - `redirect_uri`: String - [OAuth redirect URI](/v0.8.2/docs/features/mcp#oauth-callback-url) (eg. `http://localhost:3080/api/mcp/${serverName}/oauth/callback`)
+ - `scope`: String - OAuth scopes (space-separated)
+- **Optional Subkeys:**
+ - `grant_types_supported`: Array of Strings - Supported grant types (defaults to `["authorization_code", "refresh_token"]`)
+ - `token_endpoint_auth_methods_supported`: Array of Strings - Supported token endpoint authentication methods (defaults to `["client_secret_basic", "client_secret_post"]`)
+ - `response_types_supported`: Array of Strings - Supported response types (defaults to `["code"]`)
+ - `code_challenge_methods_supported`: Array of Strings - Supported PKCE code challenge methods (defaults to `["S256", "plain"]`)
+ - `skip_code_challenge_check`: Boolean - Skip checking whether the OAuth provider advertises PKCE support. Useful for providers like AWS Cognito that support S256 but don't advertise it in their metadata. (defaults to `false`)
+- **Example:**
+ ```yaml
+ oauth-api-server:
+ authorization_url: https://api.example.com/oauth/authorize
+ token_url: https://api.example.com/oauth/token
+ client_id: your_client_id
+ client_secret: your_client_secret
+ redirect_uri: http://localhost:3080/api/mcp/oauth-api-server/oauth/callback
+ scope: "read execute"
+ grant_types_supported: ["authorization_code", "refresh_token"]
+ token_endpoint_auth_methods_supported: ["client_secret_post"]
+ response_types_supported: ["code"]
+ code_challenge_methods_supported: ["S256", "plain"]
+ ```
+
+#### `startup`
+
+- **Type:** Boolean (Optional)
+- **Description:** When set to `false`, this MCP server will not be connected at application startup. This is useful for servers that require user input or configuration before connecting, or for cases where you want to control when the server is initialized.
+- **Default Value:** `true`
+- **Example:**
+ ```yaml
+ mcpServers:
+ my-mcp-server:
+ type: streamable-http
+ url: "https://api.example.com/mcp/"
+ startup: false
+ ```
+
+### Notes
+
+- **Type Inference:**
+ - If `type` is omitted:
+ - If `url` is specified and starts with `http://` or `https://`, `type` defaults to `sse`.
+ - If `url` is specified and starts with `ws://` or `wss://`, `type` defaults to `websocket`.
+ - If `command` is specified, `type` defaults to `stdio`.
+- **Connection Types:**
+ - **`stdio`**: Starts an MCP server as a child process and communicates via standard input/output.
+ - **`websocket`**: Connects to an external MCP server via WebSocket.
+ - **`sse`**: Connects to an external MCP server via Server-Sent Events (SSE).
+ - **`streamable-http`**: Connects to an external MCP server via HTTP with support for streaming responses.
+- **Internal/Local Addresses:**
+ - **Important**: MCP servers using internal IP addresses (e.g., `172.24.1.165`, `192.168.1.100`), or local domains (e.g., `mcp-server`, `host.docker.internal`) **must** be explicitly allowed in [`mcpSettings.allowedDomains`](/v0.8.2/docs/configuration/librechat_yaml/object_structure/mcp_settings).
+ - See [MCP Settings](/v0.8.2/docs/configuration/librechat_yaml/object_structure/mcp_settings) for configuration details.
+
+## Examples
+
+### Configuration with Internal Addresses
+
+When using internal/local MCP servers, you must configure `mcpSettings.allowedDomains`:
+
+```yaml filename="Complete MCP Configuration with Internal Servers"
+# MCP Settings - Required for internal/local addresses
+mcpSettings:
+ allowedDomains:
+ - "172.24.1.165" # Internal IP
+ - "mcp-prod" # Docker container
+ - "host.docker.internal" # Docker host
+
+# MCP Servers - Individual configurations
+mcpServers:
+ prod-mcp:
+ type: streamable-http
+ url: http://172.24.1.165:8000/mcp
+ timeout: 120000
+
+ test-mcp:
+ type: streamable-http
+ url: http://mcp-prod:8001/mcp
+ timeout: 120000
+```
+
+### `stdio` MCP Server
+
+```yaml filename="stdio MCP Server"
+puppeteer:
+ type: stdio
+ command: npx
+ args:
+ - -y
+ - "@modelcontextprotocol/server-puppeteer"
+ timeout: 30000
+ initTimeout: 10000
+ env:
+ NODE_ENV: "production"
+ USER_EMAIL: "{{LIBRECHAT_USER_EMAIL}}"
+ USER_ROLE: "{{LIBRECHAT_USER_ROLE}}"
+ stderr: inherit
+```
+
+### `sse` MCP Server
+
+```yaml filename="sse MCP Server"
+everything:
+ url: http://localhost:3001/sse
+ headers:
+ X-User-ID: "{{LIBRECHAT_USER_ID}}"
+ X-API-Key: "${SOME_API_KEY}"
+```
+
+### `websocket` MCP Server
+
+```yaml filename="websocket MCP Server"
+myWebSocketServer:
+ url: ws://localhost:8080
+```
+
+### `streamable-http` MCP Server
+
+```yaml filename="streamable-http MCP Server"
+streamable-http-server:
+ type: streamable-http
+ url: https://example.com/api/
+ headers:
+ X-User-ID: "{{LIBRECHAT_USER_ID}}"
+ X-API-Key: "${SOME_API_KEY}"
+```
+
+### MCP Server with Dynamic User Fields
+
+```yaml filename="MCP Server with User Fields"
+user-aware-server:
+ type: sse
+ url: https://api.example.com/users/{{LIBRECHAT_USER_USERNAME}}/stream
+ headers:
+ X-User-ID: "{{LIBRECHAT_USER_ID}}"
+ X-User-Email: "{{LIBRECHAT_USER_EMAIL}}"
+ X-User-Role: "{{LIBRECHAT_USER_ROLE}}"
+ X-Email-Verified: "{{LIBRECHAT_USER_EMAILVERIFIED}}"
+ Authorization: "Bearer ${API_TOKEN}"
+```
+
+### MCP Server with Per-User Credentials via `customUserVars`
+
+```yaml filename="MCP Server with customUserVars"
+my-mcp-server:
+ type: streamable-http
+ url: "https://api.example-service.com/api/" # Example URL
+ headers:
+ X-Auth-Token: "{{API_KEY}}" # Uses the API_KEY defined below
+ customUserVars:
+ API_KEY: # This key will be used as {{API_KEY}} in headers/url
+ title: "API Key" # This is the label shown above the input field
+ description: "Get your API key here." # This description appears below the input
+ startup: false # This server will not be connected at application startup since it requires the information provided by the user in customUserVars.
+```
+
+ **NOTE** See [MCP Server Initialization](/v0.8.2/docs/features/mcp#server-initialization) for more information about UI based server initialization.
+
+### MCP Server with Custom Icon
+
+```yaml filename="MCP Server with Icon"
+filesystem:
+ command: npx
+ args:
+ - -y
+ - "@modelcontextprotocol/server-filesystem"
+ - /home/user/LibreChat/
+ iconPath: /home/user/LibreChat/client/public/assets/logo.svg
+ chatMenu: false # Exclude from chatarea dropdown
+```
+
+### MCP Server with OAuth Authentication
+
+```yaml filename="MCP Server with OAuth"
+oauth-api-server:
+ type: streamable-http
+ url: https://api.example.com/mcp/
+ oauth:
+ authorization_url: https://api.example.com/oauth/authorize
+ token_url: https://api.example.com/oauth/token
+ client_id: your_client_id
+ client_secret: your_client_secret
+ redirect_uri: http://localhost:3080/api/mcp/oauth-api-server/oauth/callback
+ scope: "read execute"
+```
+
+### MCP Server with Server Instructions
+
+```yaml filename="MCP Server with Instructions"
+# Server that uses its own provided instructions
+web-search:
+ type: streamable-http
+ url: https://example.com/mcp/search
+ serverInstructions: true
+
+# Server with instructions explicitly disabled
+filesystem:
+ command: npx
+ args:
+ - -y
+ - "@modelcontextprotocol/server-filesystem"
+ - /home/user/documents/
+ serverInstructions: false
+
+# Server with custom instructions
+puppeteer:
+ type: stdio
+ command: npx
+ args:
+ - -y
+ - "@modelcontextprotocol/server-puppeteer"
+ serverInstructions: |
+ Browser automation security and best practices:
+ 1. Be cautious with local file access and internal IP addresses
+ 2. Take screenshots to verify successful page interactions
+ 3. Wait for page elements to load before interacting with them
+ 4. Use specific CSS selectors for reliable element targeting
+ 5. Check console logs for JavaScript errors when troubleshooting
+```
+
+### OAuth-Enabled MCP Server (Legacy requiresOAuth)
+
+```yaml filename="OAuth-Enabled MCP Server"
+composio-googlesheets:
+ type: sse
+ url: https://mcp.composio.dev/googlesheets/sse-endpoint
+ requiresOAuth: true
+ headers:
+ X-User-ID: "{{LIBRECHAT_USER_ID}}"
+ X-API-Key: "${COMPOSIO_API_KEY}"
+ timeout: 45000
+ initTimeout: 15000
+```
+
+**Related Environment Variables (Optional):**
+```bash
+# OAuth configuration for MCP servers
+MCP_OAUTH_ON_AUTH_ERROR=true
+MCP_OAUTH_DETECTION_TIMEOUT=10000
+
+# API key for the service
+COMPOSIO_API_KEY=your_composio_api_key_here
+```
+
+---
+
+**Importing MCP Server Configurations**
+
+The `mcpServers` configurations allow LibreChat to dynamically interact with various MCP servers, which can perform specialized tasks or provide specific functionalities within the application. This modular approach facilitates extending the application's capabilities by simply adding or modifying server configurations.
+
+---
+
+## Additional Information
+
+- **Default Behavior:**
+ - Initialization happens at startup, and the app must be restarted for changes to take effect.
+ - If both `url` and `command` are specified, the `type` must be explicitly defined to avoid ambiguity.
+- **Multi-User Support:**
+ - The MCPManager now supports distinct user-level and app-level connections, enabling proper connection management per user.
+ - User connections are tracked and managed separately, with proper establishment and cleanup.
+ - Use dynamic user field placeholders in headers, URLs, and environment variables:
+ - `{{LIBRECHAT_USER_ID}}` - User's unique identifier
+ - `{{LIBRECHAT_USER_EMAIL}}` - User's email address
+ - `{{LIBRECHAT_USER_USERNAME}}` - User's username
+ - `{{LIBRECHAT_USER_ROLE}}` - User's role (e.g., "user", "admin")
+ - And many more fields (see headers section for complete list)
+- **User Idle Management:**
+ - User connections are monitored for activity and will be disconnected after 15 minutes of inactivity.
+- **Environment Variables:**
+ - **In `env` (for `stdio` type):** Useful for setting up specific runtime environments or configurations required by the MCP server process.
+ - **In `headers` (for `sse` and `streamable-http` types):** Use `${ENV_VAR}` syntax to reference environment variables in header values.
+- **Dynamic User Fields:**
+ - User field placeholders are replaced at runtime with the authenticated user's information
+ - Only non-sensitive fields are available (passwords and other sensitive data are excluded)
+ - Missing fields default to empty strings
+ - Boolean fields are converted to string representations ("true" or "false")
+- **Error Handling (`stderr`):**
+ - Configuring `stderr` allows you to manage how error messages from the MCP server process are handled. The default `"inherit"` means that the errors will be printed to the parent process's `stderr`.
+- **Server Instructions:**
+ - Instructions are automatically injected into the agent's system message when MCP server tools are used
+ - Custom instructions (string values) take precedence over server-provided instructions
+ - Multiple MCP servers can each contribute their own instructions to the agent context
+ - Instructions are only included when the corresponding MCP server's tools are actually available to the agent
+- **OAuth Authentication:**
+ - OAuth2 flow is supported for secure authentication with MCP servers
+ - Users will be prompted to authenticate via OAuth before the MCP server can be used
+
+## References
+
+- [Model Context Protocol (MCP) Documentation](https://github.com/modelcontextprotocol)
+- [MCP Transports Specification](https://modelcontextprotocol.io/specification/draft/basic/transports)
+- [Node.js child_process.spawn](https://nodejs.org/api/child_process.html#child_processspawncommand-args-options)
+
+---
+
+By properly configuring the `mcpServers` in your `librechat.yaml`, you can enhance LibreChat's functionality and integrate custom tools and services seamlessly.
diff --git a/content/docs-archive/v0.8.2/configuration/librechat_yaml/object_structure/mcp_settings.mdx b/content/docs-archive/v0.8.2/configuration/librechat_yaml/object_structure/mcp_settings.mdx
new file mode 100644
index 000000000..c90244667
--- /dev/null
+++ b/content/docs-archive/v0.8.2/configuration/librechat_yaml/object_structure/mcp_settings.mdx
@@ -0,0 +1,116 @@
+---
+title: "MCP Settings Object Structure"
+icon: Blocks
+---
+
+## Overview
+
+The `mcpSettings` configuration provides global settings for MCP (Model Context Protocol) server security and behavior. This configuration is separate from `mcpServers` and controls how MCP servers can connect to certain domains and IP addresses.
+
+## Example
+
+```yaml filename="MCP Settings Object Structure"
+# Example MCP Settings Configuration
+mcpSettings:
+ allowedDomains:
+ - "example.com" # Specific domain
+ - "*.example.com" # All subdomains using wildcard
+ - "mcp-server" # Local Docker domain
+ - "172.24.1.165" # Internal network IP
+ - "https://api.example.com:8443" # With protocol and port
+```
+
+## Configuration
+
+### Subkeys
+
+
+ 
+ 
+
+
+```
+
+### How to Upload Images and Videos on GitHub
+
+
+
+
+
+
+Hello
+}
+```
+````
diff --git a/content/docs-archive/v0.8.2/features/agents.mdx b/content/docs-archive/v0.8.2/features/agents.mdx
new file mode 100644
index 000000000..96e260445
--- /dev/null
+++ b/content/docs-archive/v0.8.2/features/agents.mdx
@@ -0,0 +1,432 @@
+---
+title: AI Agents
+icon: Bot
+description: Learn how to create, customize, and leverage LibreChat's AI Agents - a powerful framework for building custom AI assistants with any model provider.
+---
+
+LibreChat's AI Agents feature provides a flexible framework for creating custom AI assistants powered by various model providers.
+
+This feature is similar to OpenAI's Assistants API and ChatGPT's GPTs, but with broader model support and a no-code implementation, letting you build sophisticated assistants with specialized capabilities.
+
+## Getting Started
+
+To create a new agent, select "Agents" from the endpoint menu and open the Agent Builder panel found in the Side Panel.
+
+
+
+The creation form includes:
+
+- **Avatar**: Upload a custom avatar to personalize your agent
+- **Name**: Choose a distinctive name for your agent
+- **Description**: Optional details about your agent's purpose
+- **Instructions**: System instructions that define your agent's behavior
+- **Model**: Select from available providers and models
+
+**Existing agents can be selected from the top dropdown of the Side Panel.**
+- **Also by mention with "@" in the chat input.**
+
+
+
+### Model Configuration
+
+The model parameters interface allows fine-tuning of your agent's responses:
+
+- Temperature (0-1 scale for response creativity)
+- Max context tokens
+- Max output tokens
+- Additional provider-specific settings
+
+## Agent Capabilities
+
+> **Note:** All capabilities can be toggled via the `librechat.yaml` configuration file. See [docs/configuration/librechat_yaml/object_structure/agents#capabilities](/v0.8.2/docs/configuration/librechat_yaml/object_structure/agents#capabilities) for more information.
+
+### Code Interpreter
+
+When enabled, the Code Interpreter capability allows your agent to:
+- Execute code in multiple languages, including:
+ - Python, JavaScript, TypeScript, Go, C, C++, Java, PHP, Rust, and Fortran
+- Process files securely through the LibreChat Code Interpreter API
+- Run code without local setup, configuration, or sandbox deployment
+- Handle file uploads and downloads seamlessly
+- [More info about the Code Interpreter API](/v0.8.2/docs/features/code_interpreter)
+ - **Requires an API Subscription from [code.librechat.ai](https://code.librechat.ai/pricing)**
+
+### File Search
+
+The File Search capability enables:
+- RAG (Retrieval-Augmented Generation) functionality
+- Semantic search across uploaded documents
+- Context-aware responses based on file contents
+- File attachment support at both agent and chat thread levels
+
+### File Context
+
+The File Context capability allows your agent to store extracted text from files as part of its system instructions:
+
+- Extract text while maintaining document structure and formatting
+- Process complex layouts including multi-column text and mixed content
+- Handle tables, equations, and other specialized content
+- Work with multilingual content
+- Text is stored in the agent's instructions in the database
+- **No OCR service required** - Uses text parsing by default with fallback methods
+- **Enhanced by OCR** - If OCR is configured, extraction quality improves for images and scanned documents
+- Uses the same processing logic as "Upload as Text": **OCR > STT > text parsing**
+- [More info about OCR configuration](/v0.8.2/docs/features/ocr)
+
+**Note:** File Context includes extracted text in the agent's system instructions. For temporary document questions in individual conversations, use [Upload as Text](/v0.8.2/docs/features/upload_as_text) from the chat instead.
+
+### Model Context Protocol (MCP)
+
+MCP is an open protocol that standardizes how applications provide context to Large Language Models (LLMs), acting like a universal adapter for AI tools and data sources.
+
+For more information, see documentation on [MCP](/v0.8.2/docs/features/mcp).
+
+#### Agents with MCP Tools
+
+
+1. Configure MCP servers in your `librechat.yaml` file
+2. Restart LibreChat to initialize the connections
+3. Create or edit an agent
+4. Click the "Add Tools" button in the Agent Builder panel to open the Tools Dialog shown below
+5. Select the MCP server(s) you want to add - each server appears as a single entry
+6. Save your changes to the agent
+
+In this example, we've added the **[Spotify MCP server](https://github.com/LibreChat-AI/spotify-mcp)** to an agent.
+
+
+
+#### Managing MCP Tools
+
+Once an MCP server is added to an agent, you can fine-tune which specific tools are available:
+
+- After adding an MCP server, expand it to see all available tools
+- Check/uncheck individual tools as needed
+- For example, the Spotify MCP server provides ~20 tools (search, playback control, playlist management, etc.)
+- This granular control lets you limit agents to only the tools they need
+
+
+
+Learn More:
+- [Configuring MCP Servers](/v0.8.2/docs/features/mcp)
+- [Model Context Protocol Introduction](https://modelcontextprotocol.io/introduction)
+
+### Artifacts
+
+The Artifacts capability enables your agent to generate and display interactive content:
+
+- Create React components, HTML code, and Mermaid diagrams
+- Display content in a separate UI window for clarity and interaction
+- Configure artifact-specific instructions at the agent level
+- [More info about Artifacts](/v0.8.2/docs/features/artifacts)
+
+When enabled, additional instructions specific to the use of artifacts are added by default. Options include:
+
+- **Enable shadcn/ui instructions**: Adds instructions for using shadcn/ui components (a collection of re-usable components built using Radix UI and Tailwind CSS)
+- **Custom Prompt Mode**: When enabled, the default artifacts system prompt will not be included, allowing you to provide your own custom instructions
+
+Configuring artifacts at the agent level is the preferred approach, as it allows for more granular control compared to the legacy app-wide configuration.
+
+If you enable Custom Prompt Mode, you should include at minimum the basic artifact format in your instructions.
+
+Here's a simple example of the minimum instructions needed:
+
+````md
+When creating content that should be displayed as an artifact, use the following format:
+
+:::artifact{identifier="unique-identifier" type="mime-type" title="Artifact Title"}
+```
+Your artifact content here
+```
+:::
+
+For the type attribute, use one of:
+- "text/html" for HTML content
+- "application/vnd.mermaid" for Mermaid diagrams
+- "application/vnd.react" for React components
+- "image/svg+xml" for SVG images
+````
+
+### Tools
+
+Agents can also be enhanced with various built-in tools:
+
+- **[OpenAI Image Tools](/v0.8.2/docs/features/image_gen#1--openai-image-tools-recommended)**: Image generation & editing using **[GPT-Image-1](https://platform.openai.com/docs/models/gpt-image-1)**
+- **[DALL-E-3](/v0.8.2/docs/features/image_gen#2--dalle-legacy)**: Image generation from text descriptions
+- **[Stable Diffusion](/v0.8.2/docs/features/image_gen#3--stable-diffusion-local)** / **[Flux](/v0.8.2/docs/features/image_gen#4--flux)**: Text-to-image generation
+- **[Wolfram](/v0.8.2/docs/configuration/tools/wolfram)**: Computational and mathematical capabilities
+- **[OpenWeather](/v0.8.2/docs/configuration/tools/openweather)**: Weather data retrieval
+- **[Google Search](/v0.8.2/docs/configuration/tools/google_search)**: Access to web search functionality
+- **Calculator**: Mathematical calculations
+- **Tavily Search**: Advanced search API with diverse data source integration
+- **Azure AI Search**: Information retrieval
+- **Traversaal**: A robust search API for LLM Agents
+
+- Tools can be disabled using the [`librechat.yaml`](/v0.8.2/docs/configuration/librechat_yaml) configuration file:
+ - [More info](/v0.8.2/docs/configuration/librechat_yaml/object_structure/agents#capabilities)
+
+### Actions
+
+With the Actions capability, you can dynamically create tools from [OpenAPI specs](https://swagger.io/specification/) to add to your Agents.
+
+
+
+**Clicking the button above will open a form where you can input the OpenAPI spec URL and create an action:**
+
+
+
+- Actions can be disabled using the [`librechat.yaml`](/v0.8.2/docs/configuration/librechat_yaml) configuration file:
+ - [More info](/v0.8.2/docs/configuration/librechat_yaml/object_structure/agents#capabilities)
+- Individual domains can be whitelisted for agent actions:
+ - [More info](/v0.8.2/docs/configuration/librechat_yaml/object_structure/actions#alloweddomains)
+- Note that you can add add the 'x-strict': true flag at operation-level in the OpenAPI spec for actions.
+If using an OpenAI model supporting it, this will automatically generate function calls with 'strict' mode enabled.
+ - Strict mode supports only a partial subset of json. Read https://platform.openai.com/docs/guides/structured-outputs/some-type-specific-keywords-are-not-yet-supported for details.
+
+### Agent Chain
+
+The Agent Chain capability enables a Mixture-of-Agents (MoA) approach, allowing you to create a sequence of agents that work together:
+
+- Create chains of specialized agents for complex tasks
+- Each agent in the chain can access outputs from previous agents
+- Configure the maximum number of steps for the agent chain
+- **Note:** Access this feature from the Advanced Settings panel in the Agent Builder
+- **Note:** This feature is currently in beta and may be subject to change
+ - The current maximum of agents that can be chained is 10, but this may be configurable in the future
+
+
+
+This feature introduces a layered Mixture-of-Agents architecture to LibreChat, where each agent takes all the outputs from agents in the previous layer as auxiliary information in generating its response, as described in [the eponymous "Mixture-of-Agents" paper](https://arxiv.org/abs/2406.04692).
+
+### Advanced Settings
+
+Advanced settings for your agent (found in the Advanced view of the Agent form) outside of "capabilities."
+
+#### Max Agent Steps
+
+This setting allows you to limit the number of steps an agent can take in a "run," which refers to the agent loop before a final response is given.
+
+If left unconfigured, the default is 25 steps, but you can adjust this to suit your needs. For admins, you can set a global default as well as a global maximum in the [`librechat.yaml`](/v0.8.2/docs/configuration/librechat_yaml/object_structure/agents#recursionlimit) file.
+
+A "step" refers to either an AI API request or a round of tool usage (1 or many tools, depending on how many tool calls the LLM provides from a single request).
+
+A single, non-tool response is 1 step. A singular round of tool usage is usually 3 steps:
+
+1. API Request -> 2. Tool Usage (1 or many tools) -> 3. Follow-up API Request
+
+## File Management
+
+Agents support multiple ways to work with files:
+
+### In Chat Interface
+
+When chatting with an agent, you have four upload options:
+
+1. **Upload Images**
+ - Uploads images for native vision model support
+ - Sends images directly to the model provider
+
+2. **Upload as Text** (requires `context` capability)
+ - Extracts and includes full document content in conversation
+ - Uses text parsing by default; enhanced by OCR if configured
+ - Content exists only in current conversation
+ - See [Upload as Text](/v0.8.2/docs/features/upload_as_text)
+
+3. **Upload for File Search** (requires `file_search` capability, toggled ON)
+ - Uses semantic search (RAG) with vector stores
+ - Returns relevant chunks via tool use
+ - Optimal for large documents/multiple files
+ - Sub-optimal for structured data (CSV, Excel, JSON, etc.)
+
+4. **Upload for Code Interpreter** (requires `execute_code` capability, toggled ON)
+ - Adds files to code interpreter environment
+ - Optimal for structured data (CSV, Excel, JSON, etc.)
+ - More info about [Code Interpreter](/v0.8.2/docs/features/code_interpreter)
+
+### In Agent Builder
+
+When configuring an agent, you can attach files in different categories:
+
+1. **Image Upload**: For visual content the agent can reference
+2. **File Search Upload**: Documents for RAG capabilities
+3. **Code Interpreter Upload**: Files for code processing
+4. **File Context**: Documents with extracted text to supplement agent instructions
+
+**File Context** uses the `context` capability and works just like ["Upload as Text"](/v0.8.2/docs/features/upload_as_text) - it uses text parsing by default and is enhanced by OCR when configured. Text is extracted at upload time and stored in the agent's instructions. This is ideal for giving agents persistent knowledge from documents, PDFs, code files, or images with text.
+
+**Processing priority:** OCR > STT > text parsing (same as Upload as Text)
+
+**Note:** The extracted text is included as part of the agent's system instructions.
+
+## Sharing and Permissions
+
+### Administrator Controls
+
+Administrators have access to global permission settings within the agent builder UI:
+
+- Enable/disable agent sharing across all users
+- Control agent usage permissions
+- Manage agent creation rights
+- Configure platform-wide settings
+
+The first account created for your instance is an administrator. If you need to add an additional administrator, you may [access MongoDB](/v0.8.2/docs/configuration/mongodb/mongodb_auth) and update the user's profile:
+
+```
+db.users.updateOne(
+ { email: 'USER_EMAIL_ADDRESS' },
+ { $set: { role: 'ADMIN' } }
+)
+```
+
+The use of agents for all users can also be disabled via config, [more info](/v0.8.2/docs/configuration/librechat_yaml/object_structure/interface).
+
+### User-Level Sharing
+
+Individual users can:
+- Share their agents with all users (if enabled)
+- Control editing permissions for shared agents
+- Manage access to their created agents
+
+### Notes
+
+- Instructions, model parameters, attached files, and tools are only exposed to the user if they have editing permissions
+ - An agent may leak any attached data, whether instructions or files, through conversation--make sure your instructions are robust against this
+- Only original authors and administrators can delete shared agents
+- Agents are private to authors unless shared
+
+## Optional Configuration
+
+LibreChat allows admins to configure the use of agents via the [`librechat.yaml`](/v0.8.2/docs/configuration/librechat_yaml) file:
+
+- Disable Agents for all users (including admins): [more info](/v0.8.2/docs/configuration/librechat_yaml/object_structure/interface)
+- Customize agent capabilities using: [more info](/v0.8.2/docs/configuration/librechat_yaml/object_structure/agents)
+
+## Best Practices
+
+- Provide clear, specific instructions for your agent
+- Carefully consider which tools are necessary for your use case
+- Organize files appropriately across the four upload categories
+- Review permission settings before sharing agents
+- Test your agent thoroughly before deploying to other users
+
+## Recap
+
+1. Select "Agents" from the endpoint dropdown menu
+2. Open the Agent Builder panel
+3. Fill out the required agent details
+4. Configure desired capabilities (Code Interpreter, File Search, File Context, etc.)
+5. Add necessary tools and files
+6. Set sharing permissions if desired
+7. Create and start using your agent
+
+When chatting with agents, you can:
+- Use "Upload as Text" to include full document content in conversations (text parsing by default, enhanced by OCR)
+- Use "Upload for File Search" for semantic search over documents (requires RAG API)
+- Add files to agent's "File Context" to included a file's full content as part of the agent's system instructions
+
+## Migration Required (v0.8.0-rc3+)
+
+
+
+
+
+## Key Features of LibreChat's Code Artifacts:
+
+- Instant prototyping of websites and UIs with generative AI
+- Effortless creation of dynamic, responsive layouts
+- Interactive learning environment for React and HTML
+- Complex idea visualization using Mermaid diagrams
+- AI-powered intuitive, user-centric design iterations
+- Free and open-source alternative to paid AI tools
+
+Experience the future of UI/UX design and development with LibreChat's generative capabilities. Bring your ideas to life faster than ever before!
+
+## Content-Security-Policy
+
+You may need to need to update your web server's Content-Security-Policy to include `frame-src 'self' https://*.codesandbox.io` in order to load generated HTML apps in the Artifacts panel. This is a dependency of the [sandpack](https://sandpack.codesandbox.io/) library.
+
+## Self-Hosting the Sandpack Bundler
+
+Artifacts in LibreChat use CodeSandbox's Sandpack library to securely render HTML/JS code. By default, LibreChat connects to CodeSandbox's public CDN, which may also transmit telemetry for its usage.
+
+For enhanced privacy, security compliance, or isolated network environments, you can [self-host the bundler.](https://sandpack.codesandbox.io/docs/guides/hosting-the-bundler)
+
+### Why Self-Host the Sandpack Bundler?
+
+[Self-hosting the bundler](https://sandpack.codesandbox.io/docs/guides/hosting-the-bundler) provides several advantages:
+
+- **Privacy & Security**: Keep code execution within your own infrastructure
+- **Reliability**: Remove dependency on external services
+- **Performance**: Reduce latency by hosting the bundler in your network
+- **Compliance**: Meet organizational data handling requirements
+- **Control**: Configure and customize to your specific needs
+
+### Configuration
+
+Once you have a self-hosted bundler set up, simply configure LibreChat to use it by setting the environment variable:
+
+```bash
+# `.env` file
+SANDPACK_BUNDLER_URL=http://your-bundler-url
+```
+
+### General Considerations
+
+Self-hosting the bundler introduces some additional overhead:
+
+- **CORS Configuration**: You'll need to manage cross-origin resource sharing policies
+- **Security Management**: You become responsible for the security of the bundler service
+- **Maintenance**: Updates and patches will need to be applied manually
+- **Resource Requirements**: Additional server resources will be needed to host the bundler
+
+For detailed instructions on setting up and maintaining your self-hosted bundler, refer to the [forked CodeSandbox repository](https://github.com/LibreChat-AI/codesandbox-client) tailored for LibreChat deployment, including the removal of telemetry from Sandpack.
+
+---
+
+AI News 2024: The Original and BEST Open-Source AI Chat Platform, LibreChat Releases Code Artifacts! This Generative UI Tool Can Generate React, HTML & Diagrams Instantly from a Single Prompt in Your Browser with Any LLM, OpenAI, Anthropic, LLAMA, Mistral, DeepSeek Coder & More Thanks to OLLAMA Integration.
+
+#AINews2024 #OpenSourceAI #GenerativeUI #CodeArtifacts #WebDevelopment #ReactJS #LLM #AIPrototyping #DevTools #OLLAMA #LibreChat
diff --git a/content/docs-archive/v0.8.2/features/authentication.mdx b/content/docs-archive/v0.8.2/features/authentication.mdx
new file mode 100644
index 000000000..48d62a5b5
--- /dev/null
+++ b/content/docs-archive/v0.8.2/features/authentication.mdx
@@ -0,0 +1,30 @@
+---
+title: Authentication
+icon: Lock
+description: Quick overview of the user authentication system of LibreChat, which offers secure and easy email and social logins.
+---
+
+
+LibreChat has a user authentication system that allows users to sign up and log in securely and easily. The system is scalable and can handle a large number of concurrent users without compromising performance or security.
+
+By default, we have email signup and login enabled, which means users can create an account using their email address and a password. They can also reset their password if they forget it.
+
+Additionally, our system can integrate social logins from various platforms such as Google, GitHub, Discord, OpenID, and more. This means users can log in using their existing accounts on these platforms, without having to create a new account or remember another password.
+
+**For further details, refer to the configuration guides provided here: [Authentication](/v0.8.2/docs/configuration/authentication)**
+
+
+
diff --git a/content/docs-archive/v0.8.2/features/code_interpreter.mdx b/content/docs-archive/v0.8.2/features/code_interpreter.mdx
new file mode 100644
index 000000000..28bdfac04
--- /dev/null
+++ b/content/docs-archive/v0.8.2/features/code_interpreter.mdx
@@ -0,0 +1,149 @@
+---
+title: Code Interpreter API
+icon: SquareTerminal
+description: Execute code securely and manage files seamlessly with LibreChat's Code Interpreter API
+---
+
+## Introduction
+
+LibreChat's Code Interpreter API provides a secure and hassle-free way to execute code and manage files through a simple API interface. Whether you're using it through LibreChat's Agents or integrating it directly into your applications, the API offers a powerful sandbox environment for running code in multiple programming languages.
+
+
+
+## Subscription
+**Access to this feature requires an [API subscription, get started here](https://code.librechat.ai/pricing).**
+
+## Getting Started
+
+1. Visit [code.librechat.ai](https://code.librechat.ai/pricing) to get your API key
+2. Integrate the API into your application or use it through LibreChat
+3. Start executing code and generating files securely
+
+## Key Features
+
+### Supported Languages
+
+Execute code in multiple programming languages:
+- Python, Node.js (JS/TS), Go, C/C++, Java, PHP, Rust, Fortran, Rscript
+
+### Seamless File Handling
+
+- Upload files for processing
+- Download generated outputs
+- Secure file management
+- Session-based file organization
+
+### Security & Convenience
+
+- Secure sandboxed execution environment
+- No local setup required
+- No server deployment needed
+- No configuration management
+
+## Using the API
+
+### In LibreChat
+
+The API has first-class support in LibreChat through two main methods:
+
+1. **[AI Agents](/v0.8.2/docs/features/agents#code-interpreter)**: Enable Code Interpreter in your agent's configuration to allow it to execute code and process files automatically.
+
+2. **Manual Execution**: Use the "Run Code" button in code blocks within the chat interface, as shown here:
+
+
+
+### Set up API key
+
+- **Per-user setup:** input your API key in LibreChat when prompted (using the above methods)
+- **Global setup:** use `LIBRECHAT_CODE_API_KEY` environment variable in the .env file of your project (provides access to all users)
+
+### Direct API Integration
+
+The Code Interpreter API can be integrated into any application using a simple API key authentication:
+
+1. Get your API key from [code.librechat.ai](https://code.librechat.ai/pricing)
+2. Include the API key in your requests using the `x-api-key` header
+
+### Enterprise
+
+The enterprise plan requires use of the `LIBRECHAT_CODE_BASEURL` environment variable to correspond with the self-hosted instance of the API, along with any generated API keys from the dashboard, used the same way as mentioned above.
+
+## Core Functionality
+
+### Code Execution
+
+- Run code snippets in supported languages
+- Receive stdout/stderr output
+- Get execution statistics (memory usage, CPU time)
+- Handle program arguments
+- Access execution status and results
+
+### File Operations
+
+- Upload input files
+- Download generated outputs
+- List available files
+- Delete unnecessary files
+- Manage file sessions
+
+### Limitations
+- Code cannot access the network
+- Only 10 files can be generated per run
+- Execution limits vary by plan:
+ - **Hobby**:
+ - 256 MB RAM per execution
+ - 25 MB per file upload
+ - 750 requests per month
+ - **Enthusiast**:
+ - 512 MB RAM per execution
+ - 50 MB per file upload
+ - 3,000 requests per month
+ - **Pro**:
+ - 512 MB RAM per execution
+ - 150 MB per file upload
+ - 7,000 requests per month
+- The [Enterprise Plan](https://code.librechat.ai/pricing) provides custom limits and features
+
+## Use Cases
+
+- **Code Testing**: Test code snippets in multiple languages
+- **File Processing**: Transform and analyze files programmatically
+- **AI Applications**: Execute AI-generated code securely
+- **Development Tools**: Build interactive coding environments
+- **Objective Logic**: Verify code logic and correctness, improving AI models
+
+## Why a Paid API?
+
+While LibreChat remains free and open source under the MIT license, the Code Interpreter API is offered as a paid service for several key reasons:
+
+1. **Project Sustainability**: Subscribing to an API plan provides direct support to the project's development, even more effectively than [GitHub Sponsors](https://github.com/sponsors/danny-avila). Your subscription helps ensure LibreChat's continued growth and improvement.
+
+2. **Technical Considerations**: Including code execution capabilities in the core project would add significant complexity and hardware requirements that not all users need. The API service eliminates these concerns while maintaining a lightweight core application.
+
+3. **Managed Service Benefits**:
+ - No complex configuration
+ - Immediate availability
+ - Regular updates and maintenance
+ - Professional support
+ - Secure, sandboxed environment
+
+4. **Intellectual Property Protection**: The Code Interpreter's architecture represents significant innovation in secure, scalable sandbox technology. While similar solutions exist, they often lack the comprehensive security measures and scalability features that make this implementation unique. Keeping this component as a closed-source API helps protect these innovations and ensures the service maintains its high security and performance standards.
+
+Even if you only use code execution occasionally, subscribing helps support LibreChat's development while enhancing your experience with professional-grade features. It's a win-win that keeps the core project free while offering optional advanced capabilities for those who need them.
+
+---
+
+## Conclusion
+
+The Code Interpreter API provides a secure, convenient way to execute code and manage files without the hassle of setting up and maintaining execution environments. Whether you're using it through LibreChat's Agents or integrating it directly into your applications, it offers a robust solution for code execution needs.
+
+For detailed technical specifications and API reference, please visit our [API Documentation](https://code.librechat.ai/docs).
+
+#LibreChat #CodeExecution #API #Development
\ No newline at end of file
diff --git a/content/docs-archive/v0.8.2/features/fork.mdx b/content/docs-archive/v0.8.2/features/fork.mdx
new file mode 100644
index 000000000..dae7c6cbf
--- /dev/null
+++ b/content/docs-archive/v0.8.2/features/fork.mdx
@@ -0,0 +1,123 @@
+---
+title: Forking Messages and Conversations
+icon: GitFork
+description: A guide on how to use the "Fork Messages/Conversations" feature in our app to create new conversations from specific messages with desired behavior.
+---
+
+import Image from 'next/image'
+
+
+ 
+
+
+
+ 
+
+
+
+
+
+### Include related branches:
+This option forks the visible messages, along with related branches; in other words, the direct path to the target message, including branches along the path.
+
+
+ 
+
+
+
+ 
+
+
+
+
+### Include all to/from here (default):
+This option forks all messages leading up to the target message, including its neighbors; in other words, all message branches, whether or not they are visible or along the same path, are included.
+
+
+ 
+
+
+
+ 
+
+
+
+
+## Additional Options
+
+- **Start fork here:** If checked, forking will commence from this message to the latest message in the conversation, according to the behavior selected above.
+
+
+ 
+
+
+
+ 
+
+
+
+
+- **Remember:** Check to remember the options you select for future usage, making it quicker to fork conversations as preferred.
+
+
+ 
+
+
+
+ 
+
+
+
+
+- Alternatively you can control the default behavior in the settings menu:
+
+
+ 
+
+
+
+ 
+
+
+
diff --git a/content/docs-archive/v0.8.2/features/image_gen.mdx b/content/docs-archive/v0.8.2/features/image_gen.mdx
new file mode 100644
index 000000000..93bebb25c
--- /dev/null
+++ b/content/docs-archive/v0.8.2/features/image_gen.mdx
@@ -0,0 +1,377 @@
+---
+title: Image Generation & Editing
+icon: Image
+description: Comprehensive guide to LibreChat's built-in image generation and editing tools
+---
+
+## 🎨 Image Generation & Editing
+
+LibreChat comes with **built-in image tools** that you can add to an **[Agent](/v0.8.2/docs/features/agents).**
+
+Each has its own look, price-point, and setup step (usually just an API key or URL).
+
+| Tool | Best for | Needs |
+|------|----------|-------|
+| **OpenAI Image Tools** | Cutting-edge results (GPT-Image-1).
+ 
+
+
+
+ 
+
+Can also ***edit*** the images you upload. | OpenAI API | +| **Gemini Image Tools** | Google's latest image models with context-aware generation. | Gemini API or Vertex AI | +| **DALL·E (3 / 2)** | Legacy OpenAI Image models. | OpenAI API | +| **Stable Diffusion** | Local or self-hosted generation, endless community models. | Automatic1111 API | +| **Flux** | Fast cloud renders, optional fine-tunes. | Flux API | +| **MCP** | Bring-your-own-Image-Generators | MCP server with image output support | + +**Notes:** +- API keys can be omitted in favor of allowing the user to enter their own key from the UI. +- Image Outputs are directly sent to the LLM as part of the immediate chat context following generation. + - The LLM will only get vision context from images attached to user messages, and not from generations/edits, except for immediately after generation. + - See [Image Storage and Handling](#image-storage-and-handling) for more details. +- MCP Server tool image outputs are supported, which may output images similarly to LC's built-in tools. + - Note: MCP servers may or may not use the correct format when outputting images. See details in the [MCP section below](#5--model-context-protocol-mcp). + +--- + +## 1 · OpenAI Image Tools (recommended) + +### Features + +"OpenAI Image Tools" are an agent toolkit made up of 2 separate tools. + +- **Image Generation**: + - **Create** brand-new images from text prompts (no upload required). +- **Image Editing**: + - **Edit** or **remix** the images you just uploaded—change colours, add objects, extend the canvas, etc. +- Both use OpenAI's latest image generation model, **GPT-Image-1**, for superior instruction following, text rendering, detailed editing, real-world knowledge +- See OpenAI's [Image Generation documentation](https://platform.openai.com/docs/guides/image-generation?image-generation-model=gpt-image-1) for more details. + +#### Generation vs. Editing +| Use-case | Invokes | +|----------|---------------| +| "Start from scratch" | **Image Generation** | +| "Use existing image(s)" | **Image Editing** | + +The agent decides which tool to use based on the context: + +- **Image Generation** creates brand new images from text descriptions only +- **Image Editing** modifies or remixes existing images using their image IDs + - These can be images from the current message or previously generated/referenced images + - The LLM keeps track of image IDs as long as they remain in the context window + - Includes the referenced image IDs in the tool output +- Both tools are always available, but the LLM will choose the appropriate one based on the user's request +- Both tools will include the generated image ID in the tool output + +⚠️ **Important** +- Image editing relies on image IDs, which are retained in the chat history. +- When files are uploaded to the current request, their image IDs are added to the context of the LLM before any tokens are generated. +- Previously referenced or generated image IDs can be used for editing, as long as they remain within the context window. +- The LLM can include any relevant image IDs in the `image_ids` array when calling the image editing tool. +- You can also attach previously uploaded images from the side panel without needing to upload them again. + - This also has the added benefit of providing a vision model with the image context, which can be useful for informing the `prompt` for the image editing tool. + +### Parameters + +#### Image Generation +• **prompt** – text description (required) +• **size** – `auto` (default), `1024x1024` (square), `1536x1024` (landscape), or `1024x1536` (portrait) +• **quality** – `auto` (default), `high`, `medium`, or `low` +• **background** – `auto` (default), `transparent`, or `opaque` (transparent requires PNG or WebP format) + +#### Image Editing + +• **image_ids** – array of image IDs to use as reference for editing (required) +• **prompt** – text description of the changes (required) +• **size** – `auto` (default), `1024x1024`, `1536x1024`, `1024x1536`, `256x256`, or `512x512` +• **quality** – `auto` (default), `high`, `medium`, or `low` + +### Setup +Create or reuse an OpenAI key and add to `.env`: + +```bash +IMAGE_GEN_OAI_API_KEY=sk-... +# optional extras +IMAGE_GEN_OAI_BASEURL=https://... +``` + +For Azure OpenAI deployments, you will first need access: https://aka.ms/oai/gptimage1access + +Then, add your corresponding credentials to your `.env` file: + +```bash +IMAGE_GEN_OAI_API_KEY=your-api-key +# optional extras +IMAGE_GEN_OAI_BASEURL=https://deploymentname.openai.azure.com/openai/deployments/gpt-image-1/ +IMAGE_GEN_OAI_AZURE_API_VERSION=2025-04-01-preview +``` + +Then add "OpenAI Image Tools" to your Agent's *Tools* list. + +### Advanced Configuration + +You can customize the tool descriptions and prompt guidance by setting these environment variables: + +```bash +# Image Generation Tool Descriptions +IMAGE_GEN_OAI_DESCRIPTION=... +IMAGE_GEN_OAI_PROMPT_DESCRIPTION=... + +# Image Editing Tool Descriptions +IMAGE_EDIT_OAI_DESCRIPTION=... +IMAGE_EDIT_OAI_PROMPT_DESCRIPTION=... +``` + +### Pricing +See the [GPT-Image-1 pricing page](https://platform.openai.com/docs/models/gpt-image-1) and [Image Generation Documentation](https://platform.openai.com/docs/guides/image-generation?image-generation-model=gpt-image-1#cost-and-latency) for details on costs associated with image generation. + +--- + +## 2 · Gemini Image Tools + +Gemini Image Tools integrate Google's latest image generation models, supporting both text-to-image generation and image context-aware editing. + +### Features + +- **Text-to-Image Generation**: Create high-quality images from detailed text descriptions +- **Image Context Support**: Use existing images as context or inspiration for new generations +- **Image Editing**: Generate new images based on modifications to existing ones (include original image ID) +- **Multiple Models**: Choose between `gemini-2.5-flash-image` (default) or `gemini-3-pro-image-preview` +- **Dual API Support**: Works with both simple Gemini API keys and Google Cloud Vertex AI + +### Parameters + +• **prompt** – Detailed text description of the desired image (required, up to 32,000 characters) +• **image_ids** – Optional array of image IDs to use as visual context for generation + +### Setup + +#### Option 1: Gemini API (Recommended) + +Get an API key from [Google AI Studio](https://aistudio.google.com/app/apikey): + +```bash +GEMINI_API_KEY=your_api_key_here +``` + +#### Option 2: Vertex AI (Enterprise) + +For Google Cloud users with Vertex AI access: + +```bash +GOOGLE_SERVICE_KEY_FILE=/path/to/service-account.json +GOOGLE_CLOUD_LOCATION=us-central1 # optional, default: global +``` + +### Model Selection + +```bash +# Default model (fast and efficient) +GEMINI_IMAGE_MODEL=gemini-2.5-flash-image + +# Higher quality model +GEMINI_IMAGE_MODEL=gemini-3-pro-image-preview +``` + +### Advanced Configuration + +Customize tool descriptions via environment variables: + +```bash +GEMINI_IMAGE_GEN_DESCRIPTION=... +GEMINI_IMAGE_GEN_PROMPT_DESCRIPTION=... +GEMINI_IMAGE_IDS_DESCRIPTION=... +``` + +More details can be found in the dedicated [Gemini Image Gen guide](/v0.8.2/docs/configuration/tools/gemini_image_gen). + +--- + +## 3 · DALL·E (legacy) + +DALL·E provides high-quality image generation using OpenAI's legacy image models. + +### Parameters +• **prompt** – Text description of the desired image (required, up to 4000 characters) +• **style** – `vivid` (hyper-real, dramatic - default) or `natural` (less hyper-real) +• **quality** – `standard` (default) or `hd` +• **size** – `1024x1024` (default/square), `1792x1024` (wide), or `1024x1792` (tall) + +### Setup + +```bash +# Required +DALLE_API_KEY=sk-... # or DALLE3_API_KEY=sk-... + +# Optional +DALLE_REVERSE_PROXY=https://... # Alternative endpoint +DALLE3_BASEURL=https://... # For Azure or custom endpoints +DALLE3_AZURE_API_VERSION=2023-12-01-preview # For Azure deployments +DALLE3_SYSTEM_PROMPT=... # Custom system prompt for DALL·E +``` + +### Advanced Configuration +For Azure OpenAI deployments, configure both the base URL and API version: + +```bash +DALLE3_BASEURL=https://your-resource-name.openai.azure.com/openai/deployments/your-deployment-name +DALLE3_AZURE_API_VERSION=2023-12-01-preview +DALLE3_API_KEY=your-azure-api-key +``` + +Enable the **DALL·E** tool for the Agent and start prompting. + +### Pricing +See the [DALL-E pricing page](https://platform.openai.com/docs/models/dall-e-3) and [Image Generation Documentation](https://platform.openai.com/docs/guides/image-generation?image-generation-model=dall-e-3) for details on costs associated with image generation. + +--- + +## 4 · Stable Diffusion (local) + +Run images entirely on your own machine or server. +Point LibreChat at any Automatic1111 (or compatible) endpoint and you're set. + +### Parameters +• **prompt** – Detailed keywords describing desired elements in the image (required) +• **negative_prompt** – Keywords describing elements to exclude from the image (required) + +The Stable Diffusion implementation uses these default parameters: +- cfg_scale: 4.5 +- steps: 22 +- width: 1024 +- height: 1024 + +These values are currently fixed but provide good results for most use cases. + +### Setup + +```bash +SD_WEBUI_URL=http://127.0.0.1:7860 # URL to your Automatic1111 WebUI +``` + +No API key required—just the reachable URL. + +More details on setting up Automatic1111 can be found in the dedicated [Stable Diffusion guide](/v0.8.2/docs/configuration/tools/stable_diffusion). + +--- + +## 5 · Flux + +Cloud generator with an emphasis on speed and optional fine-tuned models. + +### Features +- Fast cloud-based image generation +- Support for fine-tuned models +- Multiple quality levels and aspect ratios +- Raw mode for less processed, more natural-looking images + +### Parameters +The Flux tool supports three main actions: + +1. **generate** - Create a new image from a text prompt +2. **generate_finetuned** - Create an image using a fine-tuned model +3. **list_finetunes** - List available custom models for the user + +More details can be found in the dedicated [Flux guide](/v0.8.2/docs/configuration/tools/flux#parameters). + +### Setup + +```bash +FLUX_API_KEY=flux_live_... +FLUX_API_BASE_URL=https://api.us1.bfl.ai # default is fine for most users +``` + +Choose the **Flux** tool inside the Agent. Prompts are plain text; one call produces one image. + +### Pricing +See the [Flux pricing page](https://docs.bfl.ml/pricing/) for details on costs associated with image generation. + +--- + +## 6 · Model Context Protocol (MCP) + +Image outputs are supported from MCP servers. + +For example, the [Puppeteer MCP Server](https://github.com/modelcontextprotocol/servers/tree/main/src/puppeteer) can be used to generate screenshots of web pages, which correctly output the image in the expected format and is treated the same as LC's built-in image tools. + +> The examples below assume LibreChat is running outside of Docker, directly using Node.js. The Model Context Protocol is a relatively new framework, and many developers are still learning how to properly serve their systems with uv/node for scalable distribution. + +> As this technology is still emerging, there are currently few image-generating servers available, and many existing ones have yet to adopt the correct response format for images. + +> While many MCP servers do function well within Docker, the following examples do not, or not without more advanced configurations, showcasing some of the current inconsistency between MCP servers. + +```yaml +mcpServers: + puppeteer: + command: npx + args: + - -y + - "@modelcontextprotocol/server-puppeteer" +``` + +The following is an example of an [Image Generation server](https://github.com/GongRzhe/Image-Generation-MCP-Server) that outputs images using [Replicate API](https://replicate.com/account/api-tokens), but returns URLs of the images, which doesn't conform to MCP's image response standard. + +> Note: for this particular server, you need to install the `@gongrzhe/image-gen-server` package globally using npm, i.e. `npm install -g @gongrzhe/image-gen-server`, then point to the package's compiled files as shown below. + +```yaml +mcpServers: + image-gen: + command: "node" + # First, install the package globally using npm: + # `npm install -g @gongrzhe/image-gen-server` + # Then, point to the location of the installed package, + # which you can find by running `npm root -g` + args: + - "{REPLACE_WITH_NODE_MODULES_LOCATION}/@gongrzhe/image-gen-server/build/index.js" + # Example with output from `npm root -g`: + # - "/home/danny/.nvm/versions/node/v20.19.0/lib/node_modules/@gongrzhe/image-gen-server/build/index.js" + env: + # Do not hardcode the API token here, use the environment variable instead + # The following will pick up the token from your .env file or environment + REPLICATE_API_TOKEN: "${REPLICATE_API_TOKEN}" + MODEL: "google/imagen-3" +``` + +--- + +## Image Storage and Handling + +All generated images are: +1. Saved according to the configured [**`fileStrategy`**](/v0.8.2/docs/configuration/librechat_yaml/object_structure/config#filestrategy) +2. Displayed directly in the chat interface +3. Image tool outputs are directly sent to the LLM as part of the immediate chat context following generation. + - This may create issues if you are using an LLM that does not support image inputs. + - There will be an option to disable this behavior on a per-agent-basis in the future. + - These outputs are only directly sent to the LLM upon generation, not on every message. + - To include the image in the chat, you can directly attach it to the message from the side panel. + - To summarize, the LLM will only get vision context from images attached to user messages, and not from generations/edits, except for immediately after generation. + +--- + +## Proxy Support + +All image generation tools support proxy configuration through the `PROXY` environment variable: + +```bash +PROXY=http://proxy-url:port +``` + +## Error Handling +If any of the tools encounter an error, they will return an error message explaining what went wrong. Common issues include: +- Invalid API key +- API unavailability +- Content policy violations +- Proxy/network issues +- Invalid parameters +- Unsupported image payload (see [Image Storage and Handling](#image-storage-and-handling) above) + +--- + +## Prompting + +Though you can customize the prompts for [OpenAI Image Tools](#advanced-configuration) and [DALL·E](#advanced-configuration-1), the following tips inform the default prompts supplied by the tools, which is helpful to know for your own writing/prompting. + +1. Start with the **subject** and **style** (photo, oil painting, etc.). +2. Add **composition** and **camera / medium** ("wide-angle shot of…", "watercolour…"). +3. Mention **lighting & mood** ("golden hour", "dramatic shadows"). +4. Finish with **detail keywords** (textures, colours, expressions). +5. Keep negatives positive—describe what should be included, not what to avoid. + +Example: + +> A cinematic photo of an antique library bathed in warm afternoon sunlight. Tall wooden shelves overflow with leather-bound books, and dust particles shimmer in the light. A single green-shaded banker's lamp illuminates an open atlas on a polished mahogany desk in the foreground. 85 mm lens, shallow depth of field, rich amber tones, ultra-high detail. diff --git a/content/docs-archive/v0.8.2/features/import_convos.mdx b/content/docs-archive/v0.8.2/features/import_convos.mdx new file mode 100644 index 000000000..4a855f2f0 --- /dev/null +++ b/content/docs-archive/v0.8.2/features/import_convos.mdx @@ -0,0 +1,31 @@ +--- +title: Import Conversations +icon: Import +description: Conversations Import allows user to import conversations exported from other GPT chat applications. Currently, we support importing conversations from ChatGPT, ChatbotUI v1, and LibreChat itself. +--- + +Conversations Import allows user to import conversations exported from other GPT chat applications. Currently, we support importing conversations from [ChatGPT](https://chatgpt.com/), [ChatbotUI v1](https://github.com/mckaywrigley/chatbot-ui/tree/b865b0555f53957e96727bc0bbb369c9eaecd83b?tab=readme-ov-file#legacy-code), and LibreChat itself. + +The Import functionality is available in the "Settings" -> "Data Controls" section. + +## How to import conversations from Chat GPT + +1. Follow the [ChatGPT export instructions](https://help.openai.com/en/articles/7260999-how-do-i-export-my-chatgpt-history-and-data) to export your conversations. +2. You should get a link to download archive in you email. +3. Download the archive. It should be a zip file with random name like: _d119d98bb3711aff7a2c73bcc7ea53d96c984650d8f7e033faef78386a9907-2024-01-01-10-30-00.zip_ +4. Extract the content of the zip file. +5. Navigate to LibreChat Settings -> Data Controls +
+
+6. Click on the "Import" button and select `conversations.json` file from the extracted archive. It will start importing the conversations.
+7. Shortly you will get a notification that the import is complete.
+
+ 
+
+
+
+ 
+
+
+ 
+
diff --git a/content/docs-archive/v0.8.2/features/index.mdx b/content/docs-archive/v0.8.2/features/index.mdx
new file mode 100644
index 000000000..57c3f4b25
--- /dev/null
+++ b/content/docs-archive/v0.8.2/features/index.mdx
@@ -0,0 +1,7 @@
+---
+title: Overview
+icon: BookOpen
+description: Explore the features of LibreChat, including agents, MCP integration, code execution, multimodal chat, and more.
+---
+
+
+ 
+
+
+## Overview
+
+This feature enables email-based password reset functionality for your LibreChat server. You can configure it to work with various email services, including Mailgun API, Gmail, and custom mail servers.
+
+## Key Features
+
+- Supports multiple email services:
+ - **Mailgun API** - Recommended for servers that block SMTP ports
+ - **Gmail** and other predefined SMTP services
+ - **Custom mail servers** with advanced SMTP configuration
+- Allows for basic and advanced configuration options
+- Enables secure email-based password reset functionality for your LibreChat server
+
+## Setup Options
+
+- **Mailgun Configuration**: Use Mailgun's API for reliable email delivery, especially useful when SMTP ports are blocked
+- **Basic SMTP Configuration**: Use predefined services like Gmail with minimal configuration
+- **Advanced SMTP Configuration**: Configure generic SMTP services or customize settings for any mail provider
+
+**For detailed setup instructions, refer to the configuration guide: [Email Setup](/v0.8.2/docs/configuration/authentication/email)**
diff --git a/content/docs-archive/v0.8.2/features/rag_api.mdx b/content/docs-archive/v0.8.2/features/rag_api.mdx
new file mode 100644
index 000000000..70645cd62
--- /dev/null
+++ b/content/docs-archive/v0.8.2/features/rag_api.mdx
@@ -0,0 +1,70 @@
+---
+title: RAG API (Chat with Files)
+icon: Brain
+description: Retrieval-Augmented Generation (RAG) API for document indexing and retrieval using Langchain and FastAPI. This API integrates with LibreChat to provide context-aware responses based on user-uploaded files.
+---
+
+The **RAG (Retrieval-Augmented Generation) API** is a powerful tool that integrates with LibreChat to provide context-aware responses based on user-uploaded files.
+
+It leverages LangChain, PostgresQL + PGVector, and Python FastAPI to index and retrieve relevant documents, enhancing the conversational experience.
+
+**For further details, refer to the configuration guide provided here: [RAG API Configuration](/v0.8.2/docs/configuration/rag_api)**
+
+
+
+---
+
+**Currently, this feature is available through [Agents](/v0.8.2/docs/features/agents), as well as through Custom Endpoints, OpenAI, Azure OpenAI, Anthropic, and Google.**
+
+OpenAI Assistants have their own implementation of RAG through the "Retrieval" capability. Learn more about it [here.](https://platform.openai.com/docs/assistants/tools/knowledge-retrieval)
+
+It will still be useful to implement usage of the RAG API with the Assistants API since OpenAI charges for both file storage, and use of "Retrieval," and will be introduced in a future update.
+
+**Still confused about RAG?** [Read the section I wrote below](#what-is-rag) explaining the general concept in more detail with a link to a helpful video.
+
+## What is RAG?
+
+RAG, or Retrieval-Augmented Generation, is an AI framework designed to improve the quality and accuracy of responses generated by large language models (LLMs). It achieves this by grounding the LLM on external sources of knowledge, supplementing the model's internal representation of information.
+
+
+## Features
+
+- **Document Indexing**: The RAG API indexes user-uploaded files, creating embeddings for efficient retrieval.
+- **Semantic Search**: It performs semantic search over the indexed documents to find the most relevant information based on the user's input.
+- **Context-Aware Responses**: By augmenting the user's prompt with retrieved information, the API enables LibreChat to generate more accurate and contextually relevant responses.
+- **Asynchronous Processing**: The API supports asynchronous operations for improved performance and scalability.
+- **Flexible Configuration**: It allows customization of various parameters such as chunk size, overlap, and embedding models.
+
+### Key Benefits of RAG
+
+1. **Access to up-to-date and reliable facts**: RAG ensures that the LLM has access to the most current and reliable information by retrieving relevant facts from an external knowledge base.
+2. **Transparency and trust**: Users can access the model's sources, allowing them to verify the accuracy of the generated responses and build trust in the system.
+3. **Reduced data leakage and hallucinations**: By grounding the LLM on a set of external, verifiable facts, RAG reduces the chances of the model leaking sensitive data or generating incorrect or misleading information.
+4. **Lower computational and financial costs**: RAG reduces the need for continuous training and updating of the model's parameters, potentially lowering the computational and financial costs of running LLM-powered chatbots in an enterprise setting.
+
+### How RAG Works
+
+RAG consists of two main phases: retrieval and content generation.
+
+1. **Retrieval Phase**: Algorithms search for and retrieve snippets of information relevant to the user's prompt or question from an external knowledge base. In an open-domain, consumer setting, these facts can come from indexed documents on the internet. In a closed-domain, enterprise setting, a narrower set of sources are typically used for added security and reliability.
+2. **Generative Phase**: The retrieved external knowledge is appended to the user's prompt and passed to the LLM. The LLM then draws from the augmented prompt and its internal representation of its training data to synthesize a tailored, engaging answer for the user. The answer can be passed to a chatbot with links to its sources.
+
+### Challenges and Ongoing Research
+
+While RAG is currently one of the best-known tools for grounding LLMs on the latest, verifiable information and lowering the costs of constant retraining and updating, it's not perfect. Some challenges include:
+
+1. **Recognizing unanswerable questions**: LLMs need to be explicitly trained to recognize questions they can't answer based on the available information. This may require fine-tuning on thousands of examples of answerable and unanswerable questions.
+2. **Improving retrieval and generation**: Ongoing research focuses on innovating at both ends of the RAG process: improving the retrieval of the most relevant information possible to feed the LLM, and optimizing the structure of that information to obtain the richest responses from the LLM.
+
+In summary, RAG is a powerful framework that enhances the capabilities of LLMs by grounding them on external, verifiable knowledge. It helps to ensure more accurate, up-to-date, and trustworthy responses while reducing the costs associated with continuous model retraining. As research in this area progresses, we can expect further improvements in the quality and efficiency of LLM-powered conversational AI systems.
+
+For a more detailed explanation of RAG, you can watch this informative video by IBM on Youtube:
+
+
+
+
+## Conclusion
+
+The RAG API is a powerful addition to LibreChat, enabling context-aware responses based on user-uploaded files. By leveraging Langchain and FastAPI, it provides efficient document indexing, retrieval, and generation capabilities. With its flexible configuration options and seamless integration, the RAG API enhances the conversational experience in LibreChat.
+
+For more detailed information on the RAG API, including API endpoints, request/response formats, and advanced configuration, please refer to the official RAG API documentation.
diff --git a/content/docs-archive/v0.8.2/features/resumable_streams.mdx b/content/docs-archive/v0.8.2/features/resumable_streams.mdx
new file mode 100644
index 000000000..0c4484eb6
--- /dev/null
+++ b/content/docs-archive/v0.8.2/features/resumable_streams.mdx
@@ -0,0 +1,176 @@
+---
+title: Resumable Streams
+icon: Zap
+description: Never lose an AI response—seamless reconnection, multi-tab sync, and horizontal scaling for production deployments
+---
+
+LibreChat features a resilient streaming architecture that ensures you never lose AI-generated content. Whether your connection drops, you switch tabs, or you pick up on another device, your responses are always preserved and synchronized.
+
+## Why It Matters
+
+Traditional chat applications lose all streaming content when your connection drops. With resumable streams, LibreChat:
+
+- **Preserves every response** — Network hiccups, browser refreshes, or server restarts won't cause data loss
+- **Keeps multiple tabs in sync** — Open the same conversation in two browser tabs and watch them update together in real-time
+- **Enables seamless device switching** — Start a conversation on your desktop and continue on your phone
+- **Lets you multitask freely** — Start a generation, browse other tabs, and come back to a complete response
+
+## How It Works
+
+When you send a message to an AI model, LibreChat creates a generation job that tracks all streamed content. The magic happens when something interrupts your connection:
+
+1. **Automatic detection** — The client detects the disconnection instantly
+2. **State reconstruction** — Upon reconnecting, the server rebuilds all previously streamed content
+3. **Seamless sync** — Missing content is delivered via a sync event
+4. **Transparent continuation** — Streaming resumes from the current position
+
+This all happens automatically—no user action required.
+
+### Multi-Tab & Multi-Device Experience
+
+One of the most powerful aspects of resumable streams is **real-time synchronization**:
+
+- **Same chat, multiple windows** — Open a conversation in two browser tabs and both receive updates simultaneously
+- **Cross-device continuity** — Start a long generation on your laptop, then check the result on your phone
+- **Team collaboration** — In shared conversations, all viewers see content appear in real-time
+
+## Deployment Modes
+
+LibreChat supports two deployment configurations:
+
+### Single-Instance Mode (Default)
+
+Uses in-memory storage with Node.js `EventEmitter` for pub/sub. Perfect for:
+- Local development
+- Single-server deployments
+- Docker Compose setups
+
+**No configuration required** — Works out of the box.
+
+### Redis Mode (Production)
+
+Uses Redis Streams and Pub/Sub for cross-instance communication. Essential for:
+- Horizontally scaled deployments
+- Load-balanced production environments
+- High-availability setups
+- Kubernetes clusters
+
+With Redis mode, a user can start a generation on one server instance and seamlessly resume on another—perfect for rolling deployments and auto-scaling.
+
+**Note:** If you only run a single LibreChat instance, Redis for resumable streams is typically unnecessary—the in-memory mode handles everything. Redis becomes valuable when you have multiple LibreChat instances behind a load balancer. That said, Redis is still useful for other features like caching and session storage even in single-instance deployments.
+
+## Configuration
+
+### Enabling Redis Streams
+
+When Redis is enabled (`USE_REDIS=true`), resumable streams automatically use Redis. You can also explicitly enable it:
+
+```bash filename=".env"
+USE_REDIS=true
+REDIS_URI=redis://localhost:6379
+# Resumable streams will use Redis automatically when USE_REDIS=true
+# To explicitly control it:
+USE_REDIS_STREAMS=true
+```
+
+### Redis Cluster Support
+
+For Redis Cluster deployments:
+
+```bash filename=".env"
+USE_REDIS_STREAMS=true
+USE_REDIS_CLUSTER=true
+REDIS_URI=redis://node1:7001,redis://node2:7002,redis://node3:7003
+```
+
+LibreChat automatically uses hash-tagged keys to ensure multi-key operations stay within the same cluster slot.
+
+## Use Cases
+
+### Unstable Networks
+On spotty WiFi or cellular connections, responses automatically resume when connectivity returns. No need to re-send your prompt.
+
+### Mobile Users
+Switch from WiFi to cellular (or vice versa) without losing your response. The stream picks up exactly where it left off.
+
+### Long-Running Generations
+For complex prompts that generate lengthy responses, feel free to check other tabs or apps. Your response will be waiting when you return.
+
+### Multi-Device Workflows
+Start a conversation on your work computer, commute home, and check the result on your phone—the full response is there.
+
+### Production Deployments
+Scale horizontally across multiple server instances while maintaining stream continuity. Rolling deployments won't interrupt active generations.
+
+## Technical Details
+
+### Content Reconstruction
+
+The system aggregates all streamed delta events to rebuild:
+- Message content (text, tool calls, citations)
+- Agent run steps and intermediate reasoning
+- Metadata and state information
+
+### Performance Optimizations
+
+**Memory-first approach**: When reconnecting to the same server instance, LibreChat uses local cache for zero-latency content recovery, avoiding unnecessary Redis round trips.
+
+**Automatic cleanup**: Stale job entries are removed during queries to prevent memory leaks. Completed streams expire automatically.
+
+**Efficient storage**: In-memory mode uses `WeakRef` for graph storage, enabling automatic garbage collection when conversations end.
+
+### Data Flow
+
+| Component | Storage Mechanism |
+|-----------|-------------------|
+| Chunks | Redis Streams (`XADD`/`XRANGE`) |
+| Job metadata | Redis Hash structures |
+| Real-time events | Redis Pub/Sub channels |
+| Expiration | Automatic TTL after stream completion |
+
+## Testing Resumable Streams
+
+You can verify the feature is working:
+
+1. Start a streaming conversation with any AI model
+2. **Tab test**: Open the same chat in a new browser tab—both should sync
+3. **Disconnect test**: Turn off your network briefly, then reconnect
+4. **Navigation test**: Navigate away mid-stream, then return
+
+In all cases, you should see the complete response with no data loss.
+
+## Troubleshooting
+
+### Streams not resuming?
+
+**Check Redis connectivity:**
+```bash
+docker exec -it librechat-redis redis-cli ping
+# Should return: PONG
+```
+
+**Verify environment variables:**
+```bash
+# Ensure USE_REDIS_STREAMS is set
+echo $USE_REDIS_STREAMS
+```
+
+### Content appears duplicated?
+
+This typically indicates a client version mismatch. Ensure you're running the latest version of LibreChat.
+
+### High memory usage in single-instance mode?
+
+Completed streams are automatically garbage collected. If you're seeing high memory usage, check for:
+- Very long-running streams that haven't completed
+- Streams that errored without proper cleanup
+
+## Related Documentation
+
+- [Redis Configuration](/v0.8.2/docs/configuration/redis) — Setting up Redis for caching and horizontal scaling
+- [Agents](/v0.8.2/docs/features/agents) — AI agents with tool use capabilities
+- [Docker Deployment](/v0.8.2/docs/local/docker) — Container-based deployment guide
+
+---
+
+For implementation details, see [PR #10926](https://github.com/danny-avila/LibreChat/pull/10926).
diff --git a/content/docs-archive/v0.8.2/features/search.mdx b/content/docs-archive/v0.8.2/features/search.mdx
new file mode 100644
index 000000000..7dea1a8a2
--- /dev/null
+++ b/content/docs-archive/v0.8.2/features/search.mdx
@@ -0,0 +1,19 @@
+---
+title: Search
+icon: ListFilter
+description: Quickly search in past conversations with LibreChat's integrated Meilisearch
+---
+
+LibreChat has integrated **Meilisearch** to enhance the user experience by providing a fast and efficient way to search through past conversations. Meilisearch is a powerful, open-source search engine that is known for its speed and ease of use, making it an excellent choice for applications like LibreChat that require quick access to a large volume of data.
+
+
+ 
+
+
+
+The integration allows users to:
+- Perform **full-text searches** on their conversation history.
+- Utilize **typo-tolerance** for more forgiving search queries.
+- Experience **instant results** as they type, thanks to Meilisearch's as-you-type search capabilities.
+
+This feature significantly improves the functionality of LibreChat, making it easier for users to find specific messages or topics within their chat history. It's a testament to the platform's commitment to providing a seamless and user-friendly experience. For those interested in the technical details or implementation, further information can be found in the [Meilisearch Configuration Guide](/v0.8.2/docs/configuration/meilisearch).
diff --git a/content/docs-archive/v0.8.2/features/shareable_links.mdx b/content/docs-archive/v0.8.2/features/shareable_links.mdx
new file mode 100644
index 000000000..4f8f8b924
--- /dev/null
+++ b/content/docs-archive/v0.8.2/features/shareable_links.mdx
@@ -0,0 +1,168 @@
+---
+title: Shareable Links
+icon: Share2
+description: Share your conversations with others using LibreChat's shareable links feature, complete with QR codes, branching messages, and artifacts support.
+---
+
+import Image from 'next/image'
+
+## Overview
+
+Shareable Links in LibreChat allow you to share your conversations with others through automatically generated links and QR codes. Whether you're collaborating with teammates, showcasing AI interactions, or sharing generated artifacts, this feature makes it easy to allow others to view your conversations with the click of a button.
+
+## Key Features
+
+- **Easy Sharing**: Generate shareable links with just a few clicks
+- **QR Code Generation**: Quickly share conversations via QR codes for mobile access
+- **Conversation Branching**: Recipients can see branched conversations in your shared links
+- **Artifacts Support**: Shared conversations now include generated artifacts and interactive components
+- **Customizable Appearance**: Recipients can adjust language and theme preferences
+- **Link Management**: Centralized dashboard to manage all your shared links
+
+## How to Share a Conversation
+There are two ways to make a conversation shareable:
+
+### Option 1: From the Conversation Menu
+
+
+*Access the share option from the conversation menu*
+
+### Option 2: From the Share Button
+
+
+*Use the dedicated share button in your active conversation*
+
+## Share Link Options
+
+When you create a shareable link, you'll see a modal with several options to customize how your conversation appears to recipients.
+
+
+
+
+### Available Options:
+
+- **Refresh Link**: Generate a new URL for the shared conversation
+- **Generate QR code**: Create and show a QR code for easy mobile access
+- **Copy Link to clipboard**: Copy the shareable URL to your clipboard
+- **Delete Link**: Remove the shared link, revoking access to anyone who has it
+
+## QR Code Feature
+
+Generate QR codes for your shared conversations for easy mobile sharing. Simply scan the code with any smartphone camera to instantly access the conversation.
+
+
+ 
+ *Initial share link creation modal*
+
+
+ 
+ *Shared link configuration modal*
+
+
+
+
+This is particularly useful for:
+- Sharing during presentations
+- Quick mobile access
+- Offline sharing via printed materials
+- Conference or event demonstrations
+
+## Viewing Shared Conversations
+
+When someone opens your shared link, they'll see a clean, focused view of the conversation with all the context you chose to include.
+
+
+*How recipients see your shared conversation*
+
+### Features Available to Recipients:
+
+- The date the shareable link was published
+- Ability to scroll through the entire conversation
+- Access to any included artifacts or generated content
+
+## Branching in Shared Conversations
+
+Conversation branches are preserved in shared links, allowing recipients to explore different conversation paths and see how the discussion evolved.
+
+
+ 
+ *Generate QR codes for instant mobile access to shared conversations*
+
+
+ 
+ *QR code will link to the shared conversation URL*
+
+
+
+
+This feature is essential for:
+- Demonstrating different AI approaches to the same problem
+- Illustrating how solutions and interactions can take multiple different paths depending on user input
+
+## Artifacts in Shared Conversations
+
+All artifacts generated during the conversation are fully functional in shared links, including React components, HTML code, and Mermaid diagrams.
+
+
+*Generated artifacts remain interactive in shared conversations*
+
+Recipients can:
+- View interactive React components
+- See HTML previews
+- Examine Mermaid diagrams
+- Access the underlying code
+- Understand the context in which artifacts were generated
+
+## Customization Options for Recipients
+
+Recipients can customize their viewing experience by adjusting language and theme preferences to match their preferences.
+
+
+*Recipients can customize language and theme preferences*
+
+Available customizations:
+- **Theme selection**: Light, dark, or system preference
+- **Language**: View the interface in their preferred language
+
+## Managing Your Shared Links
+
+Access the Shared Links Management dashboard under the Data Controls section of the Settings menu to view and manage all your shared conversations in one place.
+
+
+ 
+ *Access different conversation branches using the branch navigation arrows*
+
+
+ 
+ *Recipients can navigate through conversation branches in shared links*
+
+
+
+
+### Management Features:
+
+- **View all links**: See a list of all conversations you've shared
+- **Search & filter**: Quickly find and view the content of specific shared links
+- **Revoke access**: Delete links to immediately stop sharing
+
+## Frequently Asked Questions
+
+**Q: Can recipients respond to shared conversations?**
+A: No, shared links are read-only. Recipients can view the conversation but cannot add messages or interact with the AI.
+
+**Q: What happens if I delete a conversation after sharing it?**
+A: The shared link will no longer be accessible, and any user which navigates to that link will be served a page stating "Shared link not found".
+
+**Q: Can I edit a conversation after sharing it?**
+A: The shared link captures the conversation at the time of creation. Additional messages will not be reflected in the shared view - however, edits made to the existing messages will be shown.
+
+**Q: Do shared links work offline?**
+A: No, recipients need an internet connection to view shared conversations.
\ No newline at end of file
diff --git a/content/docs-archive/v0.8.2/features/temporary_chat.mdx b/content/docs-archive/v0.8.2/features/temporary_chat.mdx
new file mode 100644
index 000000000..aea135218
--- /dev/null
+++ b/content/docs-archive/v0.8.2/features/temporary_chat.mdx
@@ -0,0 +1,26 @@
+---
+title: Temporary Chat
+icon: Clock
+description: Temporary chats allow users to exclude specific conversations from their chat history, search results, and bookmarks, providing a private and focused experience.
+---
+
+Keep your chat history clean and focused by using temporary chats for sensitive topics, quick experiments, or anything you don't need to permanently save. These chats are excluded from search results, cannot be bookmarked, and are automatically deleted after 30 days.
+
+## Activating Temporary Chat
+
+1. Open the model list dropdown menu located on the top left side of LibreChat.
+2. Toggle the "Temporary Chat" slider to the ON position.
+
+
+
+3. A notification will appear above the chat input area, confirming that Temporary Chat mode is active. Pressing (x) will disable the Temporary Chat.
+
+
+
+
+## What Happens When a Chat is Marked as Temporary?
+
+* Temporary Chats do not appear in the chat history sidebar.
+* Temporary Chats are excluded from search results.
+* Temporary Chats cannot be bookmarked.
+* Temporary Chats are stored in the database for 30 days and then automatically deleted.
diff --git a/content/docs-archive/v0.8.2/features/upload_as_text.mdx b/content/docs-archive/v0.8.2/features/upload_as_text.mdx
new file mode 100644
index 000000000..ee3e3a3aa
--- /dev/null
+++ b/content/docs-archive/v0.8.2/features/upload_as_text.mdx
@@ -0,0 +1,321 @@
+---
+title: Upload as Text
+icon: Upload
+description: Upload files to include their full content in conversations without requiring OCR configuration.
+---
+
+Upload as Text allows you to upload documents and have their full content included directly in your conversation with the AI. This feature works out-of-the-box using text parsing methods, with optional OCR enhancement for improved extraction quality.
+
+## Overview
+
+- **No OCR required** - Uses text parsing with fallback methods by default
+- **Enhanced by OCR** - If OCR is configured, extraction quality improves for images and scanned documents
+- **Full document content** - Entire file content available to the model in the conversation
+- **Works with all models** - No special tool capabilities needed
+- **Token limit control** - Configurable via `fileTokenLimit` to manage context usage
+
+## The `context` Capability
+
+Upload as Text is controlled by the `context` capability in your LibreChat configuration.
+
+```yaml
+# librechat.yaml
+endpoints:
+ agents:
+ capabilities:
+ - "context" # Enables "Upload as Text"
+```
+
+**Default:** The `context` capability is included by default. You only need to explicitly add it if you've customized the capabilities list.
+
+## How It Works
+
+When you upload a file using "Upload as Text":
+
+1. LibreChat checks the file MIME type against `fileConfig` patterns
+2. **Processing method determined by precedence: OCR > STT > text parsing**
+3. If file matches `fileConfig.ocr.supportedMimeTypes` AND OCR is configured: **Use OCR**
+4. If file matches `fileConfig.stt.supportedMimeTypes` AND STT is configured: **Use STT**
+5. If file matches `fileConfig.text.supportedMimeTypes`: **Use text parsing**
+6. Otherwise: **Fallback to text parsing**
+7. Text is truncated to `fileConfig.fileTokenLimit` before prompt construction
+8. Full extracted text included in conversation context
+
+### Text Processing Methods
+
+**Text Parsing (Default):**
+- Uses a robust parsing library (same as the RAG API)
+- Handles PDFs, Word docs, text files, code files, and more
+- No external service required
+- Works immediately without configuration
+- Fallback method if no other match
+
+**OCR Enhancement (Optional):**
+- Improves extraction from images, scanned documents, and complex PDFs
+- Requires OCR service configuration
+- Automatically used for files matching `fileConfig.ocr.supportedMimeTypes` when available
+- See [OCR Configuration](/v0.8.2/docs/features/ocr)
+
+**STT Processing (Optional):**
+- Converts audio files to text
+- Requires STT service configuration
+- See [Speech-to-Text Configuration](/v0.8.2/docs/configuration/librechat_yaml/object_structure/file_config#stt)
+
+## Usage
+
+1. Click the attachment icon in the chat input
+2. Select "Upload as Text" from the menu
+3. Choose your file
+4. File content is extracted and included in your message
+
+**Note:** If you don't see "Upload as Text", ensure the `context` capability is enabled in your [`endpoints.agents.capabilities` configuration](/v0.8.2/docs/configuration/librechat_yaml/object_structure/agents#capabilities).
+
+## Configuration
+
+### Basic Configuration
+
+The `context` capability is enabled by default. No additional configuration is required for basic text parsing functionality.
+
+### File Handling Configuration
+
+Control text processing behavior with `fileConfig`:
+
+```yaml
+fileConfig:
+ # Maximum tokens from text files before truncation
+ fileTokenLimit: 100000
+
+ # Files matching these patterns use OCR (if configured)
+ ocr:
+ supportedMimeTypes:
+ - "^image/(jpeg|gif|png|webp|heic|heif)$"
+ - "^application/pdf$"
+ - "^application/vnd\\.openxmlformats-officedocument\\.(wordprocessingml\\.document|presentationml\\.presentation|spreadsheetml\\.sheet)$"
+ - "^application/vnd\\.ms-(word|powerpoint|excel)$"
+ - "^application/epub\\+zip$"
+
+ # Files matching these patterns use text parsing
+ text:
+ supportedMimeTypes:
+ - "^text/(plain|markdown|csv|json|xml|html|css|javascript|typescript|x-python|x-java|x-csharp|x-php|x-ruby|x-go|x-rust|x-kotlin|x-swift|x-scala|x-perl|x-lua|x-shell|x-sql|x-yaml|x-toml)$"
+
+ # Files matching these patterns use STT (if configured)
+ stt:
+ supportedMimeTypes:
+ - "^audio/(mp3|mpeg|mpeg3|wav|wave|x-wav|ogg|vorbis|mp4|x-m4a|flac|x-flac|webm)$"
+```
+
+**Processing Priority:** OCR > STT > text parsing > fallback
+
+For more details, see [File Config Object Structure](/v0.8.2/docs/configuration/librechat_yaml/object_structure/file_config).
+
+### Optional: Configure OCR for Enhanced Extraction
+
+OCR is **not required** but enhances extraction quality when configured:
+
+```yaml
+# librechat.yaml
+ocr:
+ strategy: "mistral_ocr"
+ apiKey: "${OCR_API_KEY}"
+ baseURL: "https://api.mistral.ai/v1"
+ mistralModel: "mistral-ocr-latest"
+```
+
+See [OCR Configuration](/v0.8.2/docs/features/ocr) for full details.
+
+## When to Use Each Upload Option
+
+LibreChat offers three different ways to upload files, each suited for different use cases:
+
+### Use "Upload as Text" when:
+- ✅ You want the AI to read the complete document content
+- ✅ Working with smaller files that fit in context
+- ✅ You need "chat with files" functionality
+- ✅ Using models without tool capabilities
+- ✅ You want direct content access without semantic search
+
+### Use "Upload for File Search" when:
+- ✅ Working with large documents or multiple files
+- ✅ You want to optimize token usage
+- ✅ You need semantic search for relevant sections
+- ✅ Building knowledge bases
+- ✅ The `file_search` capability is enabled and toggled ON
+
+### Use standard "Upload Files" when:
+- ✅ Using vision models to analyze images
+- ✅ Using code interpreter to execute code
+- ✅ Files don't need text extraction
+
+## Supported File Types
+
+### Text Files (text parsing)
+- Plain text, Markdown, CSV, JSON, XML, HTML
+- Programming languages (Python, JavaScript, Java, C++, etc.)
+- Configuration files (YAML, TOML, INI, etc.)
+- Shell scripts, SQL files
+
+### Documents (text parsing or OCR)
+- PDF documents
+- Word documents (.docx, .doc)
+- PowerPoint presentations (.pptx, .ppt)
+- Excel spreadsheets (.xlsx, .xls)
+- EPUB books
+
+### Images (OCR if configured)
+- JPEG, PNG, GIF, WebP
+- HEIC, HEIF (Apple formats)
+- Screenshots, photos of documents, scanned images
+
+### Audio (STT if configured)
+- MP3, WAV, OGG, FLAC
+- M4A, WebM
+- Voice recordings, podcasts
+
+## File Processing Priority
+
+LibreChat processes files based on MIME type matching with the following **priority order**:
+
+1. **OCR** - If file matches `ocr.supportedMimeTypes` AND OCR is configured
+2. **STT** - If file matches `stt.supportedMimeTypes` AND STT is configured
+3. **Text Parsing** - If file matches `text.supportedMimeTypes`
+4. **Fallback** - Text parsing as last resort
+
+### Processing Examples
+
+**PDF file with OCR configured:**
+- Matches `ocr.supportedMimeTypes`
+- **Uses OCR** to extract text
+- Better quality for scanned PDFs
+
+**PDF file without OCR configured:**
+- Matches `text.supportedMimeTypes` (fallback)
+- **Uses text parsing** library
+- Works well for digital PDFs
+
+**Python file:**
+- Matches `text.supportedMimeTypes`
+- **Uses text parsing** (no OCR needed)
+- Direct text extraction
+
+**Audio file with STT configured:**
+- Matches `stt.supportedMimeTypes`
+- **Uses STT** to transcribe
+
+## Token Limits
+
+Files are truncated to `fileTokenLimit` tokens to manage context window usage:
+
+```yaml
+fileConfig:
+ fileTokenLimit: 100000 # Default: 100,000 tokens
+```
+
+- Truncation happens at runtime before prompt construction
+- Helps prevent exceeding model context limits
+- Configurable based on your needs and model capabilities
+- Larger limits allow more content but use more tokens
+
+## Comparison with Other File Features
+
+| Feature | Capability | Requires Service | Persistence | Best For |
+|---------|-----------|------------------|-------------|----------|
+| **Upload as Text** | `context` | No (enhanced by OCR) | Single conversation | Temporary document questions |
+| **Agent File Context** | `context` | No (enhanced by OCR) | Agent system instructions | Specialized agent knowledge |
+| **File Search** | `file_search` | Yes (vector DB) | Stored in vector store | Large documents, semantic search |
+
+### Upload as Text vs Agent File Context
+
+**Upload as Text (`context`):**
+- Available in any chat conversation
+- Content included in current conversation only
+- No OCR service required (text parsing by default)
+- Best for one-off document questions
+
+**Agent File Context (`context`):**
+- Only available in Agent Builder
+- Content stored in agent's system instructions
+- No OCR service required (text parsing by default)
+- Best for creating specialized agents with persistent knowledge
+- See [OCR for Documents](/v0.8.2/docs/features/ocr)
+
+### Upload as Text vs File Search
+
+**Upload as Text (`context`):**
+- Full document content in conversation context
+- Direct access to all text
+- Token usage: entire file (up to limit)
+- Works without RAG API configuration
+
+**File Search (`file_search`):**
+- Semantic search over documents
+- Returns relevant chunks via tool use
+- Token usage: only relevant sections
+- Requires RAG API and vector store configuration
+- See [RAG API](/v0.8.2/docs/features/rag_api)
+
+## Example Use Cases
+
+- **Document Analysis**: Upload contracts, reports, or articles for analysis
+- **Code Review**: Upload source files for review and suggestions
+- **Data Extraction**: Extract information from structured documents
+- **Translation**: Translate document contents
+- **Summarization**: Summarize articles, papers, or reports
+- **Research**: Discuss academic papers or technical documentation
+- **Troubleshooting**: Share log files for analysis
+- **Content Editing**: Review and edit written content
+- **Data Processing**: Work with CSV or JSON data files
+
+## Troubleshooting
+
+### "Upload as Text" option not appearing
+
+**Solution:** Ensure the `context` capability is enabled:
+
+```yaml
+endpoints:
+ agents:
+ capabilities:
+ - "context" # Add this if missing
+```
+
+### File content not extracted properly
+
+**Solutions:**
+1. Check if file type is supported (matches `fileConfig` patterns)
+2. For images/scanned documents: Configure OCR for better extraction
+3. For audio files: Configure STT service
+4. Verify file is not corrupted
+
+### Content seems truncated
+
+**Solution:** Increase the token limit:
+
+```yaml
+fileConfig:
+ fileTokenLimit: 150000 # Increase as needed
+```
+
+### Poor extraction quality from images
+
+**Solution:** Configure OCR to enhance extraction:
+
+```yaml
+ocr:
+ strategy: "mistral_ocr"
+ apiKey: "${OCR_API_KEY}"
+```
+
+See [OCR Configuration](/v0.8.2/docs/configuration/librechat_yaml/object_structure/ocr) for details.
+
+## Related Features
+
+- [File Context](/v0.8.2/docs/features/agents#file-context) - Files used as Agent Context
+- [OCR for Documents](/v0.8.2/docs/features/ocr) - Learn about and configure OCR services
+- [File Configuration](/v0.8.2/docs/configuration/librechat_yaml/object_structure/file_config) - Configure file handling
+
+---
+
+Upload as Text provides a simple, powerful way to work with documents in LibreChat without requiring complex configuration or external services.
+
+
diff --git a/content/docs-archive/v0.8.2/features/url_query.mdx b/content/docs-archive/v0.8.2/features/url_query.mdx
new file mode 100644
index 000000000..06c17f20a
--- /dev/null
+++ b/content/docs-archive/v0.8.2/features/url_query.mdx
@@ -0,0 +1,253 @@
+---
+title: Query Parameters
+icon: Link
+description: Learn how to configure chat conversations using URL query parameters in LibreChat. Set models, endpoints, and conversation settings dynamically.
+---
+
+LibreChat supports dynamic configuration of chat conversations through URL query parameters. This feature allows you to initiate conversations with specific settings, models, and endpoints directly from the URL.
+
+### Chat Paths
+
+Query parameters must follow a valid chat path:
+- For new conversations: `/c/new?`
+- For existing conversations: `/c/[conversation-id]?` (where conversation-id is an existing one)
+
+Examples:
+
+```bash
+https://your-domain.com/c/new?endpoint=ollama&model=llama3%3Alatest
+https://your-domain.com/c/03debefd-6a50-438a-904d-1a806f82aad4?endpoint=openAI&model=o1-mini
+```
+
+## Basic Usage
+
+The most common parameters to use are `endpoint` and `model`. Using both is recommended for the most predictable behavior:
+
+```bash
+https://your-domain.com/c/new?endpoint=azureOpenAI&model=o1-mini
+```
+
+### URL Encoding
+
+Special characters in query params must be properly URL-encoded to work correctly. Common characters that need encoding:
+
+- `:` → `%3A`
+- `/` → `%2F`
+- `?` → `%3F`
+- `#` → `%23`
+- `&` → `%26`
+- `=` → `%3D`
+- `+` → `%2B`
+- Space → `%20` (or `+`)
+
+Example with special characters:
+```ts
+Original: `Write a function: def hello()`
+Encoded: `/c/new?prompt=Write%20a%20function%3A%20def%20hello()`
+```
+
+You can use JavaScript's built-in `encodeURIComponent()` function to properly encode prompts:
+```javascript
+const prompt = "Write a function: def hello()";
+const encodedPrompt = encodeURIComponent(prompt);
+const url = `/c/new?prompt=${encodedPrompt}`;
+console.log(url);
+```
+
+Try running the code in your browser console to see the encoded URL (browser shortcut: `Ctrl+Shift+I`).
+
+### Endpoint Selection
+
+The `endpoint` parameter can be used alone:
+```bash
+https://your-domain.com/c/new?endpoint=google
+```
+
+When only `endpoint` is specified:
+- It will use the last selected model from localStorage
+- If no previous model exists, it will use the first available model in the endpoint's model list
+
+#### Notes
+
+- The `endpoint` value must be one of the following:
+```bash
+openAI, azureOpenAI, google, anthropic, assistants, azureAssistants, bedrock, agents
+```
+- If using a [custom endpoint](/v0.8.2/docs/quick_start/custom_endpoints), you can use its name as the value (case-insensitive)
+
+```bash
+# using `endpoint=perplexity` for a custom endpoint named `Perplexity`
+https://your-domain.com/c/new?endpoint=perplexity&model=llama-3.1-sonar-small-128k-online
+```
+
+### Model Selection
+
+The `model` parameter can be used alone:
+```bash
+https://your-domain.com/c/new?model=gpt-4o
+```
+
+When only `model` is specified:
+- It will only select the model if it's available in the current endpoint
+- The current endpoint is either the default endpoint or the last selected endpoint
+
+### Prompt Parameter
+
+The `prompt` parameter allows you to pre-populate the chat input field:
+```bash
+https://your-domain.com/c/new?prompt=Explain quantum computing
+```
+
+You can also use `q` as a shorthand, which is interchangeable with `prompt`:
+```bash
+https://your-domain.com/c/new?q=Explain quantum computing
+```
+
+You can combine these with other parameters:
+```bash
+https://your-domain.com/c/new?endpoint=anthropic&model=claude-3-5-sonnet-20241022&prompt=Explain quantum computing
+```
+
+### Automatic Prompt Submission
+
+The `submit` parameter allows you to automatically submit the prompt without manual intervention:
+```bash
+https://your-domain.com/c/new?prompt=Explain quantum computing&submit=true
+```
+
+This feature is particularly useful for:
+- Creating automated workflows (e.g., Raycast, Alfred, Automater)
+- Building external integrations
+
+You can combine it with other parameters for complete automation:
+```bash
+https://your-domain.com/c/new?endpoint=openAI&model=gpt-4&prompt=Explain quantum computing&submit=true
+```
+
+### Special Endpoints
+
+#### Model Specs
+You can select a specific model spec by name:
+```bash
+https://your-domain.com/c/new?spec=meeting-notes-gpt4
+```
+This will load all the settings defined in the model spec. When using the `spec` parameter, other model parameters in the URL will be ignored.
+
+#### Agents
+You can directly load an agent using its ID without specifying the endpoint:
+```bash
+https://your-domain.com/c/new?agent_id=your-agent-id
+```
+This will automatically set the endpoint to `agents`.
+
+#### Assistants
+Similarly, you can load an assistant directly:
+```bash
+https://your-domain.com/c/new?assistant_id=your-assistant-id
+```
+This will automatically set the endpoint to `assistants`.
+
+## Supported Parameters
+
+LibreChat supports a wide range of parameters for fine-tuning your conversation settings:
+
+### LibreChat Settings
+- `maxContextTokens`: Override the system-defined context window
+- `resendFiles`: Control file resubmission in subsequent messages
+- `promptPrefix`: Set custom instructions/system message
+- `imageDetail`: 'low', 'auto', or 'high' for image quality
+ - Note: while this is a LibreChat-specific parameter, it only affects the following endpoints:
+ - OpenAI, Custom Endpoints, which are OpenAI-like, and Azure OpenAI, for which this defaults to 'auto'
+- `spec`: Select a specific LibreChat [Model Spec](/v0.8.2/docs/configuration/librechat_yaml/object_structure/model_specs) by name
+ - Must match the exact name of a configured model spec
+ - When specified, other model parameters will not take effect, only those defined by the model spec
+ - **Important:** If model specs are configured with `enforce: true`, using this parameter may be required for URL query params to work properly
+- `fileTokenLimit`: Set maximum token limit for file processing to control costs and resource usage.
+ - Note: Request value overrides YAML default.
+
+### Model Parameters
+Different endpoints support various parameters:
+
+**OpenAI, Custom, Azure OpenAI:**
+```bash
+# Note: these should be valid values according to the provider's API
+temperature, presence_penalty, frequency_penalty, stop, top_p, max_tokens,
+reasoning_effort, reasoning_summary, verbosity, useResponsesApi, web_search, disableStreaming
+```
+
+**Google, Anthropic:**
+```bash
+# Note: these should be valid values according to the provider's API
+topP, topK, maxOutputTokens, thinking, thinkingBudget, web_search
+```
+
+**Anthropic, Bedrock (Anthropic models):**
+
+Set this to `true` or `false` to toggle the "prompt-caching":
+```bash
+promptCache
+```
+
+More info: https://www.anthropic.com/news/prompt-caching, https://docs.aws.amazon.com/bedrock/latest/userguide/prompt-caching.html#prompt-caching-get-started
+
+**Bedrock:**
+```bash
+# Bedrock region
+region=us-west-2
+# Bedrock equivalent of `max_tokens`
+maxTokens=200
+```
+
+**Assistants/Azure Assistants:**
+```bash
+# overrides existing assistant instructions for current run
+instructions=your+instructions
+```
+```bash
+# Adds the current date and time to `additional_instructions` for each run.
+append_current_datetime=true
+```
+
+## More Info
+
+For more information on any of the above, refer to [Model Spec Preset Fields](/v0.8.2/docs/configuration/librechat_yaml/object_structure/model_specs), which shares most parameters.
+
+**Example with multiple parameters:**
+```bash
+https://your-domain.com/c/new?endpoint=google&model=gemini-2.0-flash-exp&temperature=0.7&prompt=Oh hi mark
+```
+
+**Example with model spec:**
+```bash
+https://your-domain.com/c/new?spec=meeting-notes-gpt4&prompt=Here%20is%20the%20transcript...
+```
+Note: When using `spec`, other model parameters are ignored in favor of the model spec's configuration.
+
+## ⚠️ Warning
+
+Exercise caution when using query parameters:
+- Misuse or exceeding provider limits may result in API errors
+- If you encounter bad request errors, reset the conversation by clicking "New Chat"
+- Some parameters may have no effect if they're not supported by the selected endpoint
+
+## Best Practices
+
+1. Always use both `endpoint` and `model` when possible
+2. Verify parameter support for your chosen endpoint
+3. Use reasonable values within provider limits
+4. Test your parameter combinations before sharing URLs
+
+## Parameter Validation
+
+All parameters are validated against LibreChat's schema before being applied. Invalid parameters or values will be ignored, and valid settings will be applied to the conversation.
+
+---
+
+This feature enables powerful use cases like:
+- Sharing specific conversation configurations
+- Creating bookmarks for different chat settings
+- Automating chat setup through URL parameters
+
+---
+
+#LibreChat #ChatConfiguration #AIParameters #OpenSource #URLQueryParameters
diff --git a/content/docs-archive/v0.8.2/features/web_search.mdx b/content/docs-archive/v0.8.2/features/web_search.mdx
new file mode 100644
index 000000000..ee3c865af
--- /dev/null
+++ b/content/docs-archive/v0.8.2/features/web_search.mdx
@@ -0,0 +1,206 @@
+---
+title: "Web Search"
+icon: Search
+---
+
+LibreChat's web search feature allows you to search the internet and retrieve relevant information to enhance your conversations. The feature consists of three main components that work together to provide comprehensive search results.
+
+## Quick Start
+
+To get started with web search, you'll need to configure API keys for all three components to ensure effective search results. You can do this in two ways:
+
+1. **Environment Variables** (Recommended for admins):
+ ```bash
+ # Search Provider (Required)
+ SERPER_API_KEY=your_serper_api_key
+ # or
+ SEARXNG_INSTANCE_URL=your_searxng_instance_url
+ SEARXNG_API_KEY=your_searxng_api_key # Optional
+
+ # Scraper (Required)
+ FIRECRAWL_API_KEY=your_firecrawl_api_key
+ # Optional: Custom Firecrawl API URL
+ FIRECRAWL_API_URL=your_firecrawl_api_url
+ # Optional: Firecrawl API version (v0 or v1)
+ # FIRECRAWL_VERSION=v1
+
+ # Reranker (Required)
+ JINA_API_KEY=your_jina_api_key
+ # Optional: Custom Jina API URL
+ JINA_API_URL=your_jina_api_url
+ # or
+ COHERE_API_KEY=your_cohere_api_key
+ ```
+
+2. **User Interface** (If environment variables are not set):
+ - Users will be prompted to enter the required API keys when they first use the web search feature
+ - They can choose which search provider (Serper or SearXNG) and which reranker service to use (Jina or Cohere)
+
+## Obtaining API Keys
+
+Each component of the web search feature requires its own API key. Here's how to obtain them:
+
+### Search Providers
+
+#### Serper
+1. Visit [Serper.dev](https://serper.dev)
+2. Sign up for an account
+3. Navigate to the API Key section
+4. Copy your API key
+5. Set it in your environment variables or provide it through the UI
+
+#### SearXNG
+1. Follow the setup instructions in the [Web Search Configuration](/v0.8.2/docs/configuration/librechat_yaml/object_structure/web_search#setting-up-searxng) documentation
+2. Set `SEARXNG_INSTANCE_URL` to your instance URL
+3. Optionally set `SEARXNG_API_KEY` if your instance requires authentication
+
+### Scraper: Firecrawl
+
+1. Visit [Firecrawl.dev](https://docs.firecrawl.dev/introduction#api-key)
+2. Sign up for an account
+3. Navigate to the API Key section
+4. Copy your API key
+5. Set it in your environment variables or provide it through the UI
+6. (Optional) If you're using a custom Firecrawl instance, you'll also need to set the API URL
+
+### Rerankers
+
+#### Jina
+1. Visit [Jina.ai](https://jina.ai/api-dashboard/)
+2. Sign up for an account
+3. Navigate to the API Dashboard
+4. Copy your API key
+5. Set it in your environment variables or provide it through the UI
+
+#### Cohere
+1. Visit [Cohere Dashboard](https://dashboard.cohere.com/welcome/login)
+2. Sign up for an account
+3. Navigate to the API Keys section
+4. Copy your API key
+5. Set it in your environment variables or provide it through the UI
+
+## Components
+
+### 1. Search Providers
+
+Search providers are responsible for performing the initial web search and returning relevant results.
+
+**Available Providers:**
+- **Serper**: A Google Search API that provides high-quality search results
+ - Get your API key from [Serper.dev](https://serper.dev/api-key)
+- **SearXNG**: Open-source, self-hosted meta search engine
+ - Self-host your own instance
+ - Privacy-focused search results
+
+### 2. Scrapers
+
+Scrapers extract the actual content from web pages returned by the search provider.
+
+**Available Scrapers:**
+- **Firecrawl**: A powerful web scraping service that extracts content from web pages
+ - Get your API key from [Firecrawl.dev](https://docs.firecrawl.dev/introduction#api-key)
+ - API URL is optional (defaults to Firecrawl's hosted service)
+
+**Planned Scrapers:**
+- **Local Firecrawl**: Self-hosted version of Firecrawl
+- Additional third-party scraping services
+
+### 3. Rerankers
+
+Rerankers analyze the scraped content to determine the most relevant parts and reorder them for better results.
+
+**Available Rerankers:**
+- **Jina**: AI-powered reranking service
+ - Get your API key from [Jina.ai](https://jina.ai/api-dashboard/)
+ - API URL is optional (defaults to Jina's hosted service)
+- **Cohere**: Advanced reranking service
+ - Get your API key from [Cohere Dashboard](https://dashboard.cohere.com/welcome/login)
+
+**Planned Rerankers:**
+- **RAG API**: Open-source reranking using RAG (Retrieval-Augmented Generation)
+- Additional third-party reranking services
+
+## Configuration
+
+### Admin Configuration
+
+Admins can configure the web search feature using environment variables. The YAML configuration allows you to specify custom environment variable names for each component.
+
+⚠️ **Important: Never put actual API keys or values in the YAML file (they won't work)- only use environment variable names.**
+
+```yaml
+webSearch:
+ # Search Provider Configuration
+ serperApiKey: "${CUSTOM_SERPER_API_KEY}" # ✅ Correct: Using environment variable name
+ # serperApiKey: "sk-123..." # ❌ Wrong: Never put actual API keys here
+ # or
+ searxngInstanceUrl: "${CUSTOM_SEARXNG_INSTANCE_URL}" # ✅ Correct: Using environment variable name
+ searxngApiKey: "${CUSTOM_SEARXNG_API_KEY}" # ✅ Correct: Using environment variable name
+ # searxngInstanceUrl: "http://..." # ❌ Wrong: Never put actual URLs here
+ # searxngApiKey: "sk-123..." # ❌ Wrong: Never put actual API keys here
+
+ # Scraper Configuration
+ firecrawlApiKey: "${CUSTOM_FIRECRAWL_API_KEY}"
+ firecrawlApiUrl: "${CUSTOM_FIRECRAWL_API_URL}"
+ # firecrawlApiKey: "fc-123..." # ❌ Wrong: Never put actual API keys here
+ # firecrawlApiUrl: "https://..." # ❌ Wrong: Never put actual URLs here
+
+ # Reranker Configuration
+ jinaApiKey: "${CUSTOM_JINA_API_KEY}"
+ jinaApiUrl: "${CUSTOM_JINA_API_URL}"
+ cohereApiKey: "${CUSTOM_COHERE_API_KEY}"
+ # jinaApiKey: "jn-123..." # ❌ Wrong: Never put actual API keys here
+ # jinaApiUrl: "https://..." # ❌ Wrong: Never put actual URLs here
+ # cohereApiKey: "ch-123..." # ❌ Wrong: Never put actual API keys here
+
+ # General Settings
+ safeSearch: 1 # Options: 0 (OFF), 1 (MODERATE - default), 2 (STRICT)
+```
+
+**Note:** The YAML configuration should only contain environment variable names (in the format `${VARIABLE_NAME}`). This flexibility enables:
+- Using different variable names in different environments
+- Supporting multiple configurations for different user groups
+- Future integration with role-based configurations
+
+If you want to restrict the system to use only specific services, you can specify the service types:
+
+```yaml
+webSearch:
+ # ... variable configurations ...
+ searchProvider: "serper" # Only use Serper for search
+ # searchProvider: "searxng" # Only use SearXNG for search
+ scraperProvider: "firecrawl" # Only use Firecrawl for scraping
+ rerankerType: "jina" # Only use Jina for reranking
+```
+
+### User Configuration
+
+If the admin hasn't configured all the necessary API keys, users will be prompted to provide them through the UI. The interface allows users to:
+
+1. Choose their preferred reranker (Jina or Cohere)
+2. Enter API keys for the required services
+3. Configure the Firecrawl API URL if needed (optional)
+4. Configure the Jina API URL if needed (optional)
+
+## Usage
+
+Once configured, you can use web search in two ways:
+
+1. **Chat Interface**: Click the web search button in the chat interface to enable web search for your conversation
+2. **Agents**: Use the `web_search` capability in agents to allow them to search the web
+
+## Notes
+
+- All three components (search provider, scraper, and reranker) are required for effective search results
+- The Firecrawl API URL is optional and defaults to their hosted service
+- The Jina API URL is optional and defaults to their hosted service
+- Safe search provides three levels of content filtering: OFF (0), MODERATE (1 - default), and STRICT (2)
+- The scraper timeout is set to 7.5 seconds (7500ms) by default
+- API keys can be revoked at any time through the UI
+- Future updates will include more open-source, self-hosted options for all components
+- Additional customization options are planned, including:
+ - Control over the number of links to scrape
+ - Domain allowlist/blocklist for scraping
+ - Custom scraping rules and filters
+ - Advanced result filtering and ranking options
+ - Rate limiting and request throttling controls
diff --git a/content/docs-archive/v0.8.2/index.mdx b/content/docs-archive/v0.8.2/index.mdx
new file mode 100644
index 000000000..328c59fa0
--- /dev/null
+++ b/content/docs-archive/v0.8.2/index.mdx
@@ -0,0 +1,7 @@
+---
+title: Get Started
+icon: Rocket
+description: Everything you need to get up and running with LibreChat, the open-source AI chat platform.
+---
+
+
+ 
+ *Centralized dashboard for managing all your shared links*
+
+
+ 
+ *View details and manage individual shared links*
+
+
+ ./helm/librechat`
+
+
+Similar to other Helm charts, there exists a [values file](https://github.com/danny-avila/LibreChat/blob/main/helm/librechat/values.yaml) that outlines the default settings and indicates which configuration options can be modified.
+
+Create a `values.yaml` file populated with the values you want to modify from the default.
+
+Install the Helm chart: `helm install librechat oci://ghcr.io/danny-avila/librechat-chart/librechat --values Development version
+ +In the repo's root directory, run: + +`helm install
+
+ 
+
+
|
+| **Arabic (ar)** | 
|
+| **Tibetan (bo)** | 
|
+| **Bosnian (bs)** | 
|
+| **Catalan (ca)** | 
|
+| **Czech (cs)** | 
|
+| **Danish (da)** | 
|
+| **German (de)** | 
|
+| **Spanish (es)** | 
|
+| **Estonian (et)** | 
|
+| **Persian (fa)** | 
|
+| **Finnish (fi)** | 
|
+| **French (fr)** | 
|
+| **Hebrew (he)** | 
|
+| **Hungarian (hu)** | 
|
+| **Armenian (hy)** | 
|
+| **Indonesian (id)** | 
|
+| **Icelandic (is)** | 
|
+| **Italian (it)** | 
|
+| **Japanese (ja)** | 
|
+| **Georgian (ka)** | 
|
+| **Korean (ko)** | 
|
+| **Lithuanian (lt)** | 
|
+| **Latvian (lv)** | 
|
+| **Norwegian Bokmål (nb)** | 
|
+| **Norwegian Nynorsk (nn)** | 
|
+| **Dutch (nl)** | 
|
+| **Polish (pl)** | 
|
+| **Portuguese (pt-PT)** | 
|
+| **Brazilian Portuguese (pt-BR)** | 
|
+| **Russian (ru)** | 
|
+| **Slovak (sk)** | 
|
+| **Slovenian (sl)** | 
|
+| **Swedish (sv)** | 
|
+| **Thai (th)** | 
|
+| **Turkish (tr)** | 
|
+| **Uyghur (ug)** | 
|
+| **Ukrainian (uk)** | 
|
+| **Vietnamese (vi)** | 
|
+| **Chinese (Simplified) (zh-Hans)** | 
|
+| **Chinese (Traditional) (zh-Hant)** | 
|
+
+---
+
+
+## Getting Started
+
+Before you begin translating, please follow the steps below to set up your Locize account and start contributing.
+
+
+### Step 1: Create a Locize Account
+
+1. Visit the Registration Page
+
+ Choose your preferred language and click the corresponding link to register:
+
+ - **[English (en)](https://www.locize.app/register?invitation=tTHVYwI9TzWuOeJnKyWxSuuaDrSS5TsZqRh0BAHzebuuljz5OUXnlqbksio5WnXp)**
+ - **[Arabic (ar)](https://www.locize.app/register?invitation=Cn7hc6teYyY89nvQdosfXkubbj2MZi2XMzcxUP6fGglcPkAgd1AwS5Pfbr1Wu4lz)**
+ - **[Tibetan (bo)](https://www.locize.app/register?invitation=183Kk5eTUvr0oeKkZqsIrSG1iflQPk5WjZzH5tb1uwDS7MdS3nFo55frHm86lz78)**
+ - **[Bosnian (bs)](https://www.locize.app/register?invitation=JA2zNrFrvoEbrXQgoZAxRrEStscwrCCAhTP7t44NBxa7XAJbdhwpqntq3xQ6Wltw)**
+ - **[Catalan (ca)](https://www.locize.app/register?invitation=c7ZQ0OT9k6c5kWRXMspgRQZXoZk2vZYIZ3RTpDkVrtShlauJ55YpeMo9EOBsYXgS)**
+ - **[Czech (cs)](https://www.locize.app/register?invitation=ypNUvwJG9ynzZabWS4X1bD2b8qSmhbvyXsytm1sbkVmqN0A6inKhiny2FuNVcvC2)**
+ - **[Danish (da)](https://www.locize.app/register?invitation=xClNgP4A7SNcMdhkTsf6xm8wP24mNbSW3YhnOtDNd7nMHhAZPJsWV8UIyTR6lLxI)**
+ - **[German (de)](https://www.locize.app/register?invitation=rAXIyYNuO53txcygphdOClUR5YnNccd1MZ1Vs66p4ziOqHfM3MFiKnymdK6wLMpW)**
+ - **[Spanish (es)](https://www.locize.app/register?invitation=gkrRvUjxvFnRfUtynbaREj2zdbvd2FU95OFGcixGMOkcCxSwmrvOBclBZJWmERw6)**
+ - **[Estonian (et)](https://www.locize.app/register?invitation=q1ye9gNpYsVKvs2JS5CEjp4SBy6ovq2aUeIhAMsRoW2iVcdfxpc4GiOaHGDV85VZ)**
+ - **[Persian (fa)](https://www.locize.app/register?invitation=DfuKT56Y4KxlPOm6biYl9zbgMo3kBjWJA3Flbd7X5H4hJluUWTsFiQ3MQH07fH0d)**
+ - **[Finnish (fi)](https://www.locize.app/register?invitation=weERAttD7ax0Zfo5w9LyfWbaP50WPbS4Vk7BF1P6wM0fe5Q0xlrJACVjTAGbkv2c)**
+ - **[French (fr)](https://www.locize.app/register?invitation=wz5EbZiwE9Bxev4TTAyG09PKvnFSQoOaLomxVgEKOyaLhm9oCDdhDi4TkJp8rcq5)**
+ - **[Hebrew (he)](https://www.locize.app/register?invitation=3LSHQxUsHYumNhw5ZJNu6Re6x699i6RGnpdKzt2BrDeNFNObxjj2lKXfZFUhb1jP)**
+ - **[Hungarian (hu)](https://www.locize.app/register?invitation=3TaJ2SnDnYfTJQLalKK751cQ04AK5A2gRahC2poeZYXj8MymZ5T0rt4V688e0H7M)**
+ - **[Armenian (hy)](https://www.locize.app/register?invitation=jLAFuEOvlBR86IcF1dZFHobsYdINvFoi0dMxxrJHvXIyxnosWcDblcXn6FtOhcOo)**
+ - **[Indonesian (id)](https://www.locize.app/register?invitation=S94A2D6glr7w64Nf27XwmvzkcnTRAWhxFoxcl7ZRnmm1dMx23kfpZCx8ROlqb6X2)**
+ - **[Icelandic (is)](https://www.locize.app/register?invitation=zgnniaPHGcML0dX5TdZ7Cv9fVkWkVGbrShol4JZYaYQXyk7t2oNlITaImx5n3wZe)**
+ - **[Italian (it)](https://www.locize.app/register?invitation=LI6zvAH82797Gro6lc490d34zrw8vthQPdN01n9nfk2c1LW5VVpf4Db6WL5GFHir)**
+ - **[Japanese (ja)](https://www.locize.app/register?invitation=VVJLuv7WjjBs0wShxZheCIvwzk7XszVsHCAMZmCQ34SJYrwIeB1GW6u2vkYNJdzk)**
+ - **[Georgian (ka)](https://www.locize.app/register?invitation=WK5hB5nznxioaDGOXXPDmcULrNfFA3wkcvS2YiUbrU6b73gKOWix5Qg7uGjpPtkH)**
+ - **[Korean (ko)](https://www.locize.app/register?invitation=nbL4LZMwehlTvFKNmNGgTTJt9YsZuuyCMjF9yAc92bVIWEjAc9C1G0ujsEl76dYb)**
+ - **[Lithuanian (lt)](https://www.locize.app/register?invitation=mObXVLL1r0IpkldNhVvahfdBSxo1AtqytlBavTU9jAb2M5K1HdbEADfpXpJWkyQK)**
+ - **[Latvian (lv)](https://www.locize.app/register?invitation=ey55PwxruCkT1EJ95oluthUzDbXwYJL4pXEd2xQoEHLwleVWND4VRND13a7EsioC)**
+ - **[Norwegian Bokmål (nb)](https://www.locize.app/register?invitation=14FVJmxYhd7ZSzjmxkF1XEU0jO9HDG7lpRRiOwVNKi19Ad6hD58NWASD0bN8JgaK)**
+ - **[Norwegian Nynorsk (nn)](https://www.locize.app/register?invitation=0upNDr8hxNUkMCAu0Lzo1MQnM0i7VXbli9x2wvygCz0q8sAK2z1AwxkgUDOD4n9R)**
+ - **[Dutch (nl)](https://www.locize.app/register?invitation=BQoligTqND5E4jlGmXJZVzkLOpo4pTf9wUyN19zZbgNB38JHaciJ2FnIbsLOXPbe)**
+ - **[Polish (pl)](https://www.locize.app/register?invitation=ZPiib1OoPM3OHBUow79I8iQNiFk4SHO7HASO3rHdJpKSlJwA4oxsORR2w4yJaPig)**
+ - **[Portuguese (pt-PT)](https://www.locize.app/register?invitation=c11DbWJk7O5TNIKon9leIfIbqARz60URaGB0WFQPT2ym3wxUDR8DgIiOlXNIBz13)**
+ - **[Brazilian Portuguese (pt-BR)](https://www.locize.app/register?invitation=99JdsEgKuVR9XhQJWi91Jq0LkqigiSz4EOf4gVGSr5RwZPp6ad4JQZLHVwhumNvB)**
+ - **[Russian (ru)](https://www.locize.app/register?invitation=rz4C3pVFdfr5XPPNTsYJvjjnC7vHDVWVOfyUzCf33MxhccdYB7vM7jxcHLacGl14)**
+ - **[Slovak (sk)](https://www.locize.app/register?invitation=wQkVqwu4Xr2KzmCgsXmqI7nMjyBzT2EKNFS3P6rNe4Kii3DgQG1i5ozeQeVEBmNd)**
+ - **[Slovenian (sl)](https://www.locize.app/register?invitation=NyNTniuVwwvEkKoKoOvAT4nzbVuvxE5X4kVUhBE9KSb3sEwEARQtMTeBCqpuV9dk)**
+ - **[Swedish (sv)](https://www.locize.app/register?invitation=RYtYhip5O5ACNCth1cIZpByGnZC1b3JttimEe8mrz5NDyEjVAs1PVcMIQ1in4j7D)**
+ - **[Thai (th)](https://www.locize.app/register?invitation=3xMjJPqupRNO2BU7K3WMWhxFtoGNzL97hxKIGjE8Yoa4v7lJj8ZjTy5p5dmcfLjW)**
+ - **[Turkish (tr)](https://www.locize.app/register?invitation=x3Ov59Gdrk2b76gn5pSVCwuekDs817YOYElXJn9zCYClPG2XlBORQDRygZmdBH4B)**
+ - **[Uyghur (ug)](https://www.locize.app/register?invitation=TeQX9ECX0oqhtkyBswm8BeOqlSaA5dKZaptvaEpYlfBhGBSl8PGIYfdVvPvgQnQF)**
+ - **[Ukrainian (uk)](https://www.locize.app/register?invitation=4Z060E9kPjmOqO8BmRSvuIujLydZiRCc0lu90iwQSaCche1tSdFcGOrdlDgPZ2ec)**
+ - **[Vietnamese (vi)](https://www.locize.app/register?invitation=rhADX8GuhgQmYrmbHT13YVg2WqMLJpgPdh1OBuujn9GoNUVW6RPipYvC20aH1xcQ)**
+ - **[Chinese (Simplified) (zh-Hans)](https://www.locize.app/register?invitation=HXXM2h8SJsBLIPJol3usRct0aPPcr809xzfV4DQHolyEfeSjBwEjChd37vE3ZrRw)**
+ - **[Chinese (Traditional) (zh-Hant)](https://www.locize.app/register?invitation=9PWBDcMascIBGG6wwobkVT6cL7p7IncFZVqwIe0e7VZd14MJOAMQGk6IjlvgmA00)**
+
+
+2. **Fill in Your Details:**
+Enter your email, password, and any other required information, then click **Sign Up**.
+
+
+
+
+### Step 2: Explore the Locize Dashboard
+
+After signing up, you’ll be directed to the Locize dashboard, where you can see an overview of the translation project.
+
+- **Dashboard Overview:**
+This page displays the available languages and progress statistics for the project.
+
+
+
+
+### Step 3: Select Your Language
+
+1. **Open the Language Dropdown:**
+Click the dropdown menu that lists all supported languages.
+
+2. **Choose Your Preferred Language:**
+For example, if you want to translate into Dutch, scroll down and select **Dutch**.
+
+
+
+
+### Step 4: Navigate to the Translation Page
+
+After selecting your language, click on the translation progress indicator (for example, "35.61% translated"). This will take you to the page where you can contribute translations.
+
+
+
+
+### Step 5: Contribute Your Translation
+
+1. **Browse the Translation Strings:**
+The interface displays a list of translation keys along with their original texts.
+
+2. **Select a String to Translate:**
+Click on the string you wish to work on.
+
+3. **Enter Your Translation:**
+Type your translated text into the input field provided next to the original text.
+
+4. **Review Your Work:**
+Ensure that your translation is accurate and clear.
+
+
+
+
+### Step 6: Save and Submit Your Translation
+
+1. **Submit Your Translation:**
+Once you’re satisfied with your translation, click the **Save** button to submit it for review.
+
+2. **Pending Review:**
+Your submitted translation will be marked as pending and will be reviewed by project maintainers.
+
+
+
+
+### Step 7: Translation Approval
+
+After review, your translation will be approved and integrated into the project.
+
+- **Approved Translation:**
+Once approved, your contribution will be reflected in the Locize dashboard and the overall translation progress.
+
+
+
+---
+
+## Handling `{{0}}` and `{{1}}` in Translation Strings
+
+Sometimes translation strings need to include dynamic content. These dynamic parts, called **interpolations**, are represented by placeholders enclosed in double curly brackets (e.g., `{{0}}` or `{{1}}`). When translating such strings, it's important to maintain these placeholders in the correct positions.
+
+Below are two examples to help guide you:
+
+### Example 1: Single Interpolation
+
+Consider the translation key `com_assistants_completed_action`. The original English text is:
+
+```text
+Talked to {{0}}
+```
+
+For the German translation, ensure the placeholder remains intact and is placed appropriately:
+
+```text
+Mit {{0}} gesprochen
+```
+
+This image shows how a single interpolation is represented in a translation string:
+
+
+
+---
+
+### Example 2: Multiple Interpolations
+
+Now, look at the translation key `com_files_number_selected`, which includes two placeholders. The English version is:
+
+```text
+{{0}} of {{1}} item(s) selected
+```
+
+In the German translation, both placeholders must be preserved and positioned correctly:
+
+```text
+{{0}} von {{1}} Datei(en) ausgewählt
+```
+
+This image illustrates how multiple interpolations appear in translation strings:
+
+
+
+---
+
+
+## Adding a New Language
+
+If you don't see your language listed in our translation table, you can help us expand our language support:
+
+1. **Create a New Issue:**
+Open a new issue in our GitHub repository: [LibreChat Issues](https://github.com/danny-avila/LibreChat/issues).
+
+2. **Select the New Language Request Template:**
+Use the **New Language Request** template and provide:
+ - The full name of your language (e.g., Spanish, Mandarin).
+ - The [ISO 639-1](https://www.w3schools.com/tags/ref_language_codes.asp) code for your language (e.g., `es` for Spanish).
+
+3. **Collaborate with Maintainers:**
+Our maintainers will review your request and work with you to integrate the new language. Once approved, your language will appear in the translation progress table, and you can start contributing.
+
+---
+
+## Need Help?
+
+If you have any questions or need assistance, please feel free to:
+
+- **Open an Issue:**
+Submit an issue in our repository: [LibreChat Issues](https://github.com/danny-avila/LibreChat/issues).
+
+- **Join Our Discord Community:**
+Connect with fellow translators on our [Discord server](https://discord.librechat.ai).
+
+- **Contact a Maintainer:**
+Reach out directly to one of our project maintainers for additional support.
+
+Your contributions help make LibreChat accessible to users worldwide. Thank you for supporting our project, and happy translating!
+
+
+---
+
+We thank [Locize](https://locize.com) for their translation management tools that support multiple languages in LibreChat.
+
+
+
+
+
+
+
diff --git a/content/docs-archive/v0.8.2/user_guides/meta.json b/content/docs-archive/v0.8.2/user_guides/meta.json
new file mode 100644
index 000000000..2b90dd538
--- /dev/null
+++ b/content/docs-archive/v0.8.2/user_guides/meta.json
@@ -0,0 +1,10 @@
+{
+ "title": "User Guides",
+ "icon": "BookOpen",
+ "pages": [
+ "index",
+ "ai_overview",
+ "presets",
+ "mongodb"
+ ]
+}
diff --git a/content/docs-archive/v0.8.2/user_guides/mongodb.mdx b/content/docs-archive/v0.8.2/user_guides/mongodb.mdx
new file mode 100644
index 000000000..2d3d5e4f6
--- /dev/null
+++ b/content/docs-archive/v0.8.2/user_guides/mongodb.mdx
@@ -0,0 +1,42 @@
+---
+title: MongoDB
+icon: Database
+description: Why LibreChat Uses MongoDB
+---
+
+MongoDB, a popular NoSQL database, was chosen as the core database for LibreChat due to its flexibility, scalability, and ability to handle diverse data structures efficiently. Here are some key reasons why MongoDB is an excellent fit for LibreChat:
+
+
+
+
+
+
+
+ 
+
+
+## 1. Flexible Data Model
+MongoDB's document-based data model allows for storing and retrieving data in a flexible and dynamic manner. Unlike traditional relational databases, MongoDB doesn't require a fixed schema, making it easier to adapt to changing data requirements. This flexibility is essential for LibreChat, as it needs to store various types of data, such as conversation histories, user profiles, presets, API keys, and more, without being constrained by a rigid table structure.
+
+## 2. Efficient Storage of Conversation Histories
+One of the primary use cases for LibreChat is to store and retrieve conversation histories. MongoDB's ability to store nested data structures as JSON-like documents makes it an excellent choice for storing conversation histories, which can include complex data structures like messages, timestamps, and metadata.
+
+## 3. Secure Storage of Sensitive Data
+LibreChat handles sensitive data, such as API keys and encrypted user passwords. MongoDB's built-in support for data encryption at rest and in transit ensures that this sensitive information remains secure and protected from unauthorized access.
+
+## 4. Horizontal Scalability
+As LibreChat grows and attracts more users, its data storage requirements will increase. MongoDB's horizontal scalability allows for scaling out by adding more servers to a cluster, providing the ability to handle larger amounts of data and higher traffic loads without compromising performance.
+
+## 5. Cross-Device Accessibility
+LibreChat aims to provide a seamless experience across multiple devices, allowing users to access their data and conversation histories from different devices. MongoDB's replication and sharding capabilities ensure that data is consistently available and accessible, enabling users to pick up their conversations where they left off, regardless of the device they're using.
+
+## 6. Developer Productivity
+MongoDB's intuitive query language and rich ecosystem of tools and libraries contribute to faster development cycles and increased developer productivity. This aligns well with LibreChat's goal of being an open-source project, fostering collaboration and contributions from the developer community.
+
+By leveraging MongoDB's strengths, LibreChat can efficiently manage and store diverse data structures, ensure data security and availability, and provide a seamless cross-device experience for its users. MongoDB's flexibility, scalability, and developer-friendly features make it an ideal choice for powering the core functionalities of LibreChat.
+
+
+## Note
+
+
+
+
+
+
+## OAuth2
+
+- [Apple](/v0.8.3/docs/configuration/authentication/OAuth2-OIDC/apple)
+- [Discord](/v0.8.3/docs/configuration/authentication/OAuth2-OIDC/discord)
+- [Facebook](/v0.8.3/docs/configuration/authentication/OAuth2-OIDC/facebook)
+- [GitHub](/v0.8.3/docs/configuration/authentication/OAuth2-OIDC/github)
+- [Google](/v0.8.3/docs/configuration/authentication/OAuth2-OIDC/google)
+
+## OpenID Connect
+
+- [Auth0](/v0.8.3/docs/configuration/authentication/OAuth2-OIDC/auth0)
+- [AWS Cognito](/v0.8.3/docs/configuration/authentication/OAuth2-OIDC/aws)
+- [Azure Entra/AD](/v0.8.3/docs/configuration/authentication/OAuth2-OIDC/azure)
+- [Keycloak](/v0.8.3/docs/configuration/authentication/OAuth2-OIDC/keycloak)
+- [Re-use OpenID Tokens for Login Session](/v0.8.3/docs/configuration/authentication/OAuth2-OIDC/token-reuse)
+
+## Troubleshooting OpenID Connect
+
+If you encounter issues with OpenID Connect authentication:
+
+1. **Enable Header Debug Logging**: Set `DEBUG_OPENID_REQUESTS=true` in your environment variables to log request headers in addition to URLs (with sensitive data masked). Note: Request URLs are always logged at debug level
+2. **Check Redirect URIs**: Ensure your callback URL matches exactly between your provider and LibreChat configuration
+3. **Verify Scopes**: Make sure all required scopes are properly configured
+4. **Review Provider Logs**: Check your identity provider's logs for authentication errors
+5. **Validate Tokens**: Ensure your provider is issuing valid tokens with the expected claims
+6. **Ensure _nonce_ is generated**: Some identity providers generate `nonce` url parameter if it's missing in the request. Set `OPENID_GENERATE_NONCE=true` to force the openid-client to generate it.
+
diff --git a/content/docs-archive/v0.8.3/configuration/authentication/OAuth2-OIDC/keycloak.mdx b/content/docs-archive/v0.8.3/configuration/authentication/OAuth2-OIDC/keycloak.mdx
new file mode 100644
index 000000000..7f1289bc8
--- /dev/null
+++ b/content/docs-archive/v0.8.3/configuration/authentication/OAuth2-OIDC/keycloak.mdx
@@ -0,0 +1,70 @@
+---
+title: Keycloak
+icon: KeyRound
+description: Learn how to configure LibreChat to use Keycloak for user authentication.
+---
+
+1. **Access Keycloak Admin Console:**
+- Open the Keycloak Admin Console in your web browser. This is usually
+found at a URL like `http://localhost:8080/auth/admin/`.
+
+2. **Create a Realm (if necessary):**
+- If you don't already have a realm for your application, create one. Click on 'Add Realm' and give it a name.
+
+3. **Create a Client:**
+- Within your realm, click on 'Clients' and then 'Create'.
+- Enter a client ID and select 'openid-connect' as the Client Protocol.
+- Set 'Client Authentication' to 'On'.
+- In 'Valid Redirect URIs', enter `http://localhost:3080/oauth/openid/callback` or the appropriate URI for
+your application.
+
+
+
+
+
+
+
+
+4. **Configure Client:**
+- After creating the client, you will be redirected to its settings page.
+- Note the 'Client ID' and 'Secret' from the 'Credentials' tab – you'll need these for your application.
+
+
+
+
+5. **Add Roles (Optional):**
+If you want to restrict access to users with specific roles, you can define roles in Keycloak and assign them to users.
+- Go to the 'Roles' tab in your client or realm (depending on where you want to define the roles).
+- Create roles that match the value(s) you have in `OPENID_REQUIRED_ROLE`.
+
+
+
+6. **Assign Roles to Users (Optional):**
+- Go to 'Users', select a user, and go to the 'Role Mappings' tab.
+- Assign at least one of the roles specified in `OPENID_REQUIRED_ROLE` to the user.
+
+
+
+7. **Get path of roles list inside token (Optional):**
+- Decode your jwtToken from OpenID provider and determine path for roles list inside access token. For example, if you are
+ using Keycloak, the path is `realm_access.roles`.
+- Put this path in `OPENID_REQUIRED_ROLE_PARAMETER_PATH` variable in `.env` file.
+- By parameter `OPENID_REQUIRED_ROLE_TOKEN_KIND` you can specify which token kind you want to use.
+ Possible values are `access` and `id`.
+
+8. **Update Your Project's Configuration:**
+- Open the `.env` file in your project folder and add the following variables:
+ ```bash filename=".env"
+ OPENID_ISSUER=http://localhost:8080/realms/[YourRealmName]
+ OPENID_CLIENT_ID=[YourClientID]
+ OPENID_CLIENT_SECRET=[YourClientSecret]
+ OPENID_SESSION_SECRET=[JustGenerateARandomSessionSecret]
+ OPENID_CALLBACK_URL=/oauth/openid/callback
+ OPENID_SCOPE="openid profile email"
+ OPENID_REQUIRED_ROLE=[YourRequiredRole] # Single role or comma-separated roles (e.g., role1,role2,admin)
+ OPENID_REQUIRED_ROLE_TOKEN_KIND=(access|id) # that means, `access` or `id`
+ OPENID_REQUIRED_ROLE_PARAMETER_PATH="realm_access.roles"
+
+ # Optional: redirects the user to the end session endpoint after logging out
+ OPENID_USE_END_SESSION_ENDPOINT=true
+ ```
diff --git a/content/docs-archive/v0.8.3/configuration/authentication/OAuth2-OIDC/meta.json b/content/docs-archive/v0.8.3/configuration/authentication/OAuth2-OIDC/meta.json
new file mode 100644
index 000000000..b96081a48
--- /dev/null
+++ b/content/docs-archive/v0.8.3/configuration/authentication/OAuth2-OIDC/meta.json
@@ -0,0 +1,21 @@
+{
+ "title": "OAuth2 & OIDC",
+ "icon": "KeyRound",
+ "pages": [
+ "index",
+ "---OAuth2---",
+ "apple",
+ "discord",
+ "facebook",
+ "github",
+ "google",
+ "---OIDC---",
+ "auth0",
+ "authelia",
+ "authentik",
+ "aws",
+ "azure",
+ "keycloak",
+ "token-reuse"
+ ]
+}
diff --git a/content/docs-archive/v0.8.3/configuration/authentication/OAuth2-OIDC/token-reuse.mdx b/content/docs-archive/v0.8.3/configuration/authentication/OAuth2-OIDC/token-reuse.mdx
new file mode 100644
index 000000000..4248a7021
--- /dev/null
+++ b/content/docs-archive/v0.8.3/configuration/authentication/OAuth2-OIDC/token-reuse.mdx
@@ -0,0 +1,144 @@
+---
+title: OpenID Connect Token Reuse
+icon: Fingerprint
+description: How to configure OpenID Connect token reuse with LibreChat
+---
+
+LibreChat supports reusing access and refresh tokens issued by your OpenID Connect provider (like Azure Entra ID or Auth0) to manage user authentication state. When this feature is active, the refresh token passed to the user as a cookie is issued by your OpenID provider instead of LibreChat, allowing LibreChat servers to refresh it and request access tokens from your provider.
+
+## Prerequisites
+
+- A configured OpenID Connect provider (like Azure Entra ID, Auth0, etc.)
+- Basic OpenID Connect setup completed
+
+## Configuration Steps
+
+1. Set `OPENID_REUSE_TOKENS=true` in your environment variables.
+
+## Provider-Specific Configuration
+
+### Auth0 Configuration
+
+
+
+
+
+
+
+
+
+
+
+
+## Session Expiry and Refresh Token
+
+- Default values: session expiry: 15 minutes, refresh token expiry: 7 days
+ - For more information: **[GitHub PR #927 - Refresh Token](https://github.com/danny-avila/LibreChat/pull/927)**
+
+
+ 
+
+
+
+ 
+
+
+
+
+## Production Setup
+
+Azure Blob Storage offers scalable, secure object storage for files in LibreChat. Follow these steps to configure your Azure Blob Storage.
+
+## 1. Create an Azure Storage Account
+
+1. **Sign in to Azure:**
+ - Open the [Azure Portal](https://portal.azure.com/) and sign in with your Microsoft account.
+
+2. **Create a Storage Account:**
+ - Click on **"Create a resource"** and search for **"Storage account"**.
+ - Click **"Create"** and fill in the required details:
+ - **Subscription & Resource Group:** Choose your subscription and either select an existing resource group or create a new one.
+ - **Storage Account Name:** Enter a unique name (e.g., `mylibrechatstorage`).
+ - **Region:** Select the region closest to your users.
+ - **Performance & Redundancy:** Choose the performance tier and redundancy level that best suit your needs.
+ - Click **"Review + Create"** and then **"Create"**. Wait until the deployment completes.
+
+## 2. Set Up Authentication
+
+You have two options for authenticating with your Azure Storage Account:
+
+### Option A: Using a Connection String
+
+1. **Navigate to Access Keys:**
+ - In your newly created storage account, go to **"Access keys"** in the sidebar.
+
+2. **Copy Connection String:**
+ - Copy one of the connection strings provided. This string includes the credentials required to connect to your Blob Storage account.
+
+### Option B: Using Managed Identity
+
+If your LibreChat application is running on an Azure service that supports Managed Identity (such as an Azure VM, App Service, or AKS), you can use that instead of a connection string.
+
+1. **Assign Managed Identity:**
+ - Ensure your Azure resource (VM, App Service, or AKS) has a system-assigned or user-assigned Managed Identity enabled.
+
+2. **Grant Storage Permissions:**
+ - In your storage account, assign the **Storage Blob Data Contributor** (or a similarly scoped role) to your Managed Identity. This allows your application to access Blob Storage without a connection string.
+
+## 3. Update Your Environment Variables
+
+Create or update your `.env` file in your project’s root with the following configuration:
+
+```bash filename=".env"
+# Option A: Using a Connection String
+AZURE_STORAGE_CONNECTION_STRING=DefaultEndpointsProtocol=https;AccountName=yourAccountName;AccountKey=yourAccountKey;EndpointSuffix=core.windows.net
+
+# Option B: Using Managed Identity (do not set the connection string if using Managed Identity)
+AZURE_STORAGE_ACCOUNT_NAME=yourAccountName
+
+AZURE_STORAGE_PUBLIC_ACCESS=false
+AZURE_CONTAINER_NAME=files
+```
+
+- **AZURE_STORAGE_CONNECTION_STRING:** Set this if you are using Option A.
+- **AZURE_STORAGE_ACCOUNT_NAME:** Set this if you are using Option B (Managed Identity). Do not set both.
+- **AZURE_STORAGE_PUBLIC_ACCESS:** Set to `false` if you do not want your blobs to be publicly accessible by default. Set to `true` if you need public access (for example, for publicly viewable images).
+- **AZURE_CONTAINER_NAME:** This is the container name your application will use (e.g., `files`). The application will automatically create this container if it doesn’t exist.
+
+## 4. Configure LibreChat to Use Azure Blob Storage
+
+Update your LibreChat configuration file (`librechat.yaml`) to specify that the application should use Azure Blob Storage for file handling:
+
+```yaml filename="librechat.yaml"
+version: 1.3.5
+cache: true
+fileStrategy: "azure_blob"
+```
+
+On this page
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+Future updates will streamline configuration further by migrating some settings from your [.env file](/v0.8.3/docs/configuration/dotenv) to `librechat.yaml`.
+
+Stay tuned for ongoing enhancements to customize your LibreChat instance!
+
+**Note:** To verify your YAML config, you can use the [YAML Validator](/toolkit/yaml_checker) or other online tools like [yamlchecker.com](https://yamlchecker.com/)
+
+
+
+
+
+
+
+
+
+
+ - **From Settings Panel**: A dedicated "MCP Settings" section in the right panel lists all MCP servers with definable custom variables. Users can click on a server to open the configuration dialog to set or update their credentials for that specific MCP server.
+
+ - These user-provided values are stored securely, associated with the individual user and the specific MCP server, and substituted at runtime.
+- **Example:**
+ ```yaml
+ customUserVars:
+ MY_SERVICE_API_KEY:
+ title: "My Service API Key"
+ description: "Your personal API access key for My Service. Find it at My Service API Settings."
+ SOME_OTHER_VAR:
+ title: "Some Other Variable"
+ description: "The specific value for some other configuration (e.g., a specific path or identifier)."
+ ```
+ Usage in `headers`:
+ ```yaml
+ headers:
+ X-Auth-Token: "{{MY_SERVICE_API_KEY}}"
+ X-Some-Other-Config: "{{SOME_OTHER_VAR}}"
+ ```
+
+#### `oauth`
+
+- **Type:** Object (Optional)
+- **Description:** OAuth2 configuration for authenticating with the MCP server. When configured, users will be prompted to authenticate via OAuth flow before the MCP server can be used. If no client id & client secret is provided, Dynamic Client Registration (DCR) will be used.
+- **Required Subkeys:**
+ - `authorization_url`: String - The OAuth authorization endpoint URL
+ - `token_url`: String - The OAuth token endpoint URL
+ - `client_id`: String - OAuth client identifier
+ - `client_secret`: String - OAuth client secret
+ - `redirect_uri`: String - [OAuth redirect URI](/v0.8.3/docs/features/mcp#oauth-callback-url) (eg. `http://localhost:3080/api/mcp/${serverName}/oauth/callback`)
+ - `scope`: String - OAuth scopes (space-separated)
+- **Optional Subkeys:**
+ - `grant_types_supported`: Array of Strings - Supported grant types (defaults to `["authorization_code", "refresh_token"]`)
+ - `token_endpoint_auth_methods_supported`: Array of Strings - Supported token endpoint authentication methods (defaults to `["client_secret_basic", "client_secret_post"]`)
+ - `response_types_supported`: Array of Strings - Supported response types (defaults to `["code"]`)
+ - `code_challenge_methods_supported`: Array of Strings - Supported PKCE code challenge methods (defaults to `["S256", "plain"]`)
+ - `skip_code_challenge_check`: Boolean - Skip checking whether the OAuth provider advertises PKCE support. Useful for providers like AWS Cognito that support S256 but don't advertise it in their metadata. (defaults to `false`)
+- **Example:**
+ ```yaml
+ oauth-api-server:
+ authorization_url: https://api.example.com/oauth/authorize
+ token_url: https://api.example.com/oauth/token
+ client_id: your_client_id
+ client_secret: your_client_secret
+ redirect_uri: http://localhost:3080/api/mcp/oauth-api-server/oauth/callback
+ scope: "read execute"
+ grant_types_supported: ["authorization_code", "refresh_token"]
+ token_endpoint_auth_methods_supported: ["client_secret_post"]
+ response_types_supported: ["code"]
+ code_challenge_methods_supported: ["S256", "plain"]
+ ```
+
+#### `startup`
+
+- **Type:** Boolean (Optional)
+- **Description:** When set to `false`, this MCP server will not be connected at application startup. This is useful for servers that require user input or configuration before connecting, or for cases where you want to control when the server is initialized.
+- **Default Value:** `true`
+- **Example:**
+ ```yaml
+ mcpServers:
+ my-mcp-server:
+ type: streamable-http
+ url: "https://api.example.com/mcp/"
+ startup: false
+ ```
+
+### Notes
+
+- **Type Inference:**
+ - If `type` is omitted:
+ - If `url` is specified and starts with `http://` or `https://`, `type` defaults to `sse`.
+ - If `url` is specified and starts with `ws://` or `wss://`, `type` defaults to `websocket`.
+ - If `command` is specified, `type` defaults to `stdio`.
+- **Connection Types:**
+ - **`stdio`**: Starts an MCP server as a child process and communicates via standard input/output.
+ - **`websocket`**: Connects to an external MCP server via WebSocket.
+ - **`sse`**: Connects to an external MCP server via Server-Sent Events (SSE).
+ - **`streamable-http`**: Connects to an external MCP server via HTTP with support for streaming responses.
+- **Internal/Local Addresses:**
+ - **Important**: MCP servers using internal IP addresses (e.g., `172.24.1.165`, `192.168.1.100`), or local domains (e.g., `mcp-server`, `host.docker.internal`) **must** be explicitly allowed in [`mcpSettings.allowedDomains`](/v0.8.3/docs/configuration/librechat_yaml/object_structure/mcp_settings).
+ - See [MCP Settings](/v0.8.3/docs/configuration/librechat_yaml/object_structure/mcp_settings) for configuration details.
+
+## Examples
+
+### Configuration with Internal Addresses
+
+When using internal/local MCP servers, you must configure `mcpSettings.allowedDomains`:
+
+```yaml filename="Complete MCP Configuration with Internal Servers"
+# MCP Settings - Required for internal/local addresses
+mcpSettings:
+ allowedDomains:
+ - "172.24.1.165" # Internal IP
+ - "mcp-prod" # Docker container
+ - "host.docker.internal" # Docker host
+
+# MCP Servers - Individual configurations
+mcpServers:
+ prod-mcp:
+ type: streamable-http
+ url: http://172.24.1.165:8000/mcp
+ timeout: 120000
+
+ test-mcp:
+ type: streamable-http
+ url: http://mcp-prod:8001/mcp
+ timeout: 120000
+```
+
+### `stdio` MCP Server
+
+```yaml filename="stdio MCP Server"
+puppeteer:
+ type: stdio
+ command: npx
+ args:
+ - -y
+ - "@modelcontextprotocol/server-puppeteer"
+ timeout: 30000
+ initTimeout: 10000
+ env:
+ NODE_ENV: "production"
+ USER_EMAIL: "{{LIBRECHAT_USER_EMAIL}}"
+ USER_ROLE: "{{LIBRECHAT_USER_ROLE}}"
+ stderr: inherit
+```
+
+### `sse` MCP Server
+
+```yaml filename="sse MCP Server"
+everything:
+ url: http://localhost:3001/sse
+ headers:
+ X-User-ID: "{{LIBRECHAT_USER_ID}}"
+ X-API-Key: "${SOME_API_KEY}"
+```
+
+### `websocket` MCP Server
+
+```yaml filename="websocket MCP Server"
+myWebSocketServer:
+ url: ws://localhost:8080
+```
+
+### `streamable-http` MCP Server
+
+```yaml filename="streamable-http MCP Server"
+streamable-http-server:
+ type: streamable-http
+ url: https://example.com/api/
+ headers:
+ X-User-ID: "{{LIBRECHAT_USER_ID}}"
+ X-API-Key: "${SOME_API_KEY}"
+```
+
+### MCP Server with Dynamic User Fields
+
+```yaml filename="MCP Server with User Fields"
+user-aware-server:
+ type: sse
+ url: https://api.example.com/users/{{LIBRECHAT_USER_USERNAME}}/stream
+ headers:
+ X-User-ID: "{{LIBRECHAT_USER_ID}}"
+ X-User-Email: "{{LIBRECHAT_USER_EMAIL}}"
+ X-User-Role: "{{LIBRECHAT_USER_ROLE}}"
+ X-Email-Verified: "{{LIBRECHAT_USER_EMAILVERIFIED}}"
+ Authorization: "Bearer ${API_TOKEN}"
+```
+
+### MCP Server with Per-User Credentials via `customUserVars`
+
+```yaml filename="MCP Server with customUserVars"
+my-mcp-server:
+ type: streamable-http
+ url: "https://api.example-service.com/api/" # Example URL
+ headers:
+ X-Auth-Token: "{{API_KEY}}" # Uses the API_KEY defined below
+ customUserVars:
+ API_KEY: # This key will be used as {{API_KEY}} in headers/url
+ title: "API Key" # This is the label shown above the input field
+ description: "Get your API key here." # This description appears below the input
+ startup: false # This server will not be connected at application startup since it requires the information provided by the user in customUserVars.
+```
+
+ **NOTE** See [MCP Server Initialization](/v0.8.3/docs/features/mcp#server-initialization) for more information about UI based server initialization.
+
+### MCP Server with Custom Icon
+
+```yaml filename="MCP Server with Icon"
+filesystem:
+ command: npx
+ args:
+ - -y
+ - "@modelcontextprotocol/server-filesystem"
+ - /home/user/LibreChat/
+ iconPath: /home/user/LibreChat/client/public/assets/logo.svg
+ chatMenu: false # Exclude from chatarea dropdown
+```
+
+### MCP Server with OAuth Authentication
+
+```yaml filename="MCP Server with OAuth"
+oauth-api-server:
+ type: streamable-http
+ url: https://api.example.com/mcp/
+ oauth:
+ authorization_url: https://api.example.com/oauth/authorize
+ token_url: https://api.example.com/oauth/token
+ client_id: your_client_id
+ client_secret: your_client_secret
+ redirect_uri: http://localhost:3080/api/mcp/oauth-api-server/oauth/callback
+ scope: "read execute"
+```
+
+### MCP Server with Server Instructions
+
+```yaml filename="MCP Server with Instructions"
+# Server that uses its own provided instructions
+web-search:
+ type: streamable-http
+ url: https://example.com/mcp/search
+ serverInstructions: true
+
+# Server with instructions explicitly disabled
+filesystem:
+ command: npx
+ args:
+ - -y
+ - "@modelcontextprotocol/server-filesystem"
+ - /home/user/documents/
+ serverInstructions: false
+
+# Server with custom instructions
+puppeteer:
+ type: stdio
+ command: npx
+ args:
+ - -y
+ - "@modelcontextprotocol/server-puppeteer"
+ serverInstructions: |
+ Browser automation security and best practices:
+ 1. Be cautious with local file access and internal IP addresses
+ 2. Take screenshots to verify successful page interactions
+ 3. Wait for page elements to load before interacting with them
+ 4. Use specific CSS selectors for reliable element targeting
+ 5. Check console logs for JavaScript errors when troubleshooting
+```
+
+### OAuth-Enabled MCP Server (Legacy requiresOAuth)
+
+```yaml filename="OAuth-Enabled MCP Server"
+composio-googlesheets:
+ type: sse
+ url: https://mcp.composio.dev/googlesheets/sse-endpoint
+ requiresOAuth: true
+ headers:
+ X-User-ID: "{{LIBRECHAT_USER_ID}}"
+ X-API-Key: "${COMPOSIO_API_KEY}"
+ timeout: 45000
+ initTimeout: 15000
+```
+
+**Related Environment Variables (Optional):**
+```bash
+# OAuth configuration for MCP servers
+MCP_OAUTH_ON_AUTH_ERROR=true
+MCP_OAUTH_DETECTION_TIMEOUT=10000
+
+# API key for the service
+COMPOSIO_API_KEY=your_composio_api_key_here
+```
+
+---
+
+**Importing MCP Server Configurations**
+
+The `mcpServers` configurations allow LibreChat to dynamically interact with various MCP servers, which can perform specialized tasks or provide specific functionalities within the application. This modular approach facilitates extending the application's capabilities by simply adding or modifying server configurations.
+
+---
+
+## Additional Information
+
+- **Default Behavior:**
+ - Initialization happens at startup, and the app must be restarted for changes to take effect.
+ - If both `url` and `command` are specified, the `type` must be explicitly defined to avoid ambiguity.
+- **Multi-User Support:**
+ - The MCPManager now supports distinct user-level and app-level connections, enabling proper connection management per user.
+ - User connections are tracked and managed separately, with proper establishment and cleanup.
+ - Use dynamic user field placeholders in headers, URLs, and environment variables:
+ - `{{LIBRECHAT_USER_ID}}` - User's unique identifier
+ - `{{LIBRECHAT_USER_EMAIL}}` - User's email address
+ - `{{LIBRECHAT_USER_USERNAME}}` - User's username
+ - `{{LIBRECHAT_USER_ROLE}}` - User's role (e.g., "user", "admin")
+ - And many more fields (see headers section for complete list)
+- **User Idle Management:**
+ - User connections are monitored for activity and will be disconnected after 15 minutes of inactivity.
+- **Environment Variables:**
+ - **In `env` (for `stdio` type):** Useful for setting up specific runtime environments or configurations required by the MCP server process.
+ - **In `headers` (for `sse` and `streamable-http` types):** Use `${ENV_VAR}` syntax to reference environment variables in header values.
+- **Dynamic User Fields:**
+ - User field placeholders are replaced at runtime with the authenticated user's information
+ - Only non-sensitive fields are available (passwords and other sensitive data are excluded)
+ - Missing fields default to empty strings
+ - Boolean fields are converted to string representations ("true" or "false")
+- **Error Handling (`stderr`):**
+ - Configuring `stderr` allows you to manage how error messages from the MCP server process are handled. The default `"inherit"` means that the errors will be printed to the parent process's `stderr`.
+- **Server Instructions:**
+ - Instructions are automatically injected into the agent's system message when MCP server tools are used
+ - Custom instructions (string values) take precedence over server-provided instructions
+ - Multiple MCP servers can each contribute their own instructions to the agent context
+ - Instructions are only included when the corresponding MCP server's tools are actually available to the agent
+- **OAuth Authentication:**
+ - OAuth2 flow is supported for secure authentication with MCP servers
+ - Users will be prompted to authenticate via OAuth before the MCP server can be used
+
+## References
+
+- [Model Context Protocol (MCP) Documentation](https://github.com/modelcontextprotocol)
+- [MCP Transports Specification](https://modelcontextprotocol.io/specification/draft/basic/transports)
+- [Node.js child_process.spawn](https://nodejs.org/api/child_process.html#child_processspawncommand-args-options)
+
+---
+
+By properly configuring the `mcpServers` in your `librechat.yaml`, you can enhance LibreChat's functionality and integrate custom tools and services seamlessly.
diff --git a/content/docs-archive/v0.8.3/configuration/librechat_yaml/object_structure/mcp_settings.mdx b/content/docs-archive/v0.8.3/configuration/librechat_yaml/object_structure/mcp_settings.mdx
new file mode 100644
index 000000000..d7559319f
--- /dev/null
+++ b/content/docs-archive/v0.8.3/configuration/librechat_yaml/object_structure/mcp_settings.mdx
@@ -0,0 +1,116 @@
+---
+title: "MCP Settings Object Structure"
+icon: Blocks
+---
+
+## Overview
+
+The `mcpSettings` configuration provides global settings for MCP (Model Context Protocol) server security and behavior. This configuration is separate from `mcpServers` and controls how MCP servers can connect to certain domains and IP addresses.
+
+## Example
+
+```yaml filename="MCP Settings Object Structure"
+# Example MCP Settings Configuration
+mcpSettings:
+ allowedDomains:
+ - "example.com" # Specific domain
+ - "*.example.com" # All subdomains using wildcard
+ - "mcp-server" # Local Docker domain
+ - "172.24.1.165" # Internal network IP
+ - "https://api.example.com:8443" # With protocol and port
+```
+
+## Configuration
+
+### Subkeys
+
+
+
+
+
+
+```
+
+### How to Upload Images and Videos on GitHub
+
+
+
+
+
+
+Hello
+}
+```
+````
diff --git a/content/docs-archive/v0.8.3/features/agents.mdx b/content/docs-archive/v0.8.3/features/agents.mdx
new file mode 100644
index 000000000..bad62cc60
--- /dev/null
+++ b/content/docs-archive/v0.8.3/features/agents.mdx
@@ -0,0 +1,476 @@
+---
+title: Agents
+icon: Bot
+description: Learn how to create, customize, and leverage LibreChat's AI Agents - a powerful framework for building custom AI assistants with any model provider.
+---
+
+# Agents: Build Custom AI Assistants
+
+LibreChat's AI Agents feature provides a flexible framework for creating custom AI assistants powered by various model providers.
+
+This feature is similar to OpenAI's Assistants API and ChatGPT's GPTs, but with broader model support and a no-code implementation, letting you build sophisticated assistants with specialized capabilities.
+
+## Getting Started
+
+To create a new agent, select "Agents" from the endpoint menu and open the Agent Builder panel found in the Side Panel.
+
+
+
+The creation form includes:
+
+- **Avatar**: Upload a custom avatar to personalize your agent
+- **Name**: Choose a distinctive name for your agent
+- **Description**: Optional details about your agent's purpose
+- **Instructions**: System instructions that define your agent's behavior
+- **Model**: Select from available providers and models
+
+**Existing agents can be selected from the top dropdown of the Side Panel.**
+- **Also by mention with "@" in the chat input.**
+
+
+
+### Model Configuration
+
+The model parameters interface allows fine-tuning of your agent's responses:
+
+- Temperature (0-1 scale for response creativity)
+- Max context tokens
+- Max output tokens
+- Additional provider-specific settings
+
+## Agent Capabilities
+
+> **Note:** All capabilities can be toggled via the `librechat.yaml` configuration file. See [docs/configuration/librechat_yaml/object_structure/agents#capabilities](/v0.8.3/docs/configuration/librechat_yaml/object_structure/agents#capabilities) for more information.
+
+### Code Interpreter
+
+When enabled, the Code Interpreter capability allows your agent to:
+- Execute code in multiple languages, including:
+ - Python, JavaScript, TypeScript, Go, C, C++, Java, PHP, Rust, and Fortran
+- Process files securely through the LibreChat Code Interpreter API
+- Run code without local setup, configuration, or sandbox deployment
+- Handle file uploads and downloads seamlessly
+- [More info about the Code Interpreter API](/v0.8.3/docs/features/code_interpreter)
+ - **Requires an API Subscription from [code.librechat.ai](https://code.librechat.ai/pricing)**
+
+### File Search
+
+The File Search capability enables:
+- RAG (Retrieval-Augmented Generation) functionality
+- Semantic search across uploaded documents
+- Context-aware responses based on file contents
+- File attachment support at both agent and chat thread levels
+
+### File Context
+
+The File Context capability allows your agent to store extracted text from files as part of its system instructions:
+
+- Extract text while maintaining document structure and formatting
+- Process complex layouts including multi-column text and mixed content
+- Handle tables, equations, and other specialized content
+- Work with multilingual content
+- Text is stored in the agent's instructions in the database
+- **No OCR service required** - Uses text parsing by default with fallback methods
+- **Enhanced by OCR** - If OCR is configured, extraction quality improves for images and scanned documents
+- Uses the same processing logic as "Upload as Text": **OCR > STT > text parsing**
+- [More info about OCR configuration](/v0.8.3/docs/features/ocr)
+
+**Note:** File Context includes extracted text in the agent's system instructions. For temporary document questions in individual conversations, use [Upload as Text](/v0.8.3/docs/features/upload_as_text) from the chat instead.
+
+### Model Context Protocol (MCP)
+
+MCP is an open protocol that standardizes how applications provide context to Large Language Models (LLMs), acting like a universal adapter for AI tools and data sources.
+
+For more information, see documentation on [MCP](/v0.8.3/docs/features/mcp).
+
+#### Agents with MCP Tools
+
+
+1. Configure MCP servers in your `librechat.yaml` file
+2. Restart LibreChat to initialize the connections
+3. Create or edit an agent
+4. Click the "Add Tools" button in the Agent Builder panel to open the Tools Dialog shown below
+5. Select the MCP server(s) you want to add - each server appears as a single entry
+6. Save your changes to the agent
+
+In this example, we've added the **[Spotify MCP server](https://github.com/LibreChat-AI/spotify-mcp)** to an agent.
+
+
+
+#### Managing MCP Tools
+
+Once an MCP server is added to an agent, you can fine-tune which specific tools are available:
+
+- After adding an MCP server, expand it to see all available tools
+- Check/uncheck individual tools as needed
+- For example, the Spotify MCP server provides ~20 tools (search, playback control, playlist management, etc.)
+- This granular control lets you limit agents to only the tools they need
+
+
+
+Learn More:
+- [Configuring MCP Servers](/v0.8.3/docs/features/mcp)
+- [Model Context Protocol Introduction](https://modelcontextprotocol.io/introduction)
+
+### Deferred Tools
+
+Deferred tools allow agents to have access to many MCP tools without loading them all into the LLM context upfront. Instead, deferred tools are discoverable at runtime via a **Tool Search** mechanism.
+
+This is especially useful when an agent has access to many MCP servers with dozens of tools—loading them all would consume a large portion of the context window and degrade response quality.
+
+**How it works:**
+- Tools marked as "deferred" are excluded from the initial LLM context
+- A `ToolSearch` tool is automatically added, allowing the LLM to discover and load deferred tools on demand
+- Once discovered, the tool is available for the rest of the conversation
+
+**Configuring deferred tools:**
+1. Open the Agent Builder and add MCP tools
+2. Click the dropdown on any MCP tool
+3. Toggle "Defer Loading" — deferred tools show a clock icon
+
+**Note:** The `deferred_tools` capability is enabled by default. It can be toggled via the [`librechat.yaml` agents configuration](/v0.8.3/docs/configuration/librechat_yaml/object_structure/agents#capabilities).
+
+{/*
+### Programmatic Tool Calling
+
+**Note:** this feature is still in private beta and not accessible to all users.
+
+Programmatic Tool Calling (PTC) allows MCP tools to be executed via code in a sandbox environment rather than being called directly by the LLM. This enables more complex tool orchestration—for example, calling multiple tools in sequence, processing results with code, or building dynamic workflows.
+
+**How it works:**
+- Tools marked for "code execution" calling are routed through the Code Interpreter sandbox
+- The LLM writes code that calls the tools programmatically, allowing for loops, conditionals, and data transformations
+- Results flow back through the sandbox to the LLM
+
+**Configuring programmatic tools:**
+1. Open the Agent Builder and add MCP tools
+2. Click the dropdown on any MCP tool
+3. Toggle "Code Execution" calling — programmatic tools show a code icon
+
+**Note:** The `programmatic_tools` capability is **disabled by default** and requires the latest [Code Interpreter API](/v0.8.3/docs/features/code_interpreter). It can be enabled via the [`librechat.yaml` agents configuration](/v0.8.3/docs/configuration/librechat_yaml/object_structure/agents#capabilities).
+*/}
+
+### Artifacts
+
+The Artifacts capability enables your agent to generate and display interactive content:
+
+- Create React components, HTML code, and Mermaid diagrams
+- Display content in a separate UI window for clarity and interaction
+- Configure artifact-specific instructions at the agent level
+- [More info about Artifacts](/v0.8.3/docs/features/artifacts)
+
+When enabled, additional instructions specific to the use of artifacts are added by default. Options include:
+
+- **Enable shadcn/ui instructions**: Adds instructions for using shadcn/ui components (a collection of re-usable components built using Radix UI and Tailwind CSS)
+- **Custom Prompt Mode**: When enabled, the default artifacts system prompt will not be included, allowing you to provide your own custom instructions
+
+Configuring artifacts at the agent level is the preferred approach, as it allows for more granular control compared to the legacy app-wide configuration.
+
+If you enable Custom Prompt Mode, you should include at minimum the basic artifact format in your instructions.
+
+Here's a simple example of the minimum instructions needed:
+
+````md
+When creating content that should be displayed as an artifact, use the following format:
+
+:::artifact{identifier="unique-identifier" type="mime-type" title="Artifact Title"}
+```
+Your artifact content here
+```
+:::
+
+For the type attribute, use one of:
+- "text/html" for HTML content
+- "application/vnd.mermaid" for Mermaid diagrams
+- "application/vnd.react" for React components
+- "image/svg+xml" for SVG images
+````
+
+### Tools
+
+Agents can also be enhanced with various built-in tools:
+
+- **[OpenAI Image Tools](/v0.8.3/docs/features/image_gen#1--openai-image-tools-recommended)**: Image generation & editing using **[GPT-Image-1](https://platform.openai.com/docs/models/gpt-image-1)**
+- **[DALL-E-3](/v0.8.3/docs/features/image_gen#2--dalle-legacy)**: Image generation from text descriptions
+- **[Stable Diffusion](/v0.8.3/docs/features/image_gen#3--stable-diffusion-local)** / **[Flux](/v0.8.3/docs/features/image_gen#4--flux)**: Text-to-image generation
+- **[Wolfram](/v0.8.3/docs/configuration/tools/wolfram)**: Computational and mathematical capabilities
+- **[OpenWeather](/v0.8.3/docs/configuration/tools/openweather)**: Weather data retrieval
+- **[Google Search](/v0.8.3/docs/configuration/tools/google_search)**: Access to web search functionality
+- **Calculator**: Mathematical calculations
+- **Tavily Search**: Advanced search API with diverse data source integration
+- **Azure AI Search**: Information retrieval
+- **Traversaal**: A robust search API for LLM Agents
+
+- Tools can be disabled using the [`librechat.yaml`](/v0.8.3/docs/configuration/librechat_yaml) configuration file:
+ - [More info](/v0.8.3/docs/configuration/librechat_yaml/object_structure/agents#capabilities)
+
+### Actions
+
+With the Actions capability, you can dynamically create tools from [OpenAPI specs](https://swagger.io/specification/) to add to your Agents.
+
+
+
+**Clicking the button above will open a form where you can input the OpenAPI spec URL and create an action:**
+
+
+
+- Actions can be disabled using the [`librechat.yaml`](/v0.8.3/docs/configuration/librechat_yaml) configuration file:
+ - [More info](/v0.8.3/docs/configuration/librechat_yaml/object_structure/agents#capabilities)
+- Individual domains can be whitelisted for agent actions:
+ - [More info](/v0.8.3/docs/configuration/librechat_yaml/object_structure/actions#alloweddomains)
+- Note that you can add add the 'x-strict': true flag at operation-level in the OpenAPI spec for actions.
+If using an OpenAI model supporting it, this will automatically generate function calls with 'strict' mode enabled.
+ - Strict mode supports only a partial subset of json. Read https://platform.openai.com/docs/guides/structured-outputs/some-type-specific-keywords-are-not-yet-supported for details.
+
+### Agent Chain
+
+The Agent Chain capability enables a Mixture-of-Agents (MoA) approach, allowing you to create a sequence of agents that work together:
+
+- Create chains of specialized agents for complex tasks
+- Each agent in the chain can access outputs from previous agents
+- Configure the maximum number of steps for the agent chain
+- **Note:** Access this feature from the Advanced Settings panel in the Agent Builder
+- **Note:** This feature is currently in beta and may be subject to change
+ - The current maximum of agents that can be chained is 10, but this may be configurable in the future
+
+
+
+This feature introduces a layered Mixture-of-Agents architecture to LibreChat, where each agent takes all the outputs from agents in the previous layer as auxiliary information in generating its response, as described in [the eponymous "Mixture-of-Agents" paper](https://arxiv.org/abs/2406.04692).
+
+### Advanced Settings
+
+Advanced settings for your agent (found in the Advanced view of the Agent form) outside of "capabilities."
+
+#### Max Agent Steps
+
+This setting allows you to limit the number of steps an agent can take in a "run," which refers to the agent loop before a final response is given.
+
+If left unconfigured, the default is 25 steps, but you can adjust this to suit your needs. For admins, you can set a global default as well as a global maximum in the [`librechat.yaml`](/v0.8.3/docs/configuration/librechat_yaml/object_structure/agents#recursionlimit) file.
+
+A "step" refers to either an AI API request or a round of tool usage (1 or many tools, depending on how many tool calls the LLM provides from a single request).
+
+A single, non-tool response is 1 step. A singular round of tool usage is usually 3 steps:
+
+1. API Request -> 2. Tool Usage (1 or many tools) -> 3. Follow-up API Request
+
+## File Management
+
+Agents support multiple ways to work with files:
+
+### In Chat Interface
+
+When chatting with an agent, you have four upload options:
+
+1. **Upload Images**
+ - Uploads images for native vision model support
+ - Sends images directly to the model provider
+
+2. **Upload as Text** (requires `context` capability)
+ - Extracts and includes full document content in conversation
+ - Uses text parsing by default; enhanced by OCR if configured
+ - Content exists only in current conversation
+ - See [Upload as Text](/v0.8.3/docs/features/upload_as_text)
+
+3. **Upload for File Search** (requires `file_search` capability, toggled ON)
+ - Uses semantic search (RAG) with vector stores
+ - Returns relevant chunks via tool use
+ - Optimal for large documents/multiple files
+ - Sub-optimal for structured data (CSV, Excel, JSON, etc.)
+
+4. **Upload for Code Interpreter** (requires `execute_code` capability, toggled ON)
+ - Adds files to code interpreter environment
+ - Optimal for structured data (CSV, Excel, JSON, etc.)
+ - More info about [Code Interpreter](/v0.8.3/docs/features/code_interpreter)
+
+### In Agent Builder
+
+When configuring an agent, you can attach files in different categories:
+
+1. **Image Upload**: For visual content the agent can reference
+2. **File Search Upload**: Documents for RAG capabilities
+3. **Code Interpreter Upload**: Files for code processing
+4. **File Context**: Documents with extracted text to supplement agent instructions
+
+**File Context** uses the `context` capability and works just like ["Upload as Text"](/v0.8.3/docs/features/upload_as_text) - it uses text parsing by default and is enhanced by OCR when configured. Text is extracted at upload time and stored in the agent's instructions. This is ideal for giving agents persistent knowledge from documents, PDFs, code files, or images with text.
+
+**Processing priority:** OCR > STT > text parsing (same as Upload as Text)
+
+**Note:** The extracted text is included as part of the agent's system instructions.
+
+## Sharing and Permissions
+
+### Administrator Controls
+
+Administrators have access to global permission settings within the agent builder UI:
+
+- Enable/disable agent sharing across all users
+- Control agent usage permissions
+- Manage agent creation rights
+- Configure platform-wide settings
+
+The first account created for your instance is an administrator. If you need to add an additional administrator, you may [access MongoDB](/v0.8.3/docs/configuration/mongodb/mongodb_auth) and update the user's profile:
+
+```
+db.users.updateOne(
+ { email: 'USER_EMAIL_ADDRESS' },
+ { $set: { role: 'ADMIN' } }
+)
+```
+
+The use of agents for all users can also be disabled via config, [more info](/v0.8.3/docs/configuration/librechat_yaml/object_structure/interface).
+
+### User-Level Sharing
+
+Individual users can:
+- Share their agents with all users (if enabled)
+- Control editing permissions for shared agents
+- Manage access to their created agents
+
+### Notes
+
+- Instructions, model parameters, attached files, and tools are only exposed to the user if they have editing permissions
+ - An agent may leak any attached data, whether instructions or files, through conversation--make sure your instructions are robust against this
+- Only original authors and administrators can delete shared agents
+- Agents are private to authors unless shared
+
+## Optional Configuration
+
+LibreChat allows admins to configure the use of agents via the [`librechat.yaml`](/v0.8.3/docs/configuration/librechat_yaml) file:
+
+- Disable Agents for all users (including admins): [more info](/v0.8.3/docs/configuration/librechat_yaml/object_structure/interface)
+- Customize agent capabilities using: [more info](/v0.8.3/docs/configuration/librechat_yaml/object_structure/agents)
+
+## Best Practices
+
+- Provide clear, specific instructions for your agent
+- Carefully consider which tools are necessary for your use case
+- Organize files appropriately across the four upload categories
+- Review permission settings before sharing agents
+- Test your agent thoroughly before deploying to other users
+
+## Recap
+
+1. Select "Agents" from the endpoint dropdown menu
+2. Open the Agent Builder panel
+3. Fill out the required agent details
+4. Configure desired capabilities (Code Interpreter, File Search, File Context, etc.)
+5. Add necessary tools and files
+6. Set sharing permissions if desired
+7. Create and start using your agent
+
+When chatting with agents, you can:
+- Use "Upload as Text" to include full document content in conversations (text parsing by default, enhanced by OCR)
+- Use "Upload for File Search" for semantic search over documents (requires RAG API)
+- Add files to agent's "File Context" to included a file's full content as part of the agent's system instructions
+
+## Migration Required (v0.8.0-rc3+)
+
+
+
+
+
+## Key Features of LibreChat's Code Artifacts:
+
+- Instant prototyping of websites and UIs with generative AI
+- Effortless creation of dynamic, responsive layouts
+- Interactive learning environment for React and HTML
+- Complex idea visualization using Mermaid diagrams
+- AI-powered intuitive, user-centric design iterations
+- Free and open-source alternative to paid AI tools
+
+Experience the future of UI/UX design and development with LibreChat's generative capabilities. Bring your ideas to life faster than ever before!
+
+## Content-Security-Policy
+
+You may need to need to update your web server's Content-Security-Policy to include `frame-src 'self' https://*.codesandbox.io` in order to load generated HTML apps in the Artifacts panel. This is a dependency of the [sandpack](https://sandpack.codesandbox.io/) library.
+
+## Self-Hosting the Sandpack Bundler
+
+Artifacts in LibreChat use CodeSandbox's Sandpack library to securely render HTML/JS code. By default, LibreChat connects to CodeSandbox's public CDN, which may also transmit telemetry for its usage.
+
+For enhanced privacy, security compliance, or isolated network environments, you can [self-host the bundler.](https://sandpack.codesandbox.io/docs/guides/hosting-the-bundler)
+
+### Why Self-Host the Sandpack Bundler?
+
+[Self-hosting the bundler](https://sandpack.codesandbox.io/docs/guides/hosting-the-bundler) provides several advantages:
+
+- **Privacy & Security**: Keep code execution within your own infrastructure
+- **Reliability**: Remove dependency on external services
+- **Performance**: Reduce latency by hosting the bundler in your network
+- **Compliance**: Meet organizational data handling requirements
+- **Control**: Configure and customize to your specific needs
+
+### Configuration
+
+Once you have a self-hosted bundler set up, simply configure LibreChat to use it by setting the environment variable:
+
+```bash
+# `.env` file
+SANDPACK_BUNDLER_URL=http://your-bundler-url
+```
+
+### General Considerations
+
+Self-hosting the bundler introduces some additional overhead:
+
+- **CORS Configuration**: You'll need to manage cross-origin resource sharing policies
+- **Security Management**: You become responsible for the security of the bundler service
+- **Maintenance**: Updates and patches will need to be applied manually
+- **Resource Requirements**: Additional server resources will be needed to host the bundler
+
+For detailed instructions on setting up and maintaining your self-hosted bundler, refer to the [forked CodeSandbox repository](https://github.com/LibreChat-AI/codesandbox-client) tailored for LibreChat deployment, including the removal of telemetry from Sandpack.
+
+---
+
+AI News 2024: The Original and BEST Open-Source AI Chat Platform, LibreChat Releases Code Artifacts! This Generative UI Tool Can Generate React, HTML & Diagrams Instantly from a Single Prompt in Your Browser with Any LLM, OpenAI, Anthropic, LLAMA, Mistral, DeepSeek Coder & More Thanks to OLLAMA Integration.
+
+#AINews2024 #OpenSourceAI #GenerativeUI #CodeArtifacts #WebDevelopment #ReactJS #LLM #AIPrototyping #DevTools #OLLAMA #LibreChat
diff --git a/content/docs-archive/v0.8.3/features/authentication.mdx b/content/docs-archive/v0.8.3/features/authentication.mdx
new file mode 100644
index 000000000..af7576f6e
--- /dev/null
+++ b/content/docs-archive/v0.8.3/features/authentication.mdx
@@ -0,0 +1,30 @@
+---
+title: Authentication
+icon: Lock
+description: Quick overview of the user authentication system of LibreChat, which offers secure and easy email and social logins.
+---
+
+
+LibreChat has a user authentication system that allows users to sign up and log in securely and easily. The system is scalable and can handle a large number of concurrent users without compromising performance or security.
+
+By default, we have email signup and login enabled, which means users can create an account using their email address and a password. They can also reset their password if they forget it.
+
+Additionally, our system can integrate social logins from various platforms such as Google, GitHub, Discord, OpenID, and more. This means users can log in using their existing accounts on these platforms, without having to create a new account or remember another password.
+
+**For further details, refer to the configuration guides provided here: [Authentication](/v0.8.3/docs/configuration/authentication)**
+
+
+
diff --git a/content/docs-archive/v0.8.3/features/code_interpreter.mdx b/content/docs-archive/v0.8.3/features/code_interpreter.mdx
new file mode 100644
index 000000000..e749f930d
--- /dev/null
+++ b/content/docs-archive/v0.8.3/features/code_interpreter.mdx
@@ -0,0 +1,149 @@
+---
+title: Code Interpreter API
+icon: SquareTerminal
+description: Execute code securely and manage files seamlessly with LibreChat's Code Interpreter API
+---
+
+## Introduction
+
+LibreChat's Code Interpreter API provides a secure and hassle-free way to execute code and manage files through a simple API interface. Whether you're using it through LibreChat's Agents or integrating it directly into your applications, the API offers a powerful sandbox environment for running code in multiple programming languages.
+
+
+
+## Subscription
+**Access to this feature requires an [API subscription, get started here](https://code.librechat.ai/pricing).**
+
+## Getting Started
+
+1. Visit [code.librechat.ai](https://code.librechat.ai/pricing) to get your API key
+2. Integrate the API into your application or use it through LibreChat
+3. Start executing code and generating files securely
+
+## Key Features
+
+### Supported Languages
+
+Execute code in multiple programming languages:
+- Python, Node.js (JS/TS), Go, C/C++, Java, PHP, Rust, Fortran, Rscript
+
+### Seamless File Handling
+
+- Upload files for processing
+- Download generated outputs
+- Secure file management
+- Session-based file organization
+
+### Security & Convenience
+
+- Secure sandboxed execution environment
+- No local setup required
+- No server deployment needed
+- No configuration management
+
+## Using the API
+
+### In LibreChat
+
+The API has first-class support in LibreChat through two main methods:
+
+1. **[AI Agents](/v0.8.3/docs/features/agents#code-interpreter)**: Enable Code Interpreter in your agent's configuration to allow it to execute code and process files automatically.
+
+2. **Manual Execution**: Use the "Run Code" button in code blocks within the chat interface, as shown here:
+
+
+
+### Set up API key
+
+- **Per-user setup:** input your API key in LibreChat when prompted (using the above methods)
+- **Global setup:** use `LIBRECHAT_CODE_API_KEY` environment variable in the .env file of your project (provides access to all users)
+
+### Direct API Integration
+
+The Code Interpreter API can be integrated into any application using a simple API key authentication:
+
+1. Get your API key from [code.librechat.ai](https://code.librechat.ai/pricing)
+2. Include the API key in your requests using the `x-api-key` header
+
+### Enterprise
+
+The enterprise plan requires use of the `LIBRECHAT_CODE_BASEURL` environment variable to correspond with the self-hosted instance of the API, along with any generated API keys from the dashboard, used the same way as mentioned above.
+
+## Core Functionality
+
+### Code Execution
+
+- Run code snippets in supported languages
+- Receive stdout/stderr output
+- Get execution statistics (memory usage, CPU time)
+- Handle program arguments
+- Access execution status and results
+
+### File Operations
+
+- Upload input files
+- Download generated outputs
+- List available files
+- Delete unnecessary files
+- Manage file sessions
+
+### Limitations
+- Code cannot access the network
+- Only 10 files can be generated per run
+- Execution limits vary by plan:
+ - **Hobby**:
+ - 256 MB RAM per execution
+ - 25 MB per file upload
+ - 750 requests per month
+ - **Enthusiast**:
+ - 512 MB RAM per execution
+ - 50 MB per file upload
+ - 3,000 requests per month
+ - **Pro**:
+ - 512 MB RAM per execution
+ - 150 MB per file upload
+ - 7,000 requests per month
+- The [Enterprise Plan](https://code.librechat.ai/pricing) provides custom limits and features
+
+## Use Cases
+
+- **Code Testing**: Test code snippets in multiple languages
+- **File Processing**: Transform and analyze files programmatically
+- **AI Applications**: Execute AI-generated code securely
+- **Development Tools**: Build interactive coding environments
+- **Objective Logic**: Verify code logic and correctness, improving AI models
+
+## Why a Paid API?
+
+While LibreChat remains free and open source under the MIT license, the Code Interpreter API is offered as a paid service for several key reasons:
+
+1. **Project Sustainability**: Subscribing to an API plan provides direct support to the project's development, even more effectively than [GitHub Sponsors](https://github.com/sponsors/danny-avila). Your subscription helps ensure LibreChat's continued growth and improvement.
+
+2. **Technical Considerations**: Including code execution capabilities in the core project would add significant complexity and hardware requirements that not all users need. The API service eliminates these concerns while maintaining a lightweight core application.
+
+3. **Managed Service Benefits**:
+ - No complex configuration
+ - Immediate availability
+ - Regular updates and maintenance
+ - Professional support
+ - Secure, sandboxed environment
+
+4. **Intellectual Property Protection**: The Code Interpreter's architecture represents significant innovation in secure, scalable sandbox technology. While similar solutions exist, they often lack the comprehensive security measures and scalability features that make this implementation unique. Keeping this component as a closed-source API helps protect these innovations and ensures the service maintains its high security and performance standards.
+
+Even if you only use code execution occasionally, subscribing helps support LibreChat's development while enhancing your experience with professional-grade features. It's a win-win that keeps the core project free while offering optional advanced capabilities for those who need them.
+
+---
+
+## Conclusion
+
+The Code Interpreter API provides a secure, convenient way to execute code and manage files without the hassle of setting up and maintaining execution environments. Whether you're using it through LibreChat's Agents or integrating it directly into your applications, it offers a robust solution for code execution needs.
+
+For detailed technical specifications and API reference, please visit our [API Documentation](https://code.librechat.ai/docs).
+
+#LibreChat #CodeExecution #API #Development
\ No newline at end of file
diff --git a/content/docs-archive/v0.8.3/features/fork.mdx b/content/docs-archive/v0.8.3/features/fork.mdx
new file mode 100644
index 000000000..d5454cdd2
--- /dev/null
+++ b/content/docs-archive/v0.8.3/features/fork.mdx
@@ -0,0 +1,123 @@
+---
+title: Forking Chats
+icon: GitFork
+description: A guide on how to use the "Fork Messages/Conversations" feature in our app to create new conversations from specific messages with desired behavior.
+---
+
+import Image from 'next/image'
+
+
+ 
+
+
+
+ 
+
+
+
+
+
+### Include related branches:
+This option forks the visible messages, along with related branches; in other words, the direct path to the target message, including branches along the path.
+
+
+
+
+
+
+
+
+
+
+
+### Include all to/from here (default):
+This option forks all messages leading up to the target message, including its neighbors; in other words, all message branches, whether or not they are visible or along the same path, are included.
+
+
+
+
+
+
+
+
+
+
+
+## Additional Options
+
+- **Start fork here:** If checked, forking will commence from this message to the latest message in the conversation, according to the behavior selected above.
+
+
+
+
+
+
+
+
+
+
+
+- **Remember:** Check to remember the options you select for future usage, making it quicker to fork conversations as preferred.
+
+
+
+
+
+
+
+
+
+
+
+- Alternatively you can control the default behavior in the settings menu:
+
+
+
+
+
+
+
+
+
+
diff --git a/content/docs-archive/v0.8.3/features/image_gen.mdx b/content/docs-archive/v0.8.3/features/image_gen.mdx
new file mode 100644
index 000000000..99fec35f5
--- /dev/null
+++ b/content/docs-archive/v0.8.3/features/image_gen.mdx
@@ -0,0 +1,377 @@
+---
+title: Image Generation & Editing
+icon: Image
+description: Comprehensive guide to LibreChat's built-in image generation and editing tools
+---
+
+## 🎨 Image Generation & Editing
+
+LibreChat comes with **built-in image tools** that you can add to an **[Agent](/v0.8.3/docs/features/agents).**
+
+Each has its own look, price-point, and setup step (usually just an API key or URL).
+
+| Tool | Best for | Needs |
+|------|----------|-------|
+| **OpenAI Image Tools** | Cutting-edge results (GPT-Image-1).
+
+
+
+
+
+
+Can also ***edit*** the images you upload. | OpenAI API | +| **Gemini Image Tools** | Google's latest image models with context-aware generation. | Gemini API or Vertex AI | +| **DALL·E (3 / 2)** | Legacy OpenAI Image models. | OpenAI API | +| **Stable Diffusion** | Local or self-hosted generation, endless community models. | Automatic1111 API | +| **Flux** | Fast cloud renders, optional fine-tunes. | Flux API | +| **MCP** | Bring-your-own-Image-Generators | MCP server with image output support | + +**Notes:** +- API keys can be omitted in favor of allowing the user to enter their own key from the UI. +- Image Outputs are directly sent to the LLM as part of the immediate chat context following generation. + - The LLM will only get vision context from images attached to user messages, and not from generations/edits, except for immediately after generation. + - See [Image Storage and Handling](#image-storage-and-handling) for more details. +- MCP Server tool image outputs are supported, which may output images similarly to LC's built-in tools. + - Note: MCP servers may or may not use the correct format when outputting images. See details in the [MCP section below](#5--model-context-protocol-mcp). + +--- + +## 1 · OpenAI Image Tools (recommended) + +### Features + +"OpenAI Image Tools" are an agent toolkit made up of 2 separate tools. + +- **Image Generation**: + - **Create** brand-new images from text prompts (no upload required). +- **Image Editing**: + - **Edit** or **remix** the images you just uploaded—change colours, add objects, extend the canvas, etc. +- Both use OpenAI's latest image generation model, **GPT-Image-1**, for superior instruction following, text rendering, detailed editing, real-world knowledge +- See OpenAI's [Image Generation documentation](https://platform.openai.com/docs/guides/image-generation?image-generation-model=gpt-image-1) for more details. + +#### Generation vs. Editing +| Use-case | Invokes | +|----------|---------------| +| "Start from scratch" | **Image Generation** | +| "Use existing image(s)" | **Image Editing** | + +The agent decides which tool to use based on the context: + +- **Image Generation** creates brand new images from text descriptions only +- **Image Editing** modifies or remixes existing images using their image IDs + - These can be images from the current message or previously generated/referenced images + - The LLM keeps track of image IDs as long as they remain in the context window + - Includes the referenced image IDs in the tool output +- Both tools are always available, but the LLM will choose the appropriate one based on the user's request +- Both tools will include the generated image ID in the tool output + +⚠️ **Important** +- Image editing relies on image IDs, which are retained in the chat history. +- When files are uploaded to the current request, their image IDs are added to the context of the LLM before any tokens are generated. +- Previously referenced or generated image IDs can be used for editing, as long as they remain within the context window. +- The LLM can include any relevant image IDs in the `image_ids` array when calling the image editing tool. +- You can also attach previously uploaded images from the side panel without needing to upload them again. + - This also has the added benefit of providing a vision model with the image context, which can be useful for informing the `prompt` for the image editing tool. + +### Parameters + +#### Image Generation +• **prompt** – text description (required) +• **size** – `auto` (default), `1024x1024` (square), `1536x1024` (landscape), or `1024x1536` (portrait) +• **quality** – `auto` (default), `high`, `medium`, or `low` +• **background** – `auto` (default), `transparent`, or `opaque` (transparent requires PNG or WebP format) + +#### Image Editing + +• **image_ids** – array of image IDs to use as reference for editing (required) +• **prompt** – text description of the changes (required) +• **size** – `auto` (default), `1024x1024`, `1536x1024`, `1024x1536`, `256x256`, or `512x512` +• **quality** – `auto` (default), `high`, `medium`, or `low` + +### Setup +Create or reuse an OpenAI key and add to `.env`: + +```bash +IMAGE_GEN_OAI_API_KEY=sk-... +# optional extras +IMAGE_GEN_OAI_BASEURL=https://... +``` + +For Azure OpenAI deployments, you will first need access: https://aka.ms/oai/gptimage1access + +Then, add your corresponding credentials to your `.env` file: + +```bash +IMAGE_GEN_OAI_API_KEY=your-api-key +# optional extras +IMAGE_GEN_OAI_BASEURL=https://deploymentname.openai.azure.com/openai/deployments/gpt-image-1/ +IMAGE_GEN_OAI_AZURE_API_VERSION=2025-04-01-preview +``` + +Then add "OpenAI Image Tools" to your Agent's *Tools* list. + +### Advanced Configuration + +You can customize the tool descriptions and prompt guidance by setting these environment variables: + +```bash +# Image Generation Tool Descriptions +IMAGE_GEN_OAI_DESCRIPTION=... +IMAGE_GEN_OAI_PROMPT_DESCRIPTION=... + +# Image Editing Tool Descriptions +IMAGE_EDIT_OAI_DESCRIPTION=... +IMAGE_EDIT_OAI_PROMPT_DESCRIPTION=... +``` + +### Pricing +See the [GPT-Image-1 pricing page](https://platform.openai.com/docs/models/gpt-image-1) and [Image Generation Documentation](https://platform.openai.com/docs/guides/image-generation?image-generation-model=gpt-image-1#cost-and-latency) for details on costs associated with image generation. + +--- + +## 2 · Gemini Image Tools + +Gemini Image Tools integrate Google's latest image generation models, supporting both text-to-image generation and image context-aware editing. + +### Features + +- **Text-to-Image Generation**: Create high-quality images from detailed text descriptions +- **Image Context Support**: Use existing images as context or inspiration for new generations +- **Image Editing**: Generate new images based on modifications to existing ones (include original image ID) +- **Multiple Models**: Choose between `gemini-2.5-flash-image` (default) or `gemini-3-pro-image-preview` +- **Dual API Support**: Works with both simple Gemini API keys and Google Cloud Vertex AI + +### Parameters + +• **prompt** – Detailed text description of the desired image (required, up to 32,000 characters) +• **image_ids** – Optional array of image IDs to use as visual context for generation + +### Setup + +#### Option 1: Gemini API (Recommended) + +Get an API key from [Google AI Studio](https://aistudio.google.com/app/apikey): + +```bash +GEMINI_API_KEY=your_api_key_here +``` + +#### Option 2: Vertex AI (Enterprise) + +For Google Cloud users with Vertex AI access: + +```bash +GOOGLE_SERVICE_KEY_FILE=/path/to/service-account.json +GOOGLE_CLOUD_LOCATION=us-central1 # optional, default: global +``` + +### Model Selection + +```bash +# Default model (fast and efficient) +GEMINI_IMAGE_MODEL=gemini-2.5-flash-image + +# Higher quality model +GEMINI_IMAGE_MODEL=gemini-3-pro-image-preview +``` + +### Advanced Configuration + +Customize tool descriptions via environment variables: + +```bash +GEMINI_IMAGE_GEN_DESCRIPTION=... +GEMINI_IMAGE_GEN_PROMPT_DESCRIPTION=... +GEMINI_IMAGE_IDS_DESCRIPTION=... +``` + +More details can be found in the dedicated [Gemini Image Gen guide](/v0.8.3/docs/configuration/tools/gemini_image_gen). + +--- + +## 3 · DALL·E (legacy) + +DALL·E provides high-quality image generation using OpenAI's legacy image models. + +### Parameters +• **prompt** – Text description of the desired image (required, up to 4000 characters) +• **style** – `vivid` (hyper-real, dramatic - default) or `natural` (less hyper-real) +• **quality** – `standard` (default) or `hd` +• **size** – `1024x1024` (default/square), `1792x1024` (wide), or `1024x1792` (tall) + +### Setup + +```bash +# Required +DALLE_API_KEY=sk-... # or DALLE3_API_KEY=sk-... + +# Optional +DALLE_REVERSE_PROXY=https://... # Alternative endpoint +DALLE3_BASEURL=https://... # For Azure or custom endpoints +DALLE3_AZURE_API_VERSION=2023-12-01-preview # For Azure deployments +DALLE3_SYSTEM_PROMPT=... # Custom system prompt for DALL·E +``` + +### Advanced Configuration +For Azure OpenAI deployments, configure both the base URL and API version: + +```bash +DALLE3_BASEURL=https://your-resource-name.openai.azure.com/openai/deployments/your-deployment-name +DALLE3_AZURE_API_VERSION=2023-12-01-preview +DALLE3_API_KEY=your-azure-api-key +``` + +Enable the **DALL·E** tool for the Agent and start prompting. + +### Pricing +See the [DALL-E pricing page](https://platform.openai.com/docs/models/dall-e-3) and [Image Generation Documentation](https://platform.openai.com/docs/guides/image-generation?image-generation-model=dall-e-3) for details on costs associated with image generation. + +--- + +## 4 · Stable Diffusion (local) + +Run images entirely on your own machine or server. +Point LibreChat at any Automatic1111 (or compatible) endpoint and you're set. + +### Parameters +• **prompt** – Detailed keywords describing desired elements in the image (required) +• **negative_prompt** – Keywords describing elements to exclude from the image (required) + +The Stable Diffusion implementation uses these default parameters: +- cfg_scale: 4.5 +- steps: 22 +- width: 1024 +- height: 1024 + +These values are currently fixed but provide good results for most use cases. + +### Setup + +```bash +SD_WEBUI_URL=http://127.0.0.1:7860 # URL to your Automatic1111 WebUI +``` + +No API key required—just the reachable URL. + +More details on setting up Automatic1111 can be found in the dedicated [Stable Diffusion guide](/v0.8.3/docs/configuration/tools/stable_diffusion). + +--- + +## 5 · Flux + +Cloud generator with an emphasis on speed and optional fine-tuned models. + +### Features +- Fast cloud-based image generation +- Support for fine-tuned models +- Multiple quality levels and aspect ratios +- Raw mode for less processed, more natural-looking images + +### Parameters +The Flux tool supports three main actions: + +1. **generate** - Create a new image from a text prompt +2. **generate_finetuned** - Create an image using a fine-tuned model +3. **list_finetunes** - List available custom models for the user + +More details can be found in the dedicated [Flux guide](/v0.8.3/docs/configuration/tools/flux#parameters). + +### Setup + +```bash +FLUX_API_KEY=flux_live_... +FLUX_API_BASE_URL=https://api.us1.bfl.ai # default is fine for most users +``` + +Choose the **Flux** tool inside the Agent. Prompts are plain text; one call produces one image. + +### Pricing +See the [Flux pricing page](https://docs.bfl.ml/pricing/) for details on costs associated with image generation. + +--- + +## 6 · Model Context Protocol (MCP) + +Image outputs are supported from MCP servers. + +For example, the [Puppeteer MCP Server](https://github.com/modelcontextprotocol/servers/tree/main/src/puppeteer) can be used to generate screenshots of web pages, which correctly output the image in the expected format and is treated the same as LC's built-in image tools. + +> The examples below assume LibreChat is running outside of Docker, directly using Node.js. The Model Context Protocol is a relatively new framework, and many developers are still learning how to properly serve their systems with uv/node for scalable distribution. + +> As this technology is still emerging, there are currently few image-generating servers available, and many existing ones have yet to adopt the correct response format for images. + +> While many MCP servers do function well within Docker, the following examples do not, or not without more advanced configurations, showcasing some of the current inconsistency between MCP servers. + +```yaml +mcpServers: + puppeteer: + command: npx + args: + - -y + - "@modelcontextprotocol/server-puppeteer" +``` + +The following is an example of an [Image Generation server](https://github.com/GongRzhe/Image-Generation-MCP-Server) that outputs images using [Replicate API](https://replicate.com/account/api-tokens), but returns URLs of the images, which doesn't conform to MCP's image response standard. + +> Note: for this particular server, you need to install the `@gongrzhe/image-gen-server` package globally using npm, i.e. `npm install -g @gongrzhe/image-gen-server`, then point to the package's compiled files as shown below. + +```yaml +mcpServers: + image-gen: + command: "node" + # First, install the package globally using npm: + # `npm install -g @gongrzhe/image-gen-server` + # Then, point to the location of the installed package, + # which you can find by running `npm root -g` + args: + - "{REPLACE_WITH_NODE_MODULES_LOCATION}/@gongrzhe/image-gen-server/build/index.js" + # Example with output from `npm root -g`: + # - "/home/danny/.nvm/versions/node/v20.19.0/lib/node_modules/@gongrzhe/image-gen-server/build/index.js" + env: + # Do not hardcode the API token here, use the environment variable instead + # The following will pick up the token from your .env file or environment + REPLICATE_API_TOKEN: "${REPLICATE_API_TOKEN}" + MODEL: "google/imagen-3" +``` + +--- + +## Image Storage and Handling + +All generated images are: +1. Saved according to the configured [**`fileStrategy`**](/v0.8.3/docs/configuration/librechat_yaml/object_structure/config#filestrategy) +2. Displayed directly in the chat interface +3. Image tool outputs are directly sent to the LLM as part of the immediate chat context following generation. + - This may create issues if you are using an LLM that does not support image inputs. + - There will be an option to disable this behavior on a per-agent-basis in the future. + - These outputs are only directly sent to the LLM upon generation, not on every message. + - To include the image in the chat, you can directly attach it to the message from the side panel. + - To summarize, the LLM will only get vision context from images attached to user messages, and not from generations/edits, except for immediately after generation. + +--- + +## Proxy Support + +All image generation tools support proxy configuration through the `PROXY` environment variable: + +```bash +PROXY=http://proxy-url:port +``` + +## Error Handling +If any of the tools encounter an error, they will return an error message explaining what went wrong. Common issues include: +- Invalid API key +- API unavailability +- Content policy violations +- Proxy/network issues +- Invalid parameters +- Unsupported image payload (see [Image Storage and Handling](#image-storage-and-handling) above) + +--- + +## Prompting + +Though you can customize the prompts for [OpenAI Image Tools](#advanced-configuration) and [DALL·E](#advanced-configuration-1), the following tips inform the default prompts supplied by the tools, which is helpful to know for your own writing/prompting. + +1. Start with the **subject** and **style** (photo, oil painting, etc.). +2. Add **composition** and **camera / medium** ("wide-angle shot of…", "watercolour…"). +3. Mention **lighting & mood** ("golden hour", "dramatic shadows"). +4. Finish with **detail keywords** (textures, colours, expressions). +5. Keep negatives positive—describe what should be included, not what to avoid. + +Example: + +> A cinematic photo of an antique library bathed in warm afternoon sunlight. Tall wooden shelves overflow with leather-bound books, and dust particles shimmer in the light. A single green-shaded banker's lamp illuminates an open atlas on a polished mahogany desk in the foreground. 85 mm lens, shallow depth of field, rich amber tones, ultra-high detail. diff --git a/content/docs-archive/v0.8.3/features/import_convos.mdx b/content/docs-archive/v0.8.3/features/import_convos.mdx new file mode 100644 index 000000000..4a855f2f0 --- /dev/null +++ b/content/docs-archive/v0.8.3/features/import_convos.mdx @@ -0,0 +1,31 @@ +--- +title: Import Conversations +icon: Import +description: Conversations Import allows user to import conversations exported from other GPT chat applications. Currently, we support importing conversations from ChatGPT, ChatbotUI v1, and LibreChat itself. +--- + +Conversations Import allows user to import conversations exported from other GPT chat applications. Currently, we support importing conversations from [ChatGPT](https://chatgpt.com/), [ChatbotUI v1](https://github.com/mckaywrigley/chatbot-ui/tree/b865b0555f53957e96727bc0bbb369c9eaecd83b?tab=readme-ov-file#legacy-code), and LibreChat itself. + +The Import functionality is available in the "Settings" -> "Data Controls" section. + +## How to import conversations from Chat GPT + +1. Follow the [ChatGPT export instructions](https://help.openai.com/en/articles/7260999-how-do-i-export-my-chatgpt-history-and-data) to export your conversations. +2. You should get a link to download archive in you email. +3. Download the archive. It should be a zip file with random name like: _d119d98bb3711aff7a2c73bcc7ea53d96c984650d8f7e033faef78386a9907-2024-01-01-10-30-00.zip_ +4. Extract the content of the zip file. +5. Navigate to LibreChat Settings -> Data Controls +
+
+6. Click on the "Import" button and select `conversations.json` file from the extracted archive. It will start importing the conversations.
+7. Shortly you will get a notification that the import is complete.
+
+ 
+
+
+
+ 
+
+
+ 
+
diff --git a/content/docs-archive/v0.8.3/features/index.mdx b/content/docs-archive/v0.8.3/features/index.mdx
new file mode 100644
index 000000000..57c3f4b25
--- /dev/null
+++ b/content/docs-archive/v0.8.3/features/index.mdx
@@ -0,0 +1,7 @@
+---
+title: Overview
+icon: BookOpen
+description: Explore the features of LibreChat, including agents, MCP integration, code execution, multimodal chat, and more.
+---
+
+
+
+
+
+## Overview
+
+This feature enables email-based password reset functionality for your LibreChat server. You can configure it to work with various email services, including Mailgun API, Gmail, and custom mail servers.
+
+## Key Features
+
+- Supports multiple email services:
+ - **Mailgun API** - Recommended for servers that block SMTP ports
+ - **Gmail** and other predefined SMTP services
+ - **Custom mail servers** with advanced SMTP configuration
+- Allows for basic and advanced configuration options
+- Enables secure email-based password reset functionality for your LibreChat server
+
+## Setup Options
+
+- **Mailgun Configuration**: Use Mailgun's API for reliable email delivery, especially useful when SMTP ports are blocked
+- **Basic SMTP Configuration**: Use predefined services like Gmail with minimal configuration
+- **Advanced SMTP Configuration**: Configure generic SMTP services or customize settings for any mail provider
+
+**For detailed setup instructions, refer to the configuration guide: [Email Setup](/v0.8.3/docs/configuration/authentication/email)**
diff --git a/content/docs-archive/v0.8.3/features/rag_api.mdx b/content/docs-archive/v0.8.3/features/rag_api.mdx
new file mode 100644
index 000000000..c2fc0a967
--- /dev/null
+++ b/content/docs-archive/v0.8.3/features/rag_api.mdx
@@ -0,0 +1,70 @@
+---
+title: RAG API (Chat with Files)
+icon: Brain
+description: Retrieval-Augmented Generation (RAG) API for document indexing and retrieval using Langchain and FastAPI. This API integrates with LibreChat to provide context-aware responses based on user-uploaded files.
+---
+
+The **RAG (Retrieval-Augmented Generation) API** is a powerful tool that integrates with LibreChat to provide context-aware responses based on user-uploaded files.
+
+It leverages LangChain, PostgresQL + PGVector, and Python FastAPI to index and retrieve relevant documents, enhancing the conversational experience.
+
+**For further details, refer to the configuration guide provided here: [RAG API Configuration](/v0.8.3/docs/configuration/rag_api)**
+
+
+
+---
+
+**Currently, this feature is available through [Agents](/v0.8.3/docs/features/agents), as well as through Custom Endpoints, OpenAI, Azure OpenAI, Anthropic, and Google.**
+
+OpenAI Assistants have their own implementation of RAG through the "Retrieval" capability. Learn more about it [here.](https://platform.openai.com/docs/assistants/tools/knowledge-retrieval)
+
+It will still be useful to implement usage of the RAG API with the Assistants API since OpenAI charges for both file storage, and use of "Retrieval," and will be introduced in a future update.
+
+**Still confused about RAG?** [Read the section I wrote below](#what-is-rag) explaining the general concept in more detail with a link to a helpful video.
+
+## What is RAG?
+
+RAG, or Retrieval-Augmented Generation, is an AI framework designed to improve the quality and accuracy of responses generated by large language models (LLMs). It achieves this by grounding the LLM on external sources of knowledge, supplementing the model's internal representation of information.
+
+
+## Features
+
+- **Document Indexing**: The RAG API indexes user-uploaded files, creating embeddings for efficient retrieval.
+- **Semantic Search**: It performs semantic search over the indexed documents to find the most relevant information based on the user's input.
+- **Context-Aware Responses**: By augmenting the user's prompt with retrieved information, the API enables LibreChat to generate more accurate and contextually relevant responses.
+- **Asynchronous Processing**: The API supports asynchronous operations for improved performance and scalability.
+- **Flexible Configuration**: It allows customization of various parameters such as chunk size, overlap, and embedding models.
+
+### Key Benefits of RAG
+
+1. **Access to up-to-date and reliable facts**: RAG ensures that the LLM has access to the most current and reliable information by retrieving relevant facts from an external knowledge base.
+2. **Transparency and trust**: Users can access the model's sources, allowing them to verify the accuracy of the generated responses and build trust in the system.
+3. **Reduced data leakage and hallucinations**: By grounding the LLM on a set of external, verifiable facts, RAG reduces the chances of the model leaking sensitive data or generating incorrect or misleading information.
+4. **Lower computational and financial costs**: RAG reduces the need for continuous training and updating of the model's parameters, potentially lowering the computational and financial costs of running LLM-powered chatbots in an enterprise setting.
+
+### How RAG Works
+
+RAG consists of two main phases: retrieval and content generation.
+
+1. **Retrieval Phase**: Algorithms search for and retrieve snippets of information relevant to the user's prompt or question from an external knowledge base. In an open-domain, consumer setting, these facts can come from indexed documents on the internet. In a closed-domain, enterprise setting, a narrower set of sources are typically used for added security and reliability.
+2. **Generative Phase**: The retrieved external knowledge is appended to the user's prompt and passed to the LLM. The LLM then draws from the augmented prompt and its internal representation of its training data to synthesize a tailored, engaging answer for the user. The answer can be passed to a chatbot with links to its sources.
+
+### Challenges and Ongoing Research
+
+While RAG is currently one of the best-known tools for grounding LLMs on the latest, verifiable information and lowering the costs of constant retraining and updating, it's not perfect. Some challenges include:
+
+1. **Recognizing unanswerable questions**: LLMs need to be explicitly trained to recognize questions they can't answer based on the available information. This may require fine-tuning on thousands of examples of answerable and unanswerable questions.
+2. **Improving retrieval and generation**: Ongoing research focuses on innovating at both ends of the RAG process: improving the retrieval of the most relevant information possible to feed the LLM, and optimizing the structure of that information to obtain the richest responses from the LLM.
+
+In summary, RAG is a powerful framework that enhances the capabilities of LLMs by grounding them on external, verifiable knowledge. It helps to ensure more accurate, up-to-date, and trustworthy responses while reducing the costs associated with continuous model retraining. As research in this area progresses, we can expect further improvements in the quality and efficiency of LLM-powered conversational AI systems.
+
+For a more detailed explanation of RAG, you can watch this informative video by IBM on Youtube:
+
+
+
+
+## Conclusion
+
+The RAG API is a powerful addition to LibreChat, enabling context-aware responses based on user-uploaded files. By leveraging Langchain and FastAPI, it provides efficient document indexing, retrieval, and generation capabilities. With its flexible configuration options and seamless integration, the RAG API enhances the conversational experience in LibreChat.
+
+For more detailed information on the RAG API, including API endpoints, request/response formats, and advanced configuration, please refer to the official RAG API documentation.
diff --git a/content/docs-archive/v0.8.3/features/resumable_streams.mdx b/content/docs-archive/v0.8.3/features/resumable_streams.mdx
new file mode 100644
index 000000000..7fdccc427
--- /dev/null
+++ b/content/docs-archive/v0.8.3/features/resumable_streams.mdx
@@ -0,0 +1,176 @@
+---
+title: Resumable Streams
+icon: Zap
+description: Never lose an AI response—seamless reconnection, multi-tab sync, and horizontal scaling for production deployments
+---
+
+LibreChat features a resilient streaming architecture that ensures you never lose AI-generated content. Whether your connection drops, you switch tabs, or you pick up on another device, your responses are always preserved and synchronized.
+
+## Why It Matters
+
+Traditional chat applications lose all streaming content when your connection drops. With resumable streams, LibreChat:
+
+- **Preserves every response** — Network hiccups, browser refreshes, or server restarts won't cause data loss
+- **Keeps multiple tabs in sync** — Open the same conversation in two browser tabs and watch them update together in real-time
+- **Enables seamless device switching** — Start a conversation on your desktop and continue on your phone
+- **Lets you multitask freely** — Start a generation, browse other tabs, and come back to a complete response
+
+## How It Works
+
+When you send a message to an AI model, LibreChat creates a generation job that tracks all streamed content. The magic happens when something interrupts your connection:
+
+1. **Automatic detection** — The client detects the disconnection instantly
+2. **State reconstruction** — Upon reconnecting, the server rebuilds all previously streamed content
+3. **Seamless sync** — Missing content is delivered via a sync event
+4. **Transparent continuation** — Streaming resumes from the current position
+
+This all happens automatically—no user action required.
+
+### Multi-Tab & Multi-Device Experience
+
+One of the most powerful aspects of resumable streams is **real-time synchronization**:
+
+- **Same chat, multiple windows** — Open a conversation in two browser tabs and both receive updates simultaneously
+- **Cross-device continuity** — Start a long generation on your laptop, then check the result on your phone
+- **Team collaboration** — In shared conversations, all viewers see content appear in real-time
+
+## Deployment Modes
+
+LibreChat supports two deployment configurations:
+
+### Single-Instance Mode (Default)
+
+Uses in-memory storage with Node.js `EventEmitter` for pub/sub. Perfect for:
+- Local development
+- Single-server deployments
+- Docker Compose setups
+
+**No configuration required** — Works out of the box.
+
+### Redis Mode (Production)
+
+Uses Redis Streams and Pub/Sub for cross-instance communication. Essential for:
+- Horizontally scaled deployments
+- Load-balanced production environments
+- High-availability setups
+- Kubernetes clusters
+
+With Redis mode, a user can start a generation on one server instance and seamlessly resume on another—perfect for rolling deployments and auto-scaling.
+
+**Note:** If you only run a single LibreChat instance, Redis for resumable streams is typically unnecessary—the in-memory mode handles everything. Redis becomes valuable when you have multiple LibreChat instances behind a load balancer. That said, Redis is still useful for other features like caching and session storage even in single-instance deployments.
+
+## Configuration
+
+### Enabling Redis Streams
+
+When Redis is enabled (`USE_REDIS=true`), resumable streams automatically use Redis. You can also explicitly enable it:
+
+```bash filename=".env"
+USE_REDIS=true
+REDIS_URI=redis://localhost:6379
+# Resumable streams will use Redis automatically when USE_REDIS=true
+# To explicitly control it:
+USE_REDIS_STREAMS=true
+```
+
+### Redis Cluster Support
+
+For Redis Cluster deployments:
+
+```bash filename=".env"
+USE_REDIS_STREAMS=true
+USE_REDIS_CLUSTER=true
+REDIS_URI=redis://node1:7001,redis://node2:7002,redis://node3:7003
+```
+
+LibreChat automatically uses hash-tagged keys to ensure multi-key operations stay within the same cluster slot.
+
+## Use Cases
+
+### Unstable Networks
+On spotty WiFi or cellular connections, responses automatically resume when connectivity returns. No need to re-send your prompt.
+
+### Mobile Users
+Switch from WiFi to cellular (or vice versa) without losing your response. The stream picks up exactly where it left off.
+
+### Long-Running Generations
+For complex prompts that generate lengthy responses, feel free to check other tabs or apps. Your response will be waiting when you return.
+
+### Multi-Device Workflows
+Start a conversation on your work computer, commute home, and check the result on your phone—the full response is there.
+
+### Production Deployments
+Scale horizontally across multiple server instances while maintaining stream continuity. Rolling deployments won't interrupt active generations.
+
+## Technical Details
+
+### Content Reconstruction
+
+The system aggregates all streamed delta events to rebuild:
+- Message content (text, tool calls, citations)
+- Agent run steps and intermediate reasoning
+- Metadata and state information
+
+### Performance Optimizations
+
+**Memory-first approach**: When reconnecting to the same server instance, LibreChat uses local cache for zero-latency content recovery, avoiding unnecessary Redis round trips.
+
+**Automatic cleanup**: Stale job entries are removed during queries to prevent memory leaks. Completed streams expire automatically.
+
+**Efficient storage**: In-memory mode uses `WeakRef` for graph storage, enabling automatic garbage collection when conversations end.
+
+### Data Flow
+
+| Component | Storage Mechanism |
+|-----------|-------------------|
+| Chunks | Redis Streams (`XADD`/`XRANGE`) |
+| Job metadata | Redis Hash structures |
+| Real-time events | Redis Pub/Sub channels |
+| Expiration | Automatic TTL after stream completion |
+
+## Testing Resumable Streams
+
+You can verify the feature is working:
+
+1. Start a streaming conversation with any AI model
+2. **Tab test**: Open the same chat in a new browser tab—both should sync
+3. **Disconnect test**: Turn off your network briefly, then reconnect
+4. **Navigation test**: Navigate away mid-stream, then return
+
+In all cases, you should see the complete response with no data loss.
+
+## Troubleshooting
+
+### Streams not resuming?
+
+**Check Redis connectivity:**
+```bash
+docker exec -it librechat-redis redis-cli ping
+# Should return: PONG
+```
+
+**Verify environment variables:**
+```bash
+# Ensure USE_REDIS_STREAMS is set
+echo $USE_REDIS_STREAMS
+```
+
+### Content appears duplicated?
+
+This typically indicates a client version mismatch. Ensure you're running the latest version of LibreChat.
+
+### High memory usage in single-instance mode?
+
+Completed streams are automatically garbage collected. If you're seeing high memory usage, check for:
+- Very long-running streams that haven't completed
+- Streams that errored without proper cleanup
+
+## Related Documentation
+
+- [Redis Configuration](/v0.8.3/docs/configuration/redis) — Setting up Redis for caching and horizontal scaling
+- [Agents](/v0.8.3/docs/features/agents) — AI agents with tool use capabilities
+- [Docker Deployment](/v0.8.3/docs/local/docker) — Container-based deployment guide
+
+---
+
+For implementation details, see [PR #10926](https://github.com/danny-avila/LibreChat/pull/10926).
diff --git a/content/docs-archive/v0.8.3/features/search.mdx b/content/docs-archive/v0.8.3/features/search.mdx
new file mode 100644
index 000000000..088ba6e0e
--- /dev/null
+++ b/content/docs-archive/v0.8.3/features/search.mdx
@@ -0,0 +1,19 @@
+---
+title: Message Search
+icon: ListFilter
+description: Quickly search in past conversations with LibreChat's integrated Meilisearch
+---
+
+LibreChat has integrated **Meilisearch** to enhance the user experience by providing a fast and efficient way to search through past conversations. Meilisearch is a powerful, open-source search engine that is known for its speed and ease of use, making it an excellent choice for applications like LibreChat that require quick access to a large volume of data.
+
+
+
+
+
+
+The integration allows users to:
+- Perform **full-text searches** on their conversation history.
+- Utilize **typo-tolerance** for more forgiving search queries.
+- Experience **instant results** as they type, thanks to Meilisearch's as-you-type search capabilities.
+
+This feature significantly improves the functionality of LibreChat, making it easier for users to find specific messages or topics within their chat history. It's a testament to the platform's commitment to providing a seamless and user-friendly experience. For those interested in the technical details or implementation, further information can be found in the [Meilisearch Configuration Guide](/v0.8.3/docs/configuration/meilisearch).
diff --git a/content/docs-archive/v0.8.3/features/shareable_links.mdx b/content/docs-archive/v0.8.3/features/shareable_links.mdx
new file mode 100644
index 000000000..2d98245b5
--- /dev/null
+++ b/content/docs-archive/v0.8.3/features/shareable_links.mdx
@@ -0,0 +1,185 @@
+---
+title: Shareable Links
+icon: Share2
+description: Share your conversations with others using LibreChat's shareable links feature, complete with QR codes, branching messages, and artifacts support.
+---
+
+import Image from 'next/image'
+
+## Overview
+
+Shareable Links in LibreChat allow you to share your conversations with others through automatically generated links and QR codes. Whether you're collaborating with teammates, showcasing AI interactions, or sharing generated artifacts, this feature makes it easy to allow others to view your conversations with the click of a button.
+
+## Key Features
+
+- **Easy Sharing**: Generate shareable links with just a few clicks
+- **QR Code Generation**: Quickly share conversations via QR codes for mobile access
+- **Conversation Branching**: Recipients can see branched conversations in your shared links
+- **Artifacts Support**: Shared conversations now include generated artifacts and interactive components
+- **Customizable Appearance**: Recipients can adjust language and theme preferences
+- **Link Management**: Centralized dashboard to manage all your shared links
+
+## How to Share a Conversation
+There are two ways to make a conversation shareable:
+
+### Option 1: From the Conversation Menu
+
+
+*Access the share option from the conversation menu*
+
+### Option 2: From the Share Button
+
+
+*Use the dedicated share button in your active conversation*
+
+## Share Link Options
+
+When you create a shareable link, you'll see a modal with several options to customize how your conversation appears to recipients.
+
+
+
+
+### Available Options:
+
+- **Refresh Link**: Generate a new URL for the shared conversation
+- **Generate QR code**: Create and show a QR code for easy mobile access
+- **Copy Link to clipboard**: Copy the shareable URL to your clipboard
+- **Delete Link**: Remove the shared link, revoking access to anyone who has it
+
+## QR Code Feature
+
+Generate QR codes for your shared conversations for easy mobile sharing. Simply scan the code with any smartphone camera to instantly access the conversation.
+
+
+ 
+ *Initial share link creation modal*
+
+
+ 
+ *Shared link configuration modal*
+
+
+
+
+This is particularly useful for:
+- Sharing during presentations
+- Quick mobile access
+- Offline sharing via printed materials
+- Conference or event demonstrations
+
+## Viewing Shared Conversations
+
+When someone opens your shared link, they'll see a clean, focused view of the conversation with all the context you chose to include.
+
+
+*How recipients see your shared conversation*
+
+### Features Available to Recipients:
+
+- The date the shareable link was published
+- Ability to scroll through the entire conversation
+- Access to any included artifacts or generated content
+
+## Branching in Shared Conversations
+
+Conversation branches are preserved in shared links, allowing recipients to explore different conversation paths and see how the discussion evolved.
+
+
+ 
+ *Generate QR codes for instant mobile access to shared conversations*
+
+
+ 
+ *QR code will link to the shared conversation URL*
+
+
+
+
+This feature is essential for:
+- Demonstrating different AI approaches to the same problem
+- Illustrating how solutions and interactions can take multiple different paths depending on user input
+
+## Artifacts in Shared Conversations
+
+All artifacts generated during the conversation are fully functional in shared links, including React components, HTML code, and Mermaid diagrams.
+
+
+*Generated artifacts remain interactive in shared conversations*
+
+Recipients can:
+- View interactive React components
+- See HTML previews
+- Examine Mermaid diagrams
+- Access the underlying code
+- Understand the context in which artifacts were generated
+
+## Customization Options for Recipients
+
+Recipients can customize their viewing experience by adjusting language and theme preferences to match their preferences.
+
+
+*Recipients can customize language and theme preferences*
+
+Available customizations:
+- **Theme selection**: Light, dark, or system preference
+- **Language**: View the interface in their preferred language
+
+## Managing Your Shared Links
+
+Access the Shared Links Management dashboard under the Data Controls section of the Settings menu to view and manage all your shared conversations in one place.
+
+
+ 
+ *Access different conversation branches using the branch navigation arrows*
+
+
+ 
+ *Recipients can navigate through conversation branches in shared links*
+
+
+
+
+### Management Features:
+
+- **View all links**: See a list of all conversations you've shared
+- **Search & filter**: Quickly find and view the content of specific shared links
+- **Revoke access**: Delete links to immediately stop sharing
+
+## Configuration
+
+Shareable links behavior is controlled by the following environment variables in your `.env` file:
+
+- **`ALLOW_SHARED_LINKS`** (default: `true`) — Enables or disables the shared links feature entirely. Set to `false` to prevent users from creating shared links.
+- **`ALLOW_SHARED_LINKS_PUBLIC`** (default: `false`) — Controls whether shared links can be accessed without authentication. By default, recipients must be logged in to view shared conversations. Set to `true` to allow public (unauthenticated) access.
+
+```bash
+# Enable shared links (default)
+ALLOW_SHARED_LINKS=true
+
+# Require authentication to view shared links (default)
+ALLOW_SHARED_LINKS_PUBLIC=false
+```
+
+> **Note:** For full environment variable reference, see the [.env Configuration](/v0.8.3/docs/configuration/dotenv#shared-links) page.
+
+## Frequently Asked Questions
+
+**Q: Can recipients respond to shared conversations?**
+A: No, shared links are read-only. Recipients can view the conversation but cannot add messages or interact with the AI.
+
+**Q: What happens if I delete a conversation after sharing it?**
+A: The shared link will no longer be accessible, and any user which navigates to that link will be served a page stating "Shared link not found".
+
+**Q: Can I edit a conversation after sharing it?**
+A: The shared link captures the conversation at the time of creation. Additional messages will not be reflected in the shared view - however, edits made to the existing messages will be shown.
+
+**Q: Do shared links work offline?**
+A: No, recipients need an internet connection to view shared conversations.
\ No newline at end of file
diff --git a/content/docs-archive/v0.8.3/features/temporary_chat.mdx b/content/docs-archive/v0.8.3/features/temporary_chat.mdx
new file mode 100644
index 000000000..aea135218
--- /dev/null
+++ b/content/docs-archive/v0.8.3/features/temporary_chat.mdx
@@ -0,0 +1,26 @@
+---
+title: Temporary Chat
+icon: Clock
+description: Temporary chats allow users to exclude specific conversations from their chat history, search results, and bookmarks, providing a private and focused experience.
+---
+
+Keep your chat history clean and focused by using temporary chats for sensitive topics, quick experiments, or anything you don't need to permanently save. These chats are excluded from search results, cannot be bookmarked, and are automatically deleted after 30 days.
+
+## Activating Temporary Chat
+
+1. Open the model list dropdown menu located on the top left side of LibreChat.
+2. Toggle the "Temporary Chat" slider to the ON position.
+
+
+
+3. A notification will appear above the chat input area, confirming that Temporary Chat mode is active. Pressing (x) will disable the Temporary Chat.
+
+
+
+
+## What Happens When a Chat is Marked as Temporary?
+
+* Temporary Chats do not appear in the chat history sidebar.
+* Temporary Chats are excluded from search results.
+* Temporary Chats cannot be bookmarked.
+* Temporary Chats are stored in the database for 30 days and then automatically deleted.
diff --git a/content/docs-archive/v0.8.3/features/upload_as_text.mdx b/content/docs-archive/v0.8.3/features/upload_as_text.mdx
new file mode 100644
index 000000000..c0b909b83
--- /dev/null
+++ b/content/docs-archive/v0.8.3/features/upload_as_text.mdx
@@ -0,0 +1,321 @@
+---
+title: Upload Files as Text
+icon: Upload
+description: Upload files to include their full content in conversations without requiring OCR configuration.
+---
+
+Upload as Text allows you to upload documents and have their full content included directly in your conversation with the AI. This feature works out-of-the-box using text parsing methods, with optional OCR enhancement for improved extraction quality.
+
+## Overview
+
+- **No OCR required** - Uses text parsing with fallback methods by default
+- **Enhanced by OCR** - If OCR is configured, extraction quality improves for images and scanned documents
+- **Full document content** - Entire file content available to the model in the conversation
+- **Works with all models** - No special tool capabilities needed
+- **Token limit control** - Configurable via `fileTokenLimit` to manage context usage
+
+## The `context` Capability
+
+Upload as Text is controlled by the `context` capability in your LibreChat configuration.
+
+```yaml
+# librechat.yaml
+endpoints:
+ agents:
+ capabilities:
+ - "context" # Enables "Upload as Text"
+```
+
+**Default:** The `context` capability is included by default. You only need to explicitly add it if you've customized the capabilities list.
+
+## How It Works
+
+When you upload a file using "Upload as Text":
+
+1. LibreChat checks the file MIME type against `fileConfig` patterns
+2. **Processing method determined by precedence: OCR > STT > text parsing**
+3. If file matches `fileConfig.ocr.supportedMimeTypes` AND OCR is configured: **Use OCR**
+4. If file matches `fileConfig.stt.supportedMimeTypes` AND STT is configured: **Use STT**
+5. If file matches `fileConfig.text.supportedMimeTypes`: **Use text parsing**
+6. Otherwise: **Fallback to text parsing**
+7. Text is truncated to `fileConfig.fileTokenLimit` before prompt construction
+8. Full extracted text included in conversation context
+
+### Text Processing Methods
+
+**Text Parsing (Default):**
+- Uses a robust parsing library (same as the RAG API)
+- Handles PDFs, Word docs, text files, code files, and more
+- No external service required
+- Works immediately without configuration
+- Fallback method if no other match
+
+**OCR Enhancement (Optional):**
+- Improves extraction from images, scanned documents, and complex PDFs
+- Requires OCR service configuration
+- Automatically used for files matching `fileConfig.ocr.supportedMimeTypes` when available
+- See [OCR Configuration](/v0.8.3/docs/features/ocr)
+
+**STT Processing (Optional):**
+- Converts audio files to text
+- Requires STT service configuration
+- See [Speech-to-Text Configuration](/v0.8.3/docs/configuration/librechat_yaml/object_structure/file_config#stt)
+
+## Usage
+
+1. Click the attachment icon in the chat input
+2. Select "Upload as Text" from the menu
+3. Choose your file
+4. File content is extracted and included in your message
+
+**Note:** If you don't see "Upload as Text", ensure the `context` capability is enabled in your [`endpoints.agents.capabilities` configuration](/v0.8.3/docs/configuration/librechat_yaml/object_structure/agents#capabilities).
+
+## Configuration
+
+### Basic Configuration
+
+The `context` capability is enabled by default. No additional configuration is required for basic text parsing functionality.
+
+### File Handling Configuration
+
+Control text processing behavior with `fileConfig`:
+
+```yaml
+fileConfig:
+ # Maximum tokens from text files before truncation
+ fileTokenLimit: 100000
+
+ # Files matching these patterns use OCR (if configured)
+ ocr:
+ supportedMimeTypes:
+ - "^image/(jpeg|gif|png|webp|heic|heif)$"
+ - "^application/pdf$"
+ - "^application/vnd\\.openxmlformats-officedocument\\.(wordprocessingml\\.document|presentationml\\.presentation|spreadsheetml\\.sheet)$"
+ - "^application/vnd\\.ms-(word|powerpoint|excel)$"
+ - "^application/epub\\+zip$"
+
+ # Files matching these patterns use text parsing
+ text:
+ supportedMimeTypes:
+ - "^text/(plain|markdown|csv|json|xml|html|css|javascript|typescript|x-python|x-java|x-csharp|x-php|x-ruby|x-go|x-rust|x-kotlin|x-swift|x-scala|x-perl|x-lua|x-shell|x-sql|x-yaml|x-toml)$"
+
+ # Files matching these patterns use STT (if configured)
+ stt:
+ supportedMimeTypes:
+ - "^audio/(mp3|mpeg|mpeg3|wav|wave|x-wav|ogg|vorbis|mp4|x-m4a|flac|x-flac|webm)$"
+```
+
+**Processing Priority:** OCR > STT > text parsing > fallback
+
+For more details, see [File Config Object Structure](/v0.8.3/docs/configuration/librechat_yaml/object_structure/file_config).
+
+### Optional: Configure OCR for Enhanced Extraction
+
+OCR is **not required** but enhances extraction quality when configured:
+
+```yaml
+# librechat.yaml
+ocr:
+ strategy: "mistral_ocr"
+ apiKey: "${OCR_API_KEY}"
+ baseURL: "https://api.mistral.ai/v1"
+ mistralModel: "mistral-ocr-latest"
+```
+
+See [OCR Configuration](/v0.8.3/docs/features/ocr) for full details.
+
+## When to Use Each Upload Option
+
+LibreChat offers three different ways to upload files, each suited for different use cases:
+
+### Use "Upload as Text" when:
+- ✅ You want the AI to read the complete document content
+- ✅ Working with smaller files that fit in context
+- ✅ You need "chat with files" functionality
+- ✅ Using models without tool capabilities
+- ✅ You want direct content access without semantic search
+
+### Use "Upload for File Search" when:
+- ✅ Working with large documents or multiple files
+- ✅ You want to optimize token usage
+- ✅ You need semantic search for relevant sections
+- ✅ Building knowledge bases
+- ✅ The `file_search` capability is enabled and toggled ON
+
+### Use standard "Upload Files" when:
+- ✅ Using vision models to analyze images
+- ✅ Using code interpreter to execute code
+- ✅ Files don't need text extraction
+
+## Supported File Types
+
+### Text Files (text parsing)
+- Plain text, Markdown, CSV, JSON, XML, HTML
+- Programming languages (Python, JavaScript, Java, C++, etc.)
+- Configuration files (YAML, TOML, INI, etc.)
+- Shell scripts, SQL files
+
+### Documents (text parsing or OCR)
+- PDF documents
+- Word documents (.docx, .doc)
+- PowerPoint presentations (.pptx, .ppt)
+- Excel spreadsheets (.xlsx, .xls)
+- EPUB books
+
+### Images (OCR if configured)
+- JPEG, PNG, GIF, WebP
+- HEIC, HEIF (Apple formats)
+- Screenshots, photos of documents, scanned images
+
+### Audio (STT if configured)
+- MP3, WAV, OGG, FLAC
+- M4A, WebM
+- Voice recordings, podcasts
+
+## File Processing Priority
+
+LibreChat processes files based on MIME type matching with the following **priority order**:
+
+1. **OCR** - If file matches `ocr.supportedMimeTypes` AND OCR is configured
+2. **STT** - If file matches `stt.supportedMimeTypes` AND STT is configured
+3. **Text Parsing** - If file matches `text.supportedMimeTypes`
+4. **Fallback** - Text parsing as last resort
+
+### Processing Examples
+
+**PDF file with OCR configured:**
+- Matches `ocr.supportedMimeTypes`
+- **Uses OCR** to extract text
+- Better quality for scanned PDFs
+
+**PDF file without OCR configured:**
+- Matches `text.supportedMimeTypes` (fallback)
+- **Uses text parsing** library
+- Works well for digital PDFs
+
+**Python file:**
+- Matches `text.supportedMimeTypes`
+- **Uses text parsing** (no OCR needed)
+- Direct text extraction
+
+**Audio file with STT configured:**
+- Matches `stt.supportedMimeTypes`
+- **Uses STT** to transcribe
+
+## Token Limits
+
+Files are truncated to `fileTokenLimit` tokens to manage context window usage:
+
+```yaml
+fileConfig:
+ fileTokenLimit: 100000 # Default: 100,000 tokens
+```
+
+- Truncation happens at runtime before prompt construction
+- Helps prevent exceeding model context limits
+- Configurable based on your needs and model capabilities
+- Larger limits allow more content but use more tokens
+
+## Comparison with Other File Features
+
+| Feature | Capability | Requires Service | Persistence | Best For |
+|---------|-----------|------------------|-------------|----------|
+| **Upload as Text** | `context` | No (enhanced by OCR) | Single conversation | Temporary document questions |
+| **Agent File Context** | `context` | No (enhanced by OCR) | Agent system instructions | Specialized agent knowledge |
+| **File Search** | `file_search` | Yes (vector DB) | Stored in vector store | Large documents, semantic search |
+
+### Upload as Text vs Agent File Context
+
+**Upload as Text (`context`):**
+- Available in any chat conversation
+- Content included in current conversation only
+- No OCR service required (text parsing by default)
+- Best for one-off document questions
+
+**Agent File Context (`context`):**
+- Only available in Agent Builder
+- Content stored in agent's system instructions
+- No OCR service required (text parsing by default)
+- Best for creating specialized agents with persistent knowledge
+- See [OCR for Documents](/v0.8.3/docs/features/ocr)
+
+### Upload as Text vs File Search
+
+**Upload as Text (`context`):**
+- Full document content in conversation context
+- Direct access to all text
+- Token usage: entire file (up to limit)
+- Works without RAG API configuration
+
+**File Search (`file_search`):**
+- Semantic search over documents
+- Returns relevant chunks via tool use
+- Token usage: only relevant sections
+- Requires RAG API and vector store configuration
+- See [RAG API](/v0.8.3/docs/features/rag_api)
+
+## Example Use Cases
+
+- **Document Analysis**: Upload contracts, reports, or articles for analysis
+- **Code Review**: Upload source files for review and suggestions
+- **Data Extraction**: Extract information from structured documents
+- **Translation**: Translate document contents
+- **Summarization**: Summarize articles, papers, or reports
+- **Research**: Discuss academic papers or technical documentation
+- **Troubleshooting**: Share log files for analysis
+- **Content Editing**: Review and edit written content
+- **Data Processing**: Work with CSV or JSON data files
+
+## Troubleshooting
+
+### "Upload as Text" option not appearing
+
+**Solution:** Ensure the `context` capability is enabled:
+
+```yaml
+endpoints:
+ agents:
+ capabilities:
+ - "context" # Add this if missing
+```
+
+### File content not extracted properly
+
+**Solutions:**
+1. Check if file type is supported (matches `fileConfig` patterns)
+2. For images/scanned documents: Configure OCR for better extraction
+3. For audio files: Configure STT service
+4. Verify file is not corrupted
+
+### Content seems truncated
+
+**Solution:** Increase the token limit:
+
+```yaml
+fileConfig:
+ fileTokenLimit: 150000 # Increase as needed
+```
+
+### Poor extraction quality from images
+
+**Solution:** Configure OCR to enhance extraction:
+
+```yaml
+ocr:
+ strategy: "mistral_ocr"
+ apiKey: "${OCR_API_KEY}"
+```
+
+See [OCR Configuration](/v0.8.3/docs/configuration/librechat_yaml/object_structure/ocr) for details.
+
+## Related Features
+
+- [File Context](/v0.8.3/docs/features/agents#file-context) - Files used as Agent Context
+- [OCR for Documents](/v0.8.3/docs/features/ocr) - Learn about and configure OCR services
+- [File Configuration](/v0.8.3/docs/configuration/librechat_yaml/object_structure/file_config) - Configure file handling
+
+---
+
+Upload as Text provides a simple, powerful way to work with documents in LibreChat without requiring complex configuration or external services.
+
+
diff --git a/content/docs-archive/v0.8.3/features/url_query.mdx b/content/docs-archive/v0.8.3/features/url_query.mdx
new file mode 100644
index 000000000..cec73f753
--- /dev/null
+++ b/content/docs-archive/v0.8.3/features/url_query.mdx
@@ -0,0 +1,255 @@
+---
+title: Query Parameters
+icon: Link
+description: Learn how to configure chat conversations using URL query parameters in LibreChat. Set models, endpoints, and conversation settings dynamically.
+---
+
+LibreChat supports dynamic configuration of chat conversations through URL query parameters. This feature allows you to initiate conversations with specific settings, models, and endpoints directly from the URL.
+
+### Chat Paths
+
+Query parameters must follow a valid chat path:
+- For new conversations: `/c/new?`
+- For existing conversations: `/c/[conversation-id]?` (where conversation-id is an existing one)
+
+Examples:
+
+```bash
+https://your-domain.com/c/new?endpoint=ollama&model=llama3%3Alatest
+https://your-domain.com/c/03debefd-6a50-438a-904d-1a806f82aad4?endpoint=openAI&model=o1-mini
+```
+
+## Basic Usage
+
+The most common parameters to use are `endpoint` and `model`. Using both is recommended for the most predictable behavior:
+
+```bash
+https://your-domain.com/c/new?endpoint=azureOpenAI&model=o1-mini
+```
+
+### URL Encoding
+
+Special characters in query params must be properly URL-encoded to work correctly. Common characters that need encoding:
+
+- `:` → `%3A`
+- `/` → `%2F`
+- `?` → `%3F`
+- `#` → `%23`
+- `&` → `%26`
+- `=` → `%3D`
+- `+` → `%2B`
+- Space → `%20` (or `+`)
+
+Example with special characters:
+```ts
+Original: `Write a function: def hello()`
+Encoded: `/c/new?prompt=Write%20a%20function%3A%20def%20hello()`
+```
+
+You can use JavaScript's built-in `encodeURIComponent()` function to properly encode prompts:
+```javascript
+const prompt = "Write a function: def hello()";
+const encodedPrompt = encodeURIComponent(prompt);
+const url = `/c/new?prompt=${encodedPrompt}`;
+console.log(url);
+```
+
+Try running the code in your browser console to see the encoded URL (browser shortcut: `Ctrl+Shift+I`).
+
+### Endpoint Selection
+
+The `endpoint` parameter can be used alone:
+```bash
+https://your-domain.com/c/new?endpoint=google
+```
+
+When only `endpoint` is specified:
+- It will use the last selected model from localStorage
+- If no previous model exists, it will use the first available model in the endpoint's model list
+
+#### Notes
+
+- The `endpoint` value must be one of the following:
+```bash
+openAI, azureOpenAI, google, anthropic, assistants, azureAssistants, bedrock, agents
+```
+- If using a [custom endpoint](/v0.8.3/docs/quick_start/custom_endpoints), you can use its name as the value (case-insensitive)
+
+```bash
+# using `endpoint=perplexity` for a custom endpoint named `Perplexity`
+https://your-domain.com/c/new?endpoint=perplexity&model=llama-3.1-sonar-small-128k-online
+```
+
+### Model Selection
+
+The `model` parameter can be used alone:
+```bash
+https://your-domain.com/c/new?model=gpt-4o
+```
+
+When only `model` is specified:
+- It will only select the model if it's available in the current endpoint
+- The current endpoint is either the default endpoint or the last selected endpoint
+
+### Prompt Parameter
+
+The `prompt` parameter allows you to pre-populate the chat input field:
+```bash
+https://your-domain.com/c/new?prompt=Explain quantum computing
+```
+
+You can also use `q` as a shorthand, which is interchangeable with `prompt`:
+```bash
+https://your-domain.com/c/new?q=Explain quantum computing
+```
+
+You can combine these with other parameters:
+```bash
+https://your-domain.com/c/new?endpoint=anthropic&model=claude-3-5-sonnet-20241022&prompt=Explain quantum computing
+```
+
+### Automatic Prompt Submission
+
+The `submit` parameter allows you to automatically submit the prompt without manual intervention:
+```bash
+https://your-domain.com/c/new?prompt=Explain quantum computing&submit=true
+```
+
+This feature is particularly useful for:
+- Creating automated workflows (e.g., Raycast, Alfred, Automater)
+- Building external integrations
+
+You can combine it with other parameters for complete automation:
+```bash
+https://your-domain.com/c/new?endpoint=openAI&model=gpt-4&prompt=Explain quantum computing&submit=true
+```
+
+### Special Endpoints
+
+#### Model Specs
+You can select a specific model spec by name:
+```bash
+https://your-domain.com/c/new?spec=meeting-notes-gpt4
+```
+This will load all the settings defined in the model spec. When using the `spec` parameter, other model parameters in the URL will be ignored.
+
+#### Agents
+You can directly load an agent using its ID without specifying the endpoint:
+```bash
+https://your-domain.com/c/new?agent_id=your-agent-id
+```
+This will automatically set the endpoint to `agents`.
+
+#### Assistants
+Similarly, you can load an assistant directly:
+```bash
+https://your-domain.com/c/new?assistant_id=your-assistant-id
+```
+This will automatically set the endpoint to `assistants`.
+
+## Supported Parameters
+
+LibreChat supports a wide range of parameters for fine-tuning your conversation settings:
+
+### LibreChat Settings
+- `maxContextTokens`: Override the system-defined context window
+- `resendFiles`: Control file resubmission in subsequent messages
+- `promptPrefix`: Set custom instructions/system message
+- `imageDetail`: 'low', 'auto', or 'high' for image quality
+ - Note: while this is a LibreChat-specific parameter, it only affects the following endpoints:
+ - OpenAI, Custom Endpoints, which are OpenAI-like, and Azure OpenAI, for which this defaults to 'auto'
+- `spec`: Select a specific LibreChat [Model Spec](/v0.8.3/docs/configuration/librechat_yaml/object_structure/model_specs) by name
+ - Must match the exact name of a configured model spec
+ - When specified, other model parameters will not take effect, only those defined by the model spec
+ - **Important:** If model specs are configured with `enforce: true`, using this parameter may be required for URL query params to work properly
+- `fileTokenLimit`: Set maximum token limit for file processing to control costs and resource usage.
+ - Note: Request value overrides YAML default.
+
+### Model Parameters
+Different endpoints support various parameters:
+
+**OpenAI, Custom, Azure OpenAI:**
+```bash
+# Note: these should be valid values according to the provider's API
+temperature, presence_penalty, frequency_penalty, stop, top_p, max_tokens,
+reasoning_effort, reasoning_summary, verbosity, useResponsesApi, web_search, disableStreaming
+```
+
+**Google, Anthropic:**
+```bash
+# Note: these should be valid values according to the provider's API
+topP, topK, maxOutputTokens, thinking, thinkingBudget, thinkingLevel, web_search
+```
+
+**Anthropic, Bedrock (Anthropic models):**
+
+Set this to `true` or `false` to toggle the "prompt-caching":
+```bash
+promptCache
+```
+
+More info: https://www.anthropic.com/news/prompt-caching, https://docs.aws.amazon.com/bedrock/latest/userguide/prompt-caching.html#prompt-caching-get-started
+
+**Bedrock:**
+```bash
+# Bedrock region
+region=us-west-2
+# Bedrock equivalent of `max_tokens`
+maxTokens=200
+# Bedrock reasoning effort (for supported models like ZAI, MoonshotAI)
+reasoning_effort=medium
+```
+
+**Assistants/Azure Assistants:**
+```bash
+# overrides existing assistant instructions for current run
+instructions=your+instructions
+```
+```bash
+# Adds the current date and time to `additional_instructions` for each run.
+append_current_datetime=true
+```
+
+## More Info
+
+For more information on any of the above, refer to [Model Spec Preset Fields](/v0.8.3/docs/configuration/librechat_yaml/object_structure/model_specs), which shares most parameters.
+
+**Example with multiple parameters:**
+```bash
+https://your-domain.com/c/new?endpoint=google&model=gemini-2.0-flash-exp&temperature=0.7&prompt=Oh hi mark
+```
+
+**Example with model spec:**
+```bash
+https://your-domain.com/c/new?spec=meeting-notes-gpt4&prompt=Here%20is%20the%20transcript...
+```
+Note: When using `spec`, other model parameters are ignored in favor of the model spec's configuration.
+
+## ⚠️ Warning
+
+Exercise caution when using query parameters:
+- Misuse or exceeding provider limits may result in API errors
+- If you encounter bad request errors, reset the conversation by clicking "New Chat"
+- Some parameters may have no effect if they're not supported by the selected endpoint
+
+## Best Practices
+
+1. Always use both `endpoint` and `model` when possible
+2. Verify parameter support for your chosen endpoint
+3. Use reasonable values within provider limits
+4. Test your parameter combinations before sharing URLs
+
+## Parameter Validation
+
+All parameters are validated against LibreChat's schema before being applied. Invalid parameters or values will be ignored, and valid settings will be applied to the conversation.
+
+---
+
+This feature enables powerful use cases like:
+- Sharing specific conversation configurations
+- Creating bookmarks for different chat settings
+- Automating chat setup through URL parameters
+
+---
+
+#LibreChat #ChatConfiguration #AIParameters #OpenSource #URLQueryParameters
diff --git a/content/docs-archive/v0.8.3/features/web_search.mdx b/content/docs-archive/v0.8.3/features/web_search.mdx
new file mode 100644
index 000000000..5676d10df
--- /dev/null
+++ b/content/docs-archive/v0.8.3/features/web_search.mdx
@@ -0,0 +1,206 @@
+---
+title: "Web Search"
+icon: Search
+---
+
+LibreChat's web search feature allows you to search the internet and retrieve relevant information to enhance your conversations. The feature consists of three main components that work together to provide comprehensive search results.
+
+## Quick Start
+
+To get started with web search, you'll need to configure API keys for all three components to ensure effective search results. You can do this in two ways:
+
+1. **Environment Variables** (Recommended for admins):
+ ```bash
+ # Search Provider (Required)
+ SERPER_API_KEY=your_serper_api_key
+ # or
+ SEARXNG_INSTANCE_URL=your_searxng_instance_url
+ SEARXNG_API_KEY=your_searxng_api_key # Optional
+
+ # Scraper (Required)
+ FIRECRAWL_API_KEY=your_firecrawl_api_key
+ # Optional: Custom Firecrawl API URL
+ FIRECRAWL_API_URL=your_firecrawl_api_url
+ # Optional: Firecrawl API version (v0 or v1)
+ # FIRECRAWL_VERSION=v1
+
+ # Reranker (Required)
+ JINA_API_KEY=your_jina_api_key
+ # Optional: Custom Jina API URL
+ JINA_API_URL=your_jina_api_url
+ # or
+ COHERE_API_KEY=your_cohere_api_key
+ ```
+
+2. **User Interface** (If environment variables are not set):
+ - Users will be prompted to enter the required API keys when they first use the web search feature
+ - They can choose which search provider (Serper or SearXNG) and which reranker service to use (Jina or Cohere)
+
+## Obtaining API Keys
+
+Each component of the web search feature requires its own API key. Here's how to obtain them:
+
+### Search Providers
+
+#### Serper
+1. Visit [Serper.dev](https://serper.dev)
+2. Sign up for an account
+3. Navigate to the API Key section
+4. Copy your API key
+5. Set it in your environment variables or provide it through the UI
+
+#### SearXNG
+1. Follow the setup instructions in the [Web Search Configuration](/v0.8.3/docs/configuration/librechat_yaml/object_structure/web_search#setting-up-searxng) documentation
+2. Set `SEARXNG_INSTANCE_URL` to your instance URL
+3. Optionally set `SEARXNG_API_KEY` if your instance requires authentication
+
+### Scraper: Firecrawl
+
+1. Visit [Firecrawl.dev](https://docs.firecrawl.dev/introduction#api-key)
+2. Sign up for an account
+3. Navigate to the API Key section
+4. Copy your API key
+5. Set it in your environment variables or provide it through the UI
+6. (Optional) If you're using a custom Firecrawl instance, you'll also need to set the API URL
+
+### Rerankers
+
+#### Jina
+1. Visit [Jina.ai](https://jina.ai/api-dashboard/)
+2. Sign up for an account
+3. Navigate to the API Dashboard
+4. Copy your API key
+5. Set it in your environment variables or provide it through the UI
+
+#### Cohere
+1. Visit [Cohere Dashboard](https://dashboard.cohere.com/welcome/login)
+2. Sign up for an account
+3. Navigate to the API Keys section
+4. Copy your API key
+5. Set it in your environment variables or provide it through the UI
+
+## Components
+
+### 1. Search Providers
+
+Search providers are responsible for performing the initial web search and returning relevant results.
+
+**Available Providers:**
+- **Serper**: A Google Search API that provides high-quality search results
+ - Get your API key from [Serper.dev](https://serper.dev/api-key)
+- **SearXNG**: Open-source, self-hosted meta search engine
+ - Self-host your own instance
+ - Privacy-focused search results
+
+### 2. Scrapers
+
+Scrapers extract the actual content from web pages returned by the search provider.
+
+**Available Scrapers:**
+- **Firecrawl**: A powerful web scraping service that extracts content from web pages
+ - Get your API key from [Firecrawl.dev](https://docs.firecrawl.dev/introduction#api-key)
+ - API URL is optional (defaults to Firecrawl's hosted service)
+
+**Planned Scrapers:**
+- **Local Firecrawl**: Self-hosted version of Firecrawl
+- Additional third-party scraping services
+
+### 3. Rerankers
+
+Rerankers analyze the scraped content to determine the most relevant parts and reorder them for better results.
+
+**Available Rerankers:**
+- **Jina**: AI-powered reranking service
+ - Get your API key from [Jina.ai](https://jina.ai/api-dashboard/)
+ - API URL is optional (defaults to Jina's hosted service)
+- **Cohere**: Advanced reranking service
+ - Get your API key from [Cohere Dashboard](https://dashboard.cohere.com/welcome/login)
+
+**Planned Rerankers:**
+- **RAG API**: Open-source reranking using RAG (Retrieval-Augmented Generation)
+- Additional third-party reranking services
+
+## Configuration
+
+### Admin Configuration
+
+Admins can configure the web search feature using environment variables. The YAML configuration allows you to specify custom environment variable names for each component.
+
+⚠️ **Important: Never put actual API keys or values in the YAML file (they won't work)- only use environment variable names.**
+
+```yaml
+webSearch:
+ # Search Provider Configuration
+ serperApiKey: "${CUSTOM_SERPER_API_KEY}" # ✅ Correct: Using environment variable name
+ # serperApiKey: "sk-123..." # ❌ Wrong: Never put actual API keys here
+ # or
+ searxngInstanceUrl: "${CUSTOM_SEARXNG_INSTANCE_URL}" # ✅ Correct: Using environment variable name
+ searxngApiKey: "${CUSTOM_SEARXNG_API_KEY}" # ✅ Correct: Using environment variable name
+ # searxngInstanceUrl: "http://..." # ❌ Wrong: Never put actual URLs here
+ # searxngApiKey: "sk-123..." # ❌ Wrong: Never put actual API keys here
+
+ # Scraper Configuration
+ firecrawlApiKey: "${CUSTOM_FIRECRAWL_API_KEY}"
+ firecrawlApiUrl: "${CUSTOM_FIRECRAWL_API_URL}"
+ # firecrawlApiKey: "fc-123..." # ❌ Wrong: Never put actual API keys here
+ # firecrawlApiUrl: "https://..." # ❌ Wrong: Never put actual URLs here
+
+ # Reranker Configuration
+ jinaApiKey: "${CUSTOM_JINA_API_KEY}"
+ jinaApiUrl: "${CUSTOM_JINA_API_URL}"
+ cohereApiKey: "${CUSTOM_COHERE_API_KEY}"
+ # jinaApiKey: "jn-123..." # ❌ Wrong: Never put actual API keys here
+ # jinaApiUrl: "https://..." # ❌ Wrong: Never put actual URLs here
+ # cohereApiKey: "ch-123..." # ❌ Wrong: Never put actual API keys here
+
+ # General Settings
+ safeSearch: 1 # Options: 0 (OFF), 1 (MODERATE - default), 2 (STRICT)
+```
+
+**Note:** The YAML configuration should only contain environment variable names (in the format `${VARIABLE_NAME}`). This flexibility enables:
+- Using different variable names in different environments
+- Supporting multiple configurations for different user groups
+- Future integration with role-based configurations
+
+If you want to restrict the system to use only specific services, you can specify the service types:
+
+```yaml
+webSearch:
+ # ... variable configurations ...
+ searchProvider: "serper" # Only use Serper for search
+ # searchProvider: "searxng" # Only use SearXNG for search
+ scraperProvider: "firecrawl" # Only use Firecrawl for scraping
+ rerankerType: "jina" # Only use Jina for reranking
+```
+
+### User Configuration
+
+If the admin hasn't configured all the necessary API keys, users will be prompted to provide them through the UI. The interface allows users to:
+
+1. Choose their preferred reranker (Jina or Cohere)
+2. Enter API keys for the required services
+3. Configure the Firecrawl API URL if needed (optional)
+4. Configure the Jina API URL if needed (optional)
+
+## Usage
+
+Once configured, you can use web search in two ways:
+
+1. **Chat Interface**: Click the web search button in the chat interface to enable web search for your conversation
+2. **Agents**: Use the `web_search` capability in agents to allow them to search the web
+
+## Notes
+
+- All three components (search provider, scraper, and reranker) are required for effective search results
+- The Firecrawl API URL is optional and defaults to their hosted service
+- The Jina API URL is optional and defaults to their hosted service
+- Safe search provides three levels of content filtering: OFF (0), MODERATE (1 - default), and STRICT (2)
+- The scraper timeout is set to 7.5 seconds (7500ms) by default
+- API keys can be revoked at any time through the UI
+- Future updates will include more open-source, self-hosted options for all components
+- Additional customization options are planned, including:
+ - Control over the number of links to scrape
+ - Domain allowlist/blocklist for scraping
+ - Custom scraping rules and filters
+ - Advanced result filtering and ranking options
+ - Rate limiting and request throttling controls
diff --git a/content/docs-archive/v0.8.3/index.mdx b/content/docs-archive/v0.8.3/index.mdx
new file mode 100644
index 000000000..038c8847c
--- /dev/null
+++ b/content/docs-archive/v0.8.3/index.mdx
@@ -0,0 +1,7 @@
+---
+title: Quick Start
+icon: Rocket
+description: Choose your setup method and get LibreChat running in minutes.
+---
+
+
+ 
+ *Centralized dashboard for managing all your shared links*
+
+
+ 
+ *View details and manage individual shared links*
+
+
+ ./helm/librechat`
+
+
+Similar to other Helm charts, there exists a [values file](https://github.com/danny-avila/LibreChat/blob/main/helm/librechat/values.yaml) that outlines the default settings and indicates which configuration options can be modified.
+
+Create a `values.yaml` file populated with the values you want to modify from the default.
+
+Install the Helm chart: `helm install librechat oci://ghcr.io/danny-avila/librechat-chart/librechat --values Development version
+ +In the repo's root directory, run: + +`helm install
+
+ 
+
+
|
+| **Arabic (ar)** | |
+| **Tibetan (bo)** | |
+| **Bosnian (bs)** | |
+| **Catalan (ca)** | |
+| **Czech (cs)** | |
+| **Danish (da)** | |
+| **German (de)** | |
+| **Spanish (es)** | |
+| **Estonian (et)** | |
+| **Persian (fa)** | |
+| **Finnish (fi)** | |
+| **French (fr)** | |
+| **Hebrew (he)** | |
+| **Hungarian (hu)** | |
+| **Armenian (hy)** | |
+| **Indonesian (id)** | |
+| **Icelandic (is)** | |
+| **Italian (it)** | |
+| **Japanese (ja)** | |
+| **Georgian (ka)** | |
+| **Korean (ko)** | |
+| **Lithuanian (lt)** | |
+| **Latvian (lv)** | |
+| **Norwegian Bokmål (nb)** | |
+| **Norwegian Nynorsk (nn)** | |
+| **Dutch (nl)** | |
+| **Polish (pl)** | |
+| **Portuguese (pt-PT)** | |
+| **Brazilian Portuguese (pt-BR)** | |
+| **Russian (ru)** | |
+| **Slovak (sk)** | |
+| **Slovenian (sl)** | |
+| **Swedish (sv)** | |
+| **Thai (th)** | |
+| **Turkish (tr)** | |
+| **Uyghur (ug)** | |
+| **Ukrainian (uk)** | |
+| **Vietnamese (vi)** | |
+| **Chinese (Simplified) (zh-Hans)** | |
+| **Chinese (Traditional) (zh-Hant)** | |
+
+---
+
+
+## Getting Started
+
+Before you begin translating, please follow the steps below to set up your Locize account and start contributing.
+
+
+### Step 1: Create a Locize Account
+
+1. Visit the Registration Page
+
+ Choose your preferred language and click the corresponding link to register:
+
+ - **[English (en)](https://www.locize.app/register?invitation=tTHVYwI9TzWuOeJnKyWxSuuaDrSS5TsZqRh0BAHzebuuljz5OUXnlqbksio5WnXp)**
+ - **[Arabic (ar)](https://www.locize.app/register?invitation=Cn7hc6teYyY89nvQdosfXkubbj2MZi2XMzcxUP6fGglcPkAgd1AwS5Pfbr1Wu4lz)**
+ - **[Tibetan (bo)](https://www.locize.app/register?invitation=183Kk5eTUvr0oeKkZqsIrSG1iflQPk5WjZzH5tb1uwDS7MdS3nFo55frHm86lz78)**
+ - **[Bosnian (bs)](https://www.locize.app/register?invitation=JA2zNrFrvoEbrXQgoZAxRrEStscwrCCAhTP7t44NBxa7XAJbdhwpqntq3xQ6Wltw)**
+ - **[Catalan (ca)](https://www.locize.app/register?invitation=c7ZQ0OT9k6c5kWRXMspgRQZXoZk2vZYIZ3RTpDkVrtShlauJ55YpeMo9EOBsYXgS)**
+ - **[Czech (cs)](https://www.locize.app/register?invitation=ypNUvwJG9ynzZabWS4X1bD2b8qSmhbvyXsytm1sbkVmqN0A6inKhiny2FuNVcvC2)**
+ - **[Danish (da)](https://www.locize.app/register?invitation=xClNgP4A7SNcMdhkTsf6xm8wP24mNbSW3YhnOtDNd7nMHhAZPJsWV8UIyTR6lLxI)**
+ - **[German (de)](https://www.locize.app/register?invitation=rAXIyYNuO53txcygphdOClUR5YnNccd1MZ1Vs66p4ziOqHfM3MFiKnymdK6wLMpW)**
+ - **[Spanish (es)](https://www.locize.app/register?invitation=gkrRvUjxvFnRfUtynbaREj2zdbvd2FU95OFGcixGMOkcCxSwmrvOBclBZJWmERw6)**
+ - **[Estonian (et)](https://www.locize.app/register?invitation=q1ye9gNpYsVKvs2JS5CEjp4SBy6ovq2aUeIhAMsRoW2iVcdfxpc4GiOaHGDV85VZ)**
+ - **[Persian (fa)](https://www.locize.app/register?invitation=DfuKT56Y4KxlPOm6biYl9zbgMo3kBjWJA3Flbd7X5H4hJluUWTsFiQ3MQH07fH0d)**
+ - **[Finnish (fi)](https://www.locize.app/register?invitation=weERAttD7ax0Zfo5w9LyfWbaP50WPbS4Vk7BF1P6wM0fe5Q0xlrJACVjTAGbkv2c)**
+ - **[French (fr)](https://www.locize.app/register?invitation=wz5EbZiwE9Bxev4TTAyG09PKvnFSQoOaLomxVgEKOyaLhm9oCDdhDi4TkJp8rcq5)**
+ - **[Hebrew (he)](https://www.locize.app/register?invitation=3LSHQxUsHYumNhw5ZJNu6Re6x699i6RGnpdKzt2BrDeNFNObxjj2lKXfZFUhb1jP)**
+ - **[Hungarian (hu)](https://www.locize.app/register?invitation=3TaJ2SnDnYfTJQLalKK751cQ04AK5A2gRahC2poeZYXj8MymZ5T0rt4V688e0H7M)**
+ - **[Armenian (hy)](https://www.locize.app/register?invitation=jLAFuEOvlBR86IcF1dZFHobsYdINvFoi0dMxxrJHvXIyxnosWcDblcXn6FtOhcOo)**
+ - **[Indonesian (id)](https://www.locize.app/register?invitation=S94A2D6glr7w64Nf27XwmvzkcnTRAWhxFoxcl7ZRnmm1dMx23kfpZCx8ROlqb6X2)**
+ - **[Icelandic (is)](https://www.locize.app/register?invitation=zgnniaPHGcML0dX5TdZ7Cv9fVkWkVGbrShol4JZYaYQXyk7t2oNlITaImx5n3wZe)**
+ - **[Italian (it)](https://www.locize.app/register?invitation=LI6zvAH82797Gro6lc490d34zrw8vthQPdN01n9nfk2c1LW5VVpf4Db6WL5GFHir)**
+ - **[Japanese (ja)](https://www.locize.app/register?invitation=VVJLuv7WjjBs0wShxZheCIvwzk7XszVsHCAMZmCQ34SJYrwIeB1GW6u2vkYNJdzk)**
+ - **[Georgian (ka)](https://www.locize.app/register?invitation=WK5hB5nznxioaDGOXXPDmcULrNfFA3wkcvS2YiUbrU6b73gKOWix5Qg7uGjpPtkH)**
+ - **[Korean (ko)](https://www.locize.app/register?invitation=nbL4LZMwehlTvFKNmNGgTTJt9YsZuuyCMjF9yAc92bVIWEjAc9C1G0ujsEl76dYb)**
+ - **[Lithuanian (lt)](https://www.locize.app/register?invitation=mObXVLL1r0IpkldNhVvahfdBSxo1AtqytlBavTU9jAb2M5K1HdbEADfpXpJWkyQK)**
+ - **[Latvian (lv)](https://www.locize.app/register?invitation=ey55PwxruCkT1EJ95oluthUzDbXwYJL4pXEd2xQoEHLwleVWND4VRND13a7EsioC)**
+ - **[Norwegian Bokmål (nb)](https://www.locize.app/register?invitation=14FVJmxYhd7ZSzjmxkF1XEU0jO9HDG7lpRRiOwVNKi19Ad6hD58NWASD0bN8JgaK)**
+ - **[Norwegian Nynorsk (nn)](https://www.locize.app/register?invitation=0upNDr8hxNUkMCAu0Lzo1MQnM0i7VXbli9x2wvygCz0q8sAK2z1AwxkgUDOD4n9R)**
+ - **[Dutch (nl)](https://www.locize.app/register?invitation=BQoligTqND5E4jlGmXJZVzkLOpo4pTf9wUyN19zZbgNB38JHaciJ2FnIbsLOXPbe)**
+ - **[Polish (pl)](https://www.locize.app/register?invitation=ZPiib1OoPM3OHBUow79I8iQNiFk4SHO7HASO3rHdJpKSlJwA4oxsORR2w4yJaPig)**
+ - **[Portuguese (pt-PT)](https://www.locize.app/register?invitation=c11DbWJk7O5TNIKon9leIfIbqARz60URaGB0WFQPT2ym3wxUDR8DgIiOlXNIBz13)**
+ - **[Brazilian Portuguese (pt-BR)](https://www.locize.app/register?invitation=99JdsEgKuVR9XhQJWi91Jq0LkqigiSz4EOf4gVGSr5RwZPp6ad4JQZLHVwhumNvB)**
+ - **[Russian (ru)](https://www.locize.app/register?invitation=rz4C3pVFdfr5XPPNTsYJvjjnC7vHDVWVOfyUzCf33MxhccdYB7vM7jxcHLacGl14)**
+ - **[Slovak (sk)](https://www.locize.app/register?invitation=wQkVqwu4Xr2KzmCgsXmqI7nMjyBzT2EKNFS3P6rNe4Kii3DgQG1i5ozeQeVEBmNd)**
+ - **[Slovenian (sl)](https://www.locize.app/register?invitation=NyNTniuVwwvEkKoKoOvAT4nzbVuvxE5X4kVUhBE9KSb3sEwEARQtMTeBCqpuV9dk)**
+ - **[Swedish (sv)](https://www.locize.app/register?invitation=RYtYhip5O5ACNCth1cIZpByGnZC1b3JttimEe8mrz5NDyEjVAs1PVcMIQ1in4j7D)**
+ - **[Thai (th)](https://www.locize.app/register?invitation=3xMjJPqupRNO2BU7K3WMWhxFtoGNzL97hxKIGjE8Yoa4v7lJj8ZjTy5p5dmcfLjW)**
+ - **[Turkish (tr)](https://www.locize.app/register?invitation=x3Ov59Gdrk2b76gn5pSVCwuekDs817YOYElXJn9zCYClPG2XlBORQDRygZmdBH4B)**
+ - **[Uyghur (ug)](https://www.locize.app/register?invitation=TeQX9ECX0oqhtkyBswm8BeOqlSaA5dKZaptvaEpYlfBhGBSl8PGIYfdVvPvgQnQF)**
+ - **[Ukrainian (uk)](https://www.locize.app/register?invitation=4Z060E9kPjmOqO8BmRSvuIujLydZiRCc0lu90iwQSaCche1tSdFcGOrdlDgPZ2ec)**
+ - **[Vietnamese (vi)](https://www.locize.app/register?invitation=rhADX8GuhgQmYrmbHT13YVg2WqMLJpgPdh1OBuujn9GoNUVW6RPipYvC20aH1xcQ)**
+ - **[Chinese (Simplified) (zh-Hans)](https://www.locize.app/register?invitation=HXXM2h8SJsBLIPJol3usRct0aPPcr809xzfV4DQHolyEfeSjBwEjChd37vE3ZrRw)**
+ - **[Chinese (Traditional) (zh-Hant)](https://www.locize.app/register?invitation=9PWBDcMascIBGG6wwobkVT6cL7p7IncFZVqwIe0e7VZd14MJOAMQGk6IjlvgmA00)**
+
+
+2. **Fill in Your Details:**
+Enter your email, password, and any other required information, then click **Sign Up**.
+
+
+
+
+### Step 2: Explore the Locize Dashboard
+
+After signing up, you’ll be directed to the Locize dashboard, where you can see an overview of the translation project.
+
+- **Dashboard Overview:**
+This page displays the available languages and progress statistics for the project.
+
+
+
+
+### Step 3: Select Your Language
+
+1. **Open the Language Dropdown:**
+Click the dropdown menu that lists all supported languages.
+
+2. **Choose Your Preferred Language:**
+For example, if you want to translate into Dutch, scroll down and select **Dutch**.
+
+
+
+
+### Step 4: Navigate to the Translation Page
+
+After selecting your language, click on the translation progress indicator (for example, "35.61% translated"). This will take you to the page where you can contribute translations.
+
+
+
+
+### Step 5: Contribute Your Translation
+
+1. **Browse the Translation Strings:**
+The interface displays a list of translation keys along with their original texts.
+
+2. **Select a String to Translate:**
+Click on the string you wish to work on.
+
+3. **Enter Your Translation:**
+Type your translated text into the input field provided next to the original text.
+
+4. **Review Your Work:**
+Ensure that your translation is accurate and clear.
+
+
+
+
+### Step 6: Save and Submit Your Translation
+
+1. **Submit Your Translation:**
+Once you’re satisfied with your translation, click the **Save** button to submit it for review.
+
+2. **Pending Review:**
+Your submitted translation will be marked as pending and will be reviewed by project maintainers.
+
+
+
+
+### Step 7: Translation Approval
+
+After review, your translation will be approved and integrated into the project.
+
+- **Approved Translation:**
+Once approved, your contribution will be reflected in the Locize dashboard and the overall translation progress.
+
+
+
+---
+
+## Handling `{{0}}` and `{{1}}` in Translation Strings
+
+Sometimes translation strings need to include dynamic content. These dynamic parts, called **interpolations**, are represented by placeholders enclosed in double curly brackets (e.g., `{{0}}` or `{{1}}`). When translating such strings, it's important to maintain these placeholders in the correct positions.
+
+Below are two examples to help guide you:
+
+### Example 1: Single Interpolation
+
+Consider the translation key `com_assistants_completed_action`. The original English text is:
+
+```text
+Talked to {{0}}
+```
+
+For the German translation, ensure the placeholder remains intact and is placed appropriately:
+
+```text
+Mit {{0}} gesprochen
+```
+
+This image shows how a single interpolation is represented in a translation string:
+
+
+
+---
+
+### Example 2: Multiple Interpolations
+
+Now, look at the translation key `com_files_number_selected`, which includes two placeholders. The English version is:
+
+```text
+{{0}} of {{1}} item(s) selected
+```
+
+In the German translation, both placeholders must be preserved and positioned correctly:
+
+```text
+{{0}} von {{1}} Datei(en) ausgewählt
+```
+
+This image illustrates how multiple interpolations appear in translation strings:
+
+
+
+---
+
+
+## Adding a New Language
+
+If you don't see your language listed in our translation table, you can help us expand our language support:
+
+1. **Create a New Issue:**
+Open a new issue in our GitHub repository: [LibreChat Issues](https://github.com/danny-avila/LibreChat/issues).
+
+2. **Select the New Language Request Template:**
+Use the **New Language Request** template and provide:
+ - The full name of your language (e.g., Spanish, Mandarin).
+ - The [ISO 639-1](https://www.w3schools.com/tags/ref_language_codes.asp) code for your language (e.g., `es` for Spanish).
+
+3. **Collaborate with Maintainers:**
+Our maintainers will review your request and work with you to integrate the new language. Once approved, your language will appear in the translation progress table, and you can start contributing.
+
+---
+
+## Need Help?
+
+If you have any questions or need assistance, please feel free to:
+
+- **Open an Issue:**
+Submit an issue in our repository: [LibreChat Issues](https://github.com/danny-avila/LibreChat/issues).
+
+- **Join Our Discord Community:**
+Connect with fellow translators on our [Discord server](https://discord.librechat.ai).
+
+- **Contact a Maintainer:**
+Reach out directly to one of our project maintainers for additional support.
+
+Your contributions help make LibreChat accessible to users worldwide. Thank you for supporting our project, and happy translating!
+
+
+---
+
+We thank [Locize](https://locize.com) for their translation management tools that support multiple languages in LibreChat.
+
+
+
+
+
+
+
diff --git a/content/docs-archive/v0.8.3/user_guides/meta.json b/content/docs-archive/v0.8.3/user_guides/meta.json
new file mode 100644
index 000000000..2b90dd538
--- /dev/null
+++ b/content/docs-archive/v0.8.3/user_guides/meta.json
@@ -0,0 +1,10 @@
+{
+ "title": "User Guides",
+ "icon": "BookOpen",
+ "pages": [
+ "index",
+ "ai_overview",
+ "presets",
+ "mongodb"
+ ]
+}
diff --git a/content/docs-archive/v0.8.3/user_guides/mongodb.mdx b/content/docs-archive/v0.8.3/user_guides/mongodb.mdx
new file mode 100644
index 000000000..7d963e853
--- /dev/null
+++ b/content/docs-archive/v0.8.3/user_guides/mongodb.mdx
@@ -0,0 +1,42 @@
+---
+title: MongoDB
+icon: Database
+description: Why LibreChat Uses MongoDB
+---
+
+MongoDB, a popular NoSQL database, was chosen as the core database for LibreChat due to its flexibility, scalability, and ability to handle diverse data structures efficiently. Here are some key reasons why MongoDB is an excellent fit for LibreChat:
+
+
+
+
+
+
+
+
+
+
+## 1. Flexible Data Model
+MongoDB's document-based data model allows for storing and retrieving data in a flexible and dynamic manner. Unlike traditional relational databases, MongoDB doesn't require a fixed schema, making it easier to adapt to changing data requirements. This flexibility is essential for LibreChat, as it needs to store various types of data, such as conversation histories, user profiles, presets, API keys, and more, without being constrained by a rigid table structure.
+
+## 2. Efficient Storage of Conversation Histories
+One of the primary use cases for LibreChat is to store and retrieve conversation histories. MongoDB's ability to store nested data structures as JSON-like documents makes it an excellent choice for storing conversation histories, which can include complex data structures like messages, timestamps, and metadata.
+
+## 3. Secure Storage of Sensitive Data
+LibreChat handles sensitive data, such as API keys and encrypted user passwords. MongoDB's built-in support for data encryption at rest and in transit ensures that this sensitive information remains secure and protected from unauthorized access.
+
+## 4. Horizontal Scalability
+As LibreChat grows and attracts more users, its data storage requirements will increase. MongoDB's horizontal scalability allows for scaling out by adding more servers to a cluster, providing the ability to handle larger amounts of data and higher traffic loads without compromising performance.
+
+## 5. Cross-Device Accessibility
+LibreChat aims to provide a seamless experience across multiple devices, allowing users to access their data and conversation histories from different devices. MongoDB's replication and sharding capabilities ensure that data is consistently available and accessible, enabling users to pick up their conversations where they left off, regardless of the device they're using.
+
+## 6. Developer Productivity
+MongoDB's intuitive query language and rich ecosystem of tools and libraries contribute to faster development cycles and increased developer productivity. This aligns well with LibreChat's goal of being an open-source project, fostering collaboration and contributions from the developer community.
+
+By leveraging MongoDB's strengths, LibreChat can efficiently manage and store diverse data structures, ensure data security and availability, and provide a seamless cross-device experience for its users. MongoDB's flexibility, scalability, and developer-friendly features make it an ideal choice for powering the core functionalities of LibreChat.
+
+
+## Note
+
+
+
+
+
+
+## OAuth2
+
+- [Apple](/v0.8.4/docs/configuration/authentication/OAuth2-OIDC/apple)
+- [Discord](/v0.8.4/docs/configuration/authentication/OAuth2-OIDC/discord)
+- [Facebook](/v0.8.4/docs/configuration/authentication/OAuth2-OIDC/facebook)
+- [GitHub](/v0.8.4/docs/configuration/authentication/OAuth2-OIDC/github)
+- [Google](/v0.8.4/docs/configuration/authentication/OAuth2-OIDC/google)
+
+## OpenID Connect
+
+- [Auth0](/v0.8.4/docs/configuration/authentication/OAuth2-OIDC/auth0)
+- [AWS Cognito](/v0.8.4/docs/configuration/authentication/OAuth2-OIDC/aws)
+- [Azure Entra/AD](/v0.8.4/docs/configuration/authentication/OAuth2-OIDC/azure)
+- [Keycloak](/v0.8.4/docs/configuration/authentication/OAuth2-OIDC/keycloak)
+- [Re-use OpenID Tokens for Login Session](/v0.8.4/docs/configuration/authentication/OAuth2-OIDC/token-reuse)
+
+## Troubleshooting OpenID Connect
+
+If you encounter issues with OpenID Connect authentication:
+
+1. **Enable Header Debug Logging**: Set `DEBUG_OPENID_REQUESTS=true` in your environment variables to log request headers in addition to URLs (with sensitive data masked). Note: Request URLs are always logged at debug level
+2. **Check Redirect URIs**: Ensure your callback URL matches exactly between your provider and LibreChat configuration
+3. **Verify Scopes**: Make sure all required scopes are properly configured
+4. **Review Provider Logs**: Check your identity provider's logs for authentication errors
+5. **Validate Tokens**: Ensure your provider is issuing valid tokens with the expected claims
+6. **Ensure _nonce_ is generated**: Some identity providers generate `nonce` url parameter if it's missing in the request. Set `OPENID_GENERATE_NONCE=true` to force the openid-client to generate it.
+
diff --git a/content/docs-archive/v0.8.4/configuration/authentication/OAuth2-OIDC/keycloak.mdx b/content/docs-archive/v0.8.4/configuration/authentication/OAuth2-OIDC/keycloak.mdx
new file mode 100644
index 000000000..7f1289bc8
--- /dev/null
+++ b/content/docs-archive/v0.8.4/configuration/authentication/OAuth2-OIDC/keycloak.mdx
@@ -0,0 +1,70 @@
+---
+title: Keycloak
+icon: KeyRound
+description: Learn how to configure LibreChat to use Keycloak for user authentication.
+---
+
+1. **Access Keycloak Admin Console:**
+- Open the Keycloak Admin Console in your web browser. This is usually
+found at a URL like `http://localhost:8080/auth/admin/`.
+
+2. **Create a Realm (if necessary):**
+- If you don't already have a realm for your application, create one. Click on 'Add Realm' and give it a name.
+
+3. **Create a Client:**
+- Within your realm, click on 'Clients' and then 'Create'.
+- Enter a client ID and select 'openid-connect' as the Client Protocol.
+- Set 'Client Authentication' to 'On'.
+- In 'Valid Redirect URIs', enter `http://localhost:3080/oauth/openid/callback` or the appropriate URI for
+your application.
+
+
+
+
+
+
+
+
+4. **Configure Client:**
+- After creating the client, you will be redirected to its settings page.
+- Note the 'Client ID' and 'Secret' from the 'Credentials' tab – you'll need these for your application.
+
+
+
+
+5. **Add Roles (Optional):**
+If you want to restrict access to users with specific roles, you can define roles in Keycloak and assign them to users.
+- Go to the 'Roles' tab in your client or realm (depending on where you want to define the roles).
+- Create roles that match the value(s) you have in `OPENID_REQUIRED_ROLE`.
+
+
+
+6. **Assign Roles to Users (Optional):**
+- Go to 'Users', select a user, and go to the 'Role Mappings' tab.
+- Assign at least one of the roles specified in `OPENID_REQUIRED_ROLE` to the user.
+
+
+
+7. **Get path of roles list inside token (Optional):**
+- Decode your jwtToken from OpenID provider and determine path for roles list inside access token. For example, if you are
+ using Keycloak, the path is `realm_access.roles`.
+- Put this path in `OPENID_REQUIRED_ROLE_PARAMETER_PATH` variable in `.env` file.
+- By parameter `OPENID_REQUIRED_ROLE_TOKEN_KIND` you can specify which token kind you want to use.
+ Possible values are `access` and `id`.
+
+8. **Update Your Project's Configuration:**
+- Open the `.env` file in your project folder and add the following variables:
+ ```bash filename=".env"
+ OPENID_ISSUER=http://localhost:8080/realms/[YourRealmName]
+ OPENID_CLIENT_ID=[YourClientID]
+ OPENID_CLIENT_SECRET=[YourClientSecret]
+ OPENID_SESSION_SECRET=[JustGenerateARandomSessionSecret]
+ OPENID_CALLBACK_URL=/oauth/openid/callback
+ OPENID_SCOPE="openid profile email"
+ OPENID_REQUIRED_ROLE=[YourRequiredRole] # Single role or comma-separated roles (e.g., role1,role2,admin)
+ OPENID_REQUIRED_ROLE_TOKEN_KIND=(access|id) # that means, `access` or `id`
+ OPENID_REQUIRED_ROLE_PARAMETER_PATH="realm_access.roles"
+
+ # Optional: redirects the user to the end session endpoint after logging out
+ OPENID_USE_END_SESSION_ENDPOINT=true
+ ```
diff --git a/content/docs-archive/v0.8.4/configuration/authentication/OAuth2-OIDC/meta.json b/content/docs-archive/v0.8.4/configuration/authentication/OAuth2-OIDC/meta.json
new file mode 100644
index 000000000..b96081a48
--- /dev/null
+++ b/content/docs-archive/v0.8.4/configuration/authentication/OAuth2-OIDC/meta.json
@@ -0,0 +1,21 @@
+{
+ "title": "OAuth2 & OIDC",
+ "icon": "KeyRound",
+ "pages": [
+ "index",
+ "---OAuth2---",
+ "apple",
+ "discord",
+ "facebook",
+ "github",
+ "google",
+ "---OIDC---",
+ "auth0",
+ "authelia",
+ "authentik",
+ "aws",
+ "azure",
+ "keycloak",
+ "token-reuse"
+ ]
+}
diff --git a/content/docs-archive/v0.8.4/configuration/authentication/OAuth2-OIDC/token-reuse.mdx b/content/docs-archive/v0.8.4/configuration/authentication/OAuth2-OIDC/token-reuse.mdx
new file mode 100644
index 000000000..57b27da6e
--- /dev/null
+++ b/content/docs-archive/v0.8.4/configuration/authentication/OAuth2-OIDC/token-reuse.mdx
@@ -0,0 +1,144 @@
+---
+title: OpenID Connect Token Reuse
+icon: Fingerprint
+description: How to configure OpenID Connect token reuse with LibreChat
+---
+
+LibreChat supports reusing access and refresh tokens issued by your OpenID Connect provider (like Azure Entra ID or Auth0) to manage user authentication state. When this feature is active, the refresh token passed to the user as a cookie is issued by your OpenID provider instead of LibreChat, allowing LibreChat servers to refresh it and request access tokens from your provider.
+
+## Prerequisites
+
+- A configured OpenID Connect provider (like Azure Entra ID, Auth0, etc.)
+- Basic OpenID Connect setup completed
+
+## Configuration Steps
+
+1. Set `OPENID_REUSE_TOKENS=true` in your environment variables.
+
+## Provider-Specific Configuration
+
+### Auth0 Configuration
+
+
+
+
+
+
+
+
+
+
+
+
+## Session Expiry and Refresh Token
+
+- Default values: session expiry: 15 minutes, refresh token expiry: 7 days
+ - For more information: **[GitHub PR #927 - Refresh Token](https://github.com/danny-avila/LibreChat/pull/927)**
+
+
+ 
+
+
+
+ 
+
+
+
+
+## Production Setup
+
+Azure Blob Storage offers scalable, secure object storage for files in LibreChat. Follow these steps to configure your Azure Blob Storage.
+
+## 1. Create an Azure Storage Account
+
+1. **Sign in to Azure:**
+ - Open the [Azure Portal](https://portal.azure.com/) and sign in with your Microsoft account.
+
+2. **Create a Storage Account:**
+ - Click on **"Create a resource"** and search for **"Storage account"**.
+ - Click **"Create"** and fill in the required details:
+ - **Subscription & Resource Group:** Choose your subscription and either select an existing resource group or create a new one.
+ - **Storage Account Name:** Enter a unique name (e.g., `mylibrechatstorage`).
+ - **Region:** Select the region closest to your users.
+ - **Performance & Redundancy:** Choose the performance tier and redundancy level that best suit your needs.
+ - Click **"Review + Create"** and then **"Create"**. Wait until the deployment completes.
+
+## 2. Set Up Authentication
+
+You have two options for authenticating with your Azure Storage Account:
+
+### Option A: Using a Connection String
+
+1. **Navigate to Access Keys:**
+ - In your newly created storage account, go to **"Access keys"** in the sidebar.
+
+2. **Copy Connection String:**
+ - Copy one of the connection strings provided. This string includes the credentials required to connect to your Blob Storage account.
+
+### Option B: Using Managed Identity
+
+If your LibreChat application is running on an Azure service that supports Managed Identity (such as an Azure VM, App Service, or AKS), you can use that instead of a connection string.
+
+1. **Assign Managed Identity:**
+ - Ensure your Azure resource (VM, App Service, or AKS) has a system-assigned or user-assigned Managed Identity enabled.
+
+2. **Grant Storage Permissions:**
+ - In your storage account, assign the **Storage Blob Data Contributor** (or a similarly scoped role) to your Managed Identity. This allows your application to access Blob Storage without a connection string.
+
+## 3. Update Your Environment Variables
+
+Create or update your `.env` file in your project’s root with the following configuration:
+
+```bash filename=".env"
+# Option A: Using a Connection String
+AZURE_STORAGE_CONNECTION_STRING=DefaultEndpointsProtocol=https;AccountName=yourAccountName;AccountKey=yourAccountKey;EndpointSuffix=core.windows.net
+
+# Option B: Using Managed Identity (do not set the connection string if using Managed Identity)
+AZURE_STORAGE_ACCOUNT_NAME=yourAccountName
+
+AZURE_STORAGE_PUBLIC_ACCESS=false
+AZURE_CONTAINER_NAME=files
+```
+
+- **AZURE_STORAGE_CONNECTION_STRING:** Set this if you are using Option A.
+- **AZURE_STORAGE_ACCOUNT_NAME:** Set this if you are using Option B (Managed Identity). Do not set both.
+- **AZURE_STORAGE_PUBLIC_ACCESS:** Set to `false` if you do not want your blobs to be publicly accessible by default. Set to `true` if you need public access (for example, for publicly viewable images).
+- **AZURE_CONTAINER_NAME:** This is the container name your application will use (e.g., `files`). The application will automatically create this container if it doesn’t exist.
+
+## 4. Configure LibreChat to Use Azure Blob Storage
+
+Update your LibreChat configuration file (`librechat.yaml`) to specify that the application should use Azure Blob Storage for file handling:
+
+```yaml filename="librechat.yaml"
+version: 1.3.5
+cache: true
+fileStrategy: "azure_blob"
+```
+
+On this page
+ +
+
+
+
+
+
+
+
+
+
+
+
+ - **From Settings Panel**: A dedicated "MCP Settings" section in the right panel lists all MCP servers with definable custom variables. Users can click on a server to open the configuration dialog to set or update their credentials for that specific MCP server.
+
+ - These user-provided values are stored securely, associated with the individual user and the specific MCP server, and substituted at runtime.
+- **Example:**
+ ```yaml
+ customUserVars:
+ MY_SERVICE_API_KEY:
+ title: "My Service API Key"
+ description: "Your personal API access key for My Service. Find it at My Service API Settings."
+ SOME_OTHER_VAR:
+ title: "Some Other Variable"
+ description: "The specific value for some other configuration (e.g., a specific path or identifier)."
+ ```
+ Usage in `headers`:
+ ```yaml
+ headers:
+ X-Auth-Token: "{{MY_SERVICE_API_KEY}}"
+ X-Some-Other-Config: "{{SOME_OTHER_VAR}}"
+ ```
+ Usage in `env` (for `stdio` type):
+ ```yaml
+ env:
+ API_KEY: "{{MY_SERVICE_API_KEY}}"
+ ```
+
+#### `oauth`
+
+- **Type:** Object (Optional)
+- **Description:** OAuth2 configuration for authenticating with the MCP server. When configured, users will be prompted to authenticate via OAuth flow before the MCP server can be used. If no client id & client secret is provided, Dynamic Client Registration (DCR) will be used.
+- **Required Subkeys:**
+ - `authorization_url`: String - The OAuth authorization endpoint URL
+ - `token_url`: String - The OAuth token endpoint URL
+ - `client_id`: String - OAuth client identifier
+ - `client_secret`: String - OAuth client secret
+ - `redirect_uri`: String - [OAuth redirect URI](/v0.8.4/docs/features/mcp#oauth-callback-url) (eg. `http://localhost:3080/api/mcp/${serverName}/oauth/callback`)
+ - `scope`: String - OAuth scopes (space-separated)
+- **Optional Subkeys:**
+ - `grant_types_supported`: Array of Strings - Supported grant types (defaults to `["authorization_code", "refresh_token"]`)
+ - `token_endpoint_auth_methods_supported`: Array of Strings - Supported token endpoint authentication methods (defaults to `["client_secret_basic", "client_secret_post"]`)
+ - `response_types_supported`: Array of Strings - Supported response types (defaults to `["code"]`)
+ - `code_challenge_methods_supported`: Array of Strings - Supported PKCE code challenge methods (defaults to `["S256", "plain"]`)
+ - `skip_code_challenge_check`: Boolean - Skip checking whether the OAuth provider advertises PKCE support. Useful for providers like AWS Cognito that support S256 but don't advertise it in their metadata. (defaults to `false`)
+- **Example:**
+ ```yaml
+ oauth-api-server:
+ authorization_url: https://api.example.com/oauth/authorize
+ token_url: https://api.example.com/oauth/token
+ client_id: your_client_id
+ client_secret: your_client_secret
+ redirect_uri: http://localhost:3080/api/mcp/oauth-api-server/oauth/callback
+ scope: "read execute"
+ grant_types_supported: ["authorization_code", "refresh_token"]
+ token_endpoint_auth_methods_supported: ["client_secret_post"]
+ response_types_supported: ["code"]
+ code_challenge_methods_supported: ["S256", "plain"]
+ ```
+
+#### `startup`
+
+- **Type:** Boolean (Optional)
+- **Description:** When set to `false`, this MCP server will not be connected at application startup. This is useful for servers that require user input or configuration before connecting, or for cases where you want to control when the server is initialized.
+- **Default Value:** `true`
+- **Example:**
+ ```yaml
+ mcpServers:
+ my-mcp-server:
+ type: streamable-http
+ url: "https://api.example.com/mcp/"
+ startup: false
+ ```
+
+### Notes
+
+- **Type Inference:**
+ - If `type` is omitted:
+ - If `url` is specified and starts with `http://` or `https://`, `type` defaults to `sse`.
+ - If `url` is specified and starts with `ws://` or `wss://`, `type` defaults to `websocket`.
+ - If `command` is specified, `type` defaults to `stdio`.
+- **Connection Types:**
+ - **`stdio`**: Starts an MCP server as a child process and communicates via standard input/output.
+ - **`websocket`**: Connects to an external MCP server via WebSocket.
+ - **`sse`**: Connects to an external MCP server via Server-Sent Events (SSE).
+ - **`streamable-http`**: Connects to an external MCP server via HTTP with support for streaming responses.
+- **Internal/Local Addresses:**
+ - **Important**: MCP servers using internal IP addresses (e.g., `172.24.1.165`, `192.168.1.100`), or local domains (e.g., `mcp-server`, `host.docker.internal`) **must** be explicitly allowed in [`mcpSettings.allowedDomains`](/v0.8.4/docs/configuration/librechat_yaml/object_structure/mcp_settings).
+ - See [MCP Settings](/v0.8.4/docs/configuration/librechat_yaml/object_structure/mcp_settings) for configuration details.
+
+## Examples
+
+### Configuration with Internal Addresses
+
+When using internal/local MCP servers, you must configure `mcpSettings.allowedDomains`:
+
+```yaml filename="Complete MCP Configuration with Internal Servers"
+# MCP Settings - Required for internal/local addresses
+mcpSettings:
+ allowedDomains:
+ - "172.24.1.165" # Internal IP
+ - "mcp-prod" # Docker container
+ - "host.docker.internal" # Docker host
+
+# MCP Servers - Individual configurations
+mcpServers:
+ prod-mcp:
+ type: streamable-http
+ url: http://172.24.1.165:8000/mcp
+ timeout: 120000
+
+ test-mcp:
+ type: streamable-http
+ url: http://mcp-prod:8001/mcp
+ timeout: 120000
+```
+
+### `stdio` MCP Server
+
+```yaml filename="stdio MCP Server"
+puppeteer:
+ type: stdio
+ command: npx
+ args:
+ - -y
+ - "@modelcontextprotocol/server-puppeteer"
+ timeout: 30000
+ initTimeout: 10000
+ env:
+ NODE_ENV: "production"
+ USER_EMAIL: "{{LIBRECHAT_USER_EMAIL}}"
+ USER_ROLE: "{{LIBRECHAT_USER_ROLE}}"
+ stderr: inherit
+```
+
+### `sse` MCP Server
+
+```yaml filename="sse MCP Server"
+everything:
+ url: http://localhost:3001/sse
+ headers:
+ X-User-ID: "{{LIBRECHAT_USER_ID}}"
+ X-API-Key: "${SOME_API_KEY}"
+```
+
+### `websocket` MCP Server
+
+```yaml filename="websocket MCP Server"
+myWebSocketServer:
+ url: ws://localhost:8080
+```
+
+### `streamable-http` MCP Server
+
+```yaml filename="streamable-http MCP Server"
+streamable-http-server:
+ type: streamable-http
+ url: https://example.com/api/
+ headers:
+ X-User-ID: "{{LIBRECHAT_USER_ID}}"
+ X-API-Key: "${SOME_API_KEY}"
+```
+
+### MCP Server with Dynamic User Fields
+
+```yaml filename="MCP Server with User Fields"
+user-aware-server:
+ type: sse
+ url: https://api.example.com/users/{{LIBRECHAT_USER_USERNAME}}/stream
+ headers:
+ X-User-ID: "{{LIBRECHAT_USER_ID}}"
+ X-User-Email: "{{LIBRECHAT_USER_EMAIL}}"
+ X-User-Role: "{{LIBRECHAT_USER_ROLE}}"
+ X-Email-Verified: "{{LIBRECHAT_USER_EMAILVERIFIED}}"
+ Authorization: "Bearer ${API_TOKEN}"
+```
+
+### MCP Server with Per-User Credentials via `customUserVars`
+
+```yaml filename="MCP Server with customUserVars"
+my-mcp-server:
+ type: streamable-http
+ url: "https://api.example-service.com/api/" # Example URL
+ headers:
+ X-Auth-Token: "{{API_KEY}}" # Uses the API_KEY defined below
+ customUserVars:
+ API_KEY: # This key will be used as {{API_KEY}} in headers/url
+ title: "API Key" # This is the label shown above the input field
+ description: "Get your API key here." # This description appears below the input
+```
+
+ **NOTE** See [MCP Server Initialization](/v0.8.4/docs/features/mcp#server-initialization) for more information about UI based server initialization.
+
+### MCP Server with Custom Icon
+
+```yaml filename="MCP Server with Icon"
+filesystem:
+ command: npx
+ args:
+ - -y
+ - "@modelcontextprotocol/server-filesystem"
+ - /home/user/LibreChat/
+ iconPath: /home/user/LibreChat/client/public/assets/logo.svg
+ chatMenu: false # Exclude from chatarea dropdown
+```
+
+### MCP Server with OAuth Authentication
+
+```yaml filename="MCP Server with OAuth"
+oauth-api-server:
+ type: streamable-http
+ url: https://api.example.com/mcp/
+ oauth:
+ authorization_url: https://api.example.com/oauth/authorize
+ token_url: https://api.example.com/oauth/token
+ client_id: your_client_id
+ client_secret: your_client_secret
+ redirect_uri: http://localhost:3080/api/mcp/oauth-api-server/oauth/callback
+ scope: "read execute"
+```
+
+### MCP Server with Server Instructions
+
+```yaml filename="MCP Server with Instructions"
+# Server that uses its own provided instructions
+web-search:
+ type: streamable-http
+ url: https://example.com/mcp/search
+ serverInstructions: true
+
+# Server with instructions explicitly disabled
+filesystem:
+ command: npx
+ args:
+ - -y
+ - "@modelcontextprotocol/server-filesystem"
+ - /home/user/documents/
+ serverInstructions: false
+
+# Server with custom instructions
+puppeteer:
+ type: stdio
+ command: npx
+ args:
+ - -y
+ - "@modelcontextprotocol/server-puppeteer"
+ serverInstructions: |
+ Browser automation security and best practices:
+ 1. Be cautious with local file access and internal IP addresses
+ 2. Take screenshots to verify successful page interactions
+ 3. Wait for page elements to load before interacting with them
+ 4. Use specific CSS selectors for reliable element targeting
+ 5. Check console logs for JavaScript errors when troubleshooting
+```
+
+### OAuth-Enabled MCP Server (Legacy requiresOAuth)
+
+```yaml filename="OAuth-Enabled MCP Server"
+composio-googlesheets:
+ type: sse
+ url: https://mcp.composio.dev/googlesheets/sse-endpoint
+ requiresOAuth: true
+ headers:
+ X-User-ID: "{{LIBRECHAT_USER_ID}}"
+ X-API-Key: "${COMPOSIO_API_KEY}"
+ timeout: 45000
+ initTimeout: 15000
+```
+
+**Related Environment Variables (Optional):**
+```bash
+# OAuth configuration for MCP servers
+MCP_OAUTH_ON_AUTH_ERROR=true
+MCP_OAUTH_DETECTION_TIMEOUT=10000
+
+# API key for the service
+COMPOSIO_API_KEY=your_composio_api_key_here
+```
+
+---
+
+**Importing MCP Server Configurations**
+
+The `mcpServers` configurations allow LibreChat to dynamically interact with various MCP servers, which can perform specialized tasks or provide specific functionalities within the application. This modular approach facilitates extending the application's capabilities by simply adding or modifying server configurations.
+
+---
+
+## Additional Information
+
+- **Default Behavior:**
+ - Initialization happens at startup, and the app must be restarted for changes to take effect.
+ - If both `url` and `command` are specified, the `type` must be explicitly defined to avoid ambiguity.
+- **Multi-User Support:**
+ - The MCPManager now supports distinct user-level and app-level connections, enabling proper connection management per user.
+ - User connections are tracked and managed separately, with proper establishment and cleanup.
+ - Use dynamic user field placeholders in headers, URLs, and environment variables:
+ - `{{LIBRECHAT_USER_ID}}` - User's unique identifier
+ - `{{LIBRECHAT_USER_EMAIL}}` - User's email address
+ - `{{LIBRECHAT_USER_USERNAME}}` - User's username
+ - `{{LIBRECHAT_USER_ROLE}}` - User's role (e.g., "user", "admin")
+ - And many more fields (see headers section for complete list)
+- **User Idle Management:**
+ - User connections are monitored for activity and will be disconnected after 15 minutes of inactivity.
+- **Environment Variables:**
+ - **In `env` (for `stdio` type):** Useful for setting up specific runtime environments or configurations required by the MCP server process.
+ - **In `headers` (for `sse` and `streamable-http` types):** Use `${ENV_VAR}` syntax to reference environment variables in header values.
+- **Dynamic User Fields:**
+ - User field placeholders are replaced at runtime with the authenticated user's information
+ - Only non-sensitive fields are available (passwords and other sensitive data are excluded)
+ - Missing fields default to empty strings
+ - Boolean fields are converted to string representations ("true" or "false")
+- **Error Handling (`stderr`):**
+ - Configuring `stderr` allows you to manage how error messages from the MCP server process are handled. The default `"inherit"` means that the errors will be printed to the parent process's `stderr`.
+- **Server Instructions:**
+ - Instructions are automatically injected into the agent's system message when MCP server tools are used
+ - Custom instructions (string values) take precedence over server-provided instructions
+ - Multiple MCP servers can each contribute their own instructions to the agent context
+ - Instructions are only included when the corresponding MCP server's tools are actually available to the agent
+- **OAuth Authentication:**
+ - OAuth2 flow is supported for secure authentication with MCP servers
+ - Users will be prompted to authenticate via OAuth before the MCP server can be used
+
+## References
+
+- [Model Context Protocol (MCP) Documentation](https://github.com/modelcontextprotocol)
+- [MCP Transports Specification](https://modelcontextprotocol.io/specification/draft/basic/transports)
+- [Node.js child_process.spawn](https://nodejs.org/api/child_process.html#child_processspawncommand-args-options)
+
+---
+
+By properly configuring the `mcpServers` in your `librechat.yaml`, you can enhance LibreChat's functionality and integrate custom tools and services seamlessly.
diff --git a/content/docs-archive/v0.8.4/configuration/librechat_yaml/object_structure/mcp_settings.mdx b/content/docs-archive/v0.8.4/configuration/librechat_yaml/object_structure/mcp_settings.mdx
new file mode 100644
index 000000000..3121c351d
--- /dev/null
+++ b/content/docs-archive/v0.8.4/configuration/librechat_yaml/object_structure/mcp_settings.mdx
@@ -0,0 +1,116 @@
+---
+title: "MCP Settings Object Structure"
+icon: Blocks
+---
+
+## Overview
+
+The `mcpSettings` configuration provides global settings for MCP (Model Context Protocol) server security and behavior. This configuration is separate from `mcpServers` and controls how MCP servers can connect to certain domains and IP addresses.
+
+## Example
+
+```yaml filename="MCP Settings Object Structure"
+# Example MCP Settings Configuration
+mcpSettings:
+ allowedDomains:
+ - "example.com" # Specific domain
+ - "*.example.com" # All subdomains using wildcard
+ - "mcp-server" # Local Docker domain
+ - "172.24.1.165" # Internal network IP
+ - "https://api.example.com:8443" # With protocol and port
+```
+
+## Configuration
+
+### Subkeys
+
+
+
+
+
+
+```
+
+### How to Upload Images and Videos on GitHub
+
+
+
+
+
+
+Hello
+}
+```
+````
diff --git a/content/docs-archive/v0.8.4/features/agents.mdx b/content/docs-archive/v0.8.4/features/agents.mdx
new file mode 100644
index 000000000..d10e567ad
--- /dev/null
+++ b/content/docs-archive/v0.8.4/features/agents.mdx
@@ -0,0 +1,476 @@
+---
+title: Agents
+icon: Bot
+description: Learn how to create, customize, and leverage LibreChat's AI Agents - a powerful framework for building custom AI assistants with any model provider.
+---
+
+# Agents: Build Custom AI Assistants
+
+LibreChat's AI Agents feature provides a flexible framework for creating custom AI assistants powered by various model providers.
+
+This feature is similar to OpenAI's Assistants API and ChatGPT's GPTs, but with broader model support and a no-code implementation, letting you build sophisticated assistants with specialized capabilities.
+
+## Getting Started
+
+To create a new agent, select "Agents" from the endpoint menu and open the Agent Builder panel found in the Side Panel.
+
+
+
+The creation form includes:
+
+- **Avatar**: Upload a custom avatar to personalize your agent
+- **Name**: Choose a distinctive name for your agent
+- **Description**: Optional details about your agent's purpose
+- **Instructions**: System instructions that define your agent's behavior
+- **Model**: Select from available providers and models
+
+**Existing agents can be selected from the top dropdown of the Side Panel.**
+- **Also by mention with "@" in the chat input.**
+
+
+
+### Model Configuration
+
+The model parameters interface allows fine-tuning of your agent's responses:
+
+- Temperature (0-1 scale for response creativity)
+- Max context tokens
+- Max output tokens
+- Additional provider-specific settings
+
+## Agent Capabilities
+
+> **Note:** All capabilities can be toggled via the `librechat.yaml` configuration file. See [docs/configuration/librechat_yaml/object_structure/agents#capabilities](/v0.8.4/docs/configuration/librechat_yaml/object_structure/agents#capabilities) for more information.
+
+### Code Interpreter
+
+When enabled, the Code Interpreter capability allows your agent to:
+- Execute code in multiple languages, including:
+ - Python, JavaScript, TypeScript, Go, C, C++, Java, PHP, Rust, and Fortran
+- Process files securely through the LibreChat Code Interpreter API
+- Run code without local setup, configuration, or sandbox deployment
+- Handle file uploads and downloads seamlessly
+- [More info about the Code Interpreter API](/v0.8.4/docs/features/code_interpreter)
+ - **Requires an API Subscription from [code.librechat.ai](https://code.librechat.ai/pricing)**
+
+### File Search
+
+The File Search capability enables:
+- RAG (Retrieval-Augmented Generation) functionality
+- Semantic search across uploaded documents
+- Context-aware responses based on file contents
+- File attachment support at both agent and chat thread levels
+
+### File Context
+
+The File Context capability allows your agent to store extracted text from files as part of its system instructions:
+
+- Extract text while maintaining document structure and formatting
+- Process complex layouts including multi-column text and mixed content
+- Handle tables, equations, and other specialized content
+- Work with multilingual content
+- Text is stored in the agent's instructions in the database
+- **No OCR service required** - Uses text parsing by default with fallback methods
+- **Enhanced by OCR** - If OCR is configured, extraction quality improves for images and scanned documents
+- Uses the same processing logic as "Upload as Text": **OCR > STT > text parsing**
+- [More info about OCR configuration](/v0.8.4/docs/features/ocr)
+
+**Note:** File Context includes extracted text in the agent's system instructions. For temporary document questions in individual conversations, use [Upload as Text](/v0.8.4/docs/features/upload_as_text) from the chat instead.
+
+### Model Context Protocol (MCP)
+
+MCP is an open protocol that standardizes how applications provide context to Large Language Models (LLMs), acting like a universal adapter for AI tools and data sources.
+
+For more information, see documentation on [MCP](/v0.8.4/docs/features/mcp).
+
+#### Agents with MCP Tools
+
+
+1. Configure MCP servers in your `librechat.yaml` file
+2. Restart LibreChat to initialize the connections
+3. Create or edit an agent
+4. Click the "Add Tools" button in the Agent Builder panel to open the Tools Dialog shown below
+5. Select the MCP server(s) you want to add - each server appears as a single entry
+6. Save your changes to the agent
+
+In this example, we've added the **[Spotify MCP server](https://github.com/LibreChat-AI/spotify-mcp)** to an agent.
+
+
+
+#### Managing MCP Tools
+
+Once an MCP server is added to an agent, you can fine-tune which specific tools are available:
+
+- After adding an MCP server, expand it to see all available tools
+- Check/uncheck individual tools as needed
+- For example, the Spotify MCP server provides ~20 tools (search, playback control, playlist management, etc.)
+- This granular control lets you limit agents to only the tools they need
+
+
+
+Learn More:
+- [Configuring MCP Servers](/v0.8.4/docs/features/mcp)
+- [Model Context Protocol Introduction](https://modelcontextprotocol.io/introduction)
+
+### Deferred Tools
+
+Deferred tools allow agents to have access to many MCP tools without loading them all into the LLM context upfront. Instead, deferred tools are discoverable at runtime via a **Tool Search** mechanism.
+
+This is especially useful when an agent has access to many MCP servers with dozens of tools—loading them all would consume a large portion of the context window and degrade response quality.
+
+**How it works:**
+- Tools marked as "deferred" are excluded from the initial LLM context
+- A `ToolSearch` tool is automatically added, allowing the LLM to discover and load deferred tools on demand
+- Once discovered, the tool is available for the rest of the conversation
+
+**Configuring deferred tools:**
+1. Open the Agent Builder and add MCP tools
+2. Click the dropdown on any MCP tool
+3. Toggle "Defer Loading" — deferred tools show a clock icon
+
+**Note:** The `deferred_tools` capability is enabled by default. It can be toggled via the [`librechat.yaml` agents configuration](/v0.8.4/docs/configuration/librechat_yaml/object_structure/agents#capabilities).
+
+{/*
+### Programmatic Tool Calling
+
+**Note:** this feature is still in private beta and not accessible to all users.
+
+Programmatic Tool Calling (PTC) allows MCP tools to be executed via code in a sandbox environment rather than being called directly by the LLM. This enables more complex tool orchestration—for example, calling multiple tools in sequence, processing results with code, or building dynamic workflows.
+
+**How it works:**
+- Tools marked for "code execution" calling are routed through the Code Interpreter sandbox
+- The LLM writes code that calls the tools programmatically, allowing for loops, conditionals, and data transformations
+- Results flow back through the sandbox to the LLM
+
+**Configuring programmatic tools:**
+1. Open the Agent Builder and add MCP tools
+2. Click the dropdown on any MCP tool
+3. Toggle "Code Execution" calling — programmatic tools show a code icon
+
+**Note:** The `programmatic_tools` capability is **disabled by default** and requires the latest [Code Interpreter API](/v0.8.4/docs/features/code_interpreter). It can be enabled via the [`librechat.yaml` agents configuration](/v0.8.4/docs/configuration/librechat_yaml/object_structure/agents#capabilities).
+*/}
+
+### Artifacts
+
+The Artifacts capability enables your agent to generate and display interactive content:
+
+- Create React components, HTML code, and Mermaid diagrams
+- Display content in a separate UI window for clarity and interaction
+- Configure artifact-specific instructions at the agent level
+- [More info about Artifacts](/v0.8.4/docs/features/artifacts)
+
+When enabled, additional instructions specific to the use of artifacts are added by default. Options include:
+
+- **Enable shadcn/ui instructions**: Adds instructions for using shadcn/ui components (a collection of re-usable components built using Radix UI and Tailwind CSS)
+- **Custom Prompt Mode**: When enabled, the default artifacts system prompt will not be included, allowing you to provide your own custom instructions
+
+Configuring artifacts at the agent level is the preferred approach, as it allows for more granular control compared to the legacy app-wide configuration.
+
+If you enable Custom Prompt Mode, you should include at minimum the basic artifact format in your instructions.
+
+Here's a simple example of the minimum instructions needed:
+
+````md
+When creating content that should be displayed as an artifact, use the following format:
+
+:::artifact{identifier="unique-identifier" type="mime-type" title="Artifact Title"}
+```
+Your artifact content here
+```
+:::
+
+For the type attribute, use one of:
+- "text/html" for HTML content
+- "application/vnd.mermaid" for Mermaid diagrams
+- "application/vnd.react" for React components
+- "image/svg+xml" for SVG images
+````
+
+### Tools
+
+Agents can also be enhanced with various built-in tools:
+
+- **[OpenAI Image Tools](/v0.8.4/docs/features/image_gen#1--openai-image-tools-recommended)**: Image generation & editing using **[GPT-Image-1](https://platform.openai.com/docs/models/gpt-image-1)**
+- **[DALL-E-3](/v0.8.4/docs/features/image_gen#2--dalle-legacy)**: Image generation from text descriptions
+- **[Stable Diffusion](/v0.8.4/docs/features/image_gen#3--stable-diffusion-local)** / **[Flux](/v0.8.4/docs/features/image_gen#4--flux)**: Text-to-image generation
+- **[Wolfram](/v0.8.4/docs/configuration/tools/wolfram)**: Computational and mathematical capabilities
+- **[OpenWeather](/v0.8.4/docs/configuration/tools/openweather)**: Weather data retrieval
+- **[Google Search](/v0.8.4/docs/configuration/tools/google_search)**: Access to web search functionality
+- **Calculator**: Mathematical calculations
+- **Tavily Search**: Advanced search API with diverse data source integration
+- **Azure AI Search**: Information retrieval
+- **Traversaal**: A robust search API for LLM Agents
+
+- Tools can be disabled using the [`librechat.yaml`](/v0.8.4/docs/configuration/librechat_yaml) configuration file:
+ - [More info](/v0.8.4/docs/configuration/librechat_yaml/object_structure/agents#capabilities)
+
+### Actions
+
+With the Actions capability, you can dynamically create tools from [OpenAPI specs](https://swagger.io/specification/) to add to your Agents.
+
+
+
+**Clicking the button above will open a form where you can input the OpenAPI spec URL and create an action:**
+
+
+
+- Actions can be disabled using the [`librechat.yaml`](/v0.8.4/docs/configuration/librechat_yaml) configuration file:
+ - [More info](/v0.8.4/docs/configuration/librechat_yaml/object_structure/agents#capabilities)
+- Individual domains can be whitelisted for agent actions:
+ - [More info](/v0.8.4/docs/configuration/librechat_yaml/object_structure/actions#alloweddomains)
+- Note that you can add add the 'x-strict': true flag at operation-level in the OpenAPI spec for actions.
+If using an OpenAI model supporting it, this will automatically generate function calls with 'strict' mode enabled.
+ - Strict mode supports only a partial subset of json. Read https://platform.openai.com/docs/guides/structured-outputs/some-type-specific-keywords-are-not-yet-supported for details.
+
+### Agent Chain
+
+The Agent Chain capability enables a Mixture-of-Agents (MoA) approach, allowing you to create a sequence of agents that work together:
+
+- Create chains of specialized agents for complex tasks
+- Each agent in the chain can access outputs from previous agents
+- Configure the maximum number of steps for the agent chain
+- **Note:** Access this feature from the Advanced Settings panel in the Agent Builder
+- **Note:** This feature is currently in beta and may be subject to change
+ - The current maximum of agents that can be chained is 10, but this may be configurable in the future
+
+
+
+This feature introduces a layered Mixture-of-Agents architecture to LibreChat, where each agent takes all the outputs from agents in the previous layer as auxiliary information in generating its response, as described in [the eponymous "Mixture-of-Agents" paper](https://arxiv.org/abs/2406.04692).
+
+### Advanced Settings
+
+Advanced settings for your agent (found in the Advanced view of the Agent form) outside of "capabilities."
+
+#### Max Agent Steps
+
+This setting allows you to limit the number of steps an agent can take in a "run," which refers to the agent loop before a final response is given.
+
+If left unconfigured, the default is 25 steps, but you can adjust this to suit your needs. For admins, you can set a global default as well as a global maximum in the [`librechat.yaml`](/v0.8.4/docs/configuration/librechat_yaml/object_structure/agents#recursionlimit) file.
+
+A "step" refers to either an AI API request or a round of tool usage (1 or many tools, depending on how many tool calls the LLM provides from a single request).
+
+A single, non-tool response is 1 step. A singular round of tool usage is usually 3 steps:
+
+1. API Request -> 2. Tool Usage (1 or many tools) -> 3. Follow-up API Request
+
+## File Management
+
+Agents support multiple ways to work with files:
+
+### In Chat Interface
+
+When chatting with an agent, you have four upload options:
+
+1. **Upload Images**
+ - Uploads images for native vision model support
+ - Sends images directly to the model provider
+
+2. **Upload as Text** (requires `context` capability)
+ - Extracts and includes full document content in conversation
+ - Uses text parsing by default; enhanced by OCR if configured
+ - Content exists only in current conversation
+ - See [Upload as Text](/v0.8.4/docs/features/upload_as_text)
+
+3. **Upload for File Search** (requires `file_search` capability, toggled ON)
+ - Uses semantic search (RAG) with vector stores
+ - Returns relevant chunks via tool use
+ - Optimal for large documents/multiple files
+ - Sub-optimal for structured data (CSV, Excel, JSON, etc.)
+
+4. **Upload for Code Interpreter** (requires `execute_code` capability, toggled ON)
+ - Adds files to code interpreter environment
+ - Optimal for structured data (CSV, Excel, JSON, etc.)
+ - More info about [Code Interpreter](/v0.8.4/docs/features/code_interpreter)
+
+### In Agent Builder
+
+When configuring an agent, you can attach files in different categories:
+
+1. **Image Upload**: For visual content the agent can reference
+2. **File Search Upload**: Documents for RAG capabilities
+3. **Code Interpreter Upload**: Files for code processing
+4. **File Context**: Documents with extracted text to supplement agent instructions
+
+**File Context** uses the `context` capability and works just like ["Upload as Text"](/v0.8.4/docs/features/upload_as_text) - it uses text parsing by default and is enhanced by OCR when configured. Text is extracted at upload time and stored in the agent's instructions. This is ideal for giving agents persistent knowledge from documents, PDFs, code files, or images with text.
+
+**Processing priority:** OCR > STT > text parsing (same as Upload as Text)
+
+**Note:** The extracted text is included as part of the agent's system instructions.
+
+## Sharing and Permissions
+
+### Administrator Controls
+
+Administrators have access to global permission settings within the agent builder UI:
+
+- Enable/disable agent sharing across all users
+- Control agent usage permissions
+- Manage agent creation rights
+- Configure platform-wide settings
+
+The first account created for your instance is an administrator. If you need to add an additional administrator, you may [access MongoDB](/v0.8.4/docs/configuration/mongodb/mongodb_auth) and update the user's profile:
+
+```
+db.users.updateOne(
+ { email: 'USER_EMAIL_ADDRESS' },
+ { $set: { role: 'ADMIN' } }
+)
+```
+
+The use of agents for all users can also be disabled via config, [more info](/v0.8.4/docs/configuration/librechat_yaml/object_structure/interface).
+
+### User-Level Sharing
+
+Individual users can:
+- Share their agents with all users (if enabled)
+- Control editing permissions for shared agents
+- Manage access to their created agents
+
+### Notes
+
+- Instructions, model parameters, attached files, and tools are only exposed to the user if they have editing permissions
+ - An agent may leak any attached data, whether instructions or files, through conversation--make sure your instructions are robust against this
+- Only original authors and administrators can delete shared agents
+- Agents are private to authors unless shared
+
+## Optional Configuration
+
+LibreChat allows admins to configure the use of agents via the [`librechat.yaml`](/v0.8.4/docs/configuration/librechat_yaml) file:
+
+- Disable Agents for all users (including admins): [more info](/v0.8.4/docs/configuration/librechat_yaml/object_structure/interface)
+- Customize agent capabilities using: [more info](/v0.8.4/docs/configuration/librechat_yaml/object_structure/agents)
+
+## Best Practices
+
+- Provide clear, specific instructions for your agent
+- Carefully consider which tools are necessary for your use case
+- Organize files appropriately across the four upload categories
+- Review permission settings before sharing agents
+- Test your agent thoroughly before deploying to other users
+
+## Recap
+
+1. Select "Agents" from the endpoint dropdown menu
+2. Open the Agent Builder panel
+3. Fill out the required agent details
+4. Configure desired capabilities (Code Interpreter, File Search, File Context, etc.)
+5. Add necessary tools and files
+6. Set sharing permissions if desired
+7. Create and start using your agent
+
+When chatting with agents, you can:
+- Use "Upload as Text" to include full document content in conversations (text parsing by default, enhanced by OCR)
+- Use "Upload for File Search" for semantic search over documents (requires RAG API)
+- Add files to agent's "File Context" to included a file's full content as part of the agent's system instructions
+
+## Migration Required (v0.8.0-rc3+)
+
+
+
+
+
+## Key Features of LibreChat's Code Artifacts:
+
+- Instant prototyping of websites and UIs with generative AI
+- Effortless creation of dynamic, responsive layouts
+- Interactive learning environment for React and HTML
+- Complex idea visualization using Mermaid diagrams
+- AI-powered intuitive, user-centric design iterations
+- Free and open-source alternative to paid AI tools
+
+Experience the future of UI/UX design and development with LibreChat's generative capabilities. Bring your ideas to life faster than ever before!
+
+## Content-Security-Policy
+
+You may need to need to update your web server's Content-Security-Policy to include `frame-src 'self' https://*.codesandbox.io` in order to load generated HTML apps in the Artifacts panel. This is a dependency of the [sandpack](https://sandpack.codesandbox.io/) library.
+
+## Self-Hosting the Sandpack Bundler
+
+Artifacts in LibreChat use CodeSandbox's Sandpack library to securely render HTML/JS code. By default, LibreChat connects to CodeSandbox's public CDN, which may also transmit telemetry for its usage.
+
+For enhanced privacy, security compliance, or isolated network environments, you can [self-host the bundler.](https://sandpack.codesandbox.io/docs/guides/hosting-the-bundler)
+
+### Why Self-Host the Sandpack Bundler?
+
+[Self-hosting the bundler](https://sandpack.codesandbox.io/docs/guides/hosting-the-bundler) provides several advantages:
+
+- **Privacy & Security**: Keep code execution within your own infrastructure
+- **Reliability**: Remove dependency on external services
+- **Performance**: Reduce latency by hosting the bundler in your network
+- **Compliance**: Meet organizational data handling requirements
+- **Control**: Configure and customize to your specific needs
+
+### Configuration
+
+Once you have a self-hosted bundler set up, simply configure LibreChat to use it by setting the environment variable:
+
+```bash
+# `.env` file
+SANDPACK_BUNDLER_URL=http://your-bundler-url
+```
+
+### General Considerations
+
+Self-hosting the bundler introduces some additional overhead:
+
+- **CORS Configuration**: You'll need to manage cross-origin resource sharing policies
+- **Security Management**: You become responsible for the security of the bundler service
+- **Maintenance**: Updates and patches will need to be applied manually
+- **Resource Requirements**: Additional server resources will be needed to host the bundler
+
+For detailed instructions on setting up and maintaining your self-hosted bundler, refer to the [forked CodeSandbox repository](https://github.com/LibreChat-AI/codesandbox-client) tailored for LibreChat deployment, including the removal of telemetry from Sandpack.
+
+---
+
+AI News 2024: The Original and BEST Open-Source AI Chat Platform, LibreChat Releases Code Artifacts! This Generative UI Tool Can Generate React, HTML & Diagrams Instantly from a Single Prompt in Your Browser with Any LLM, OpenAI, Anthropic, LLAMA, Mistral, DeepSeek Coder & More Thanks to OLLAMA Integration.
+
+#AINews2024 #OpenSourceAI #GenerativeUI #CodeArtifacts #WebDevelopment #ReactJS #LLM #AIPrototyping #DevTools #OLLAMA #LibreChat
diff --git a/content/docs-archive/v0.8.4/features/authentication.mdx b/content/docs-archive/v0.8.4/features/authentication.mdx
new file mode 100644
index 000000000..05f4783b8
--- /dev/null
+++ b/content/docs-archive/v0.8.4/features/authentication.mdx
@@ -0,0 +1,30 @@
+---
+title: Authentication
+icon: Lock
+description: Quick overview of the user authentication system of LibreChat, which offers secure and easy email and social logins.
+---
+
+
+LibreChat has a user authentication system that allows users to sign up and log in securely and easily. The system is scalable and can handle a large number of concurrent users without compromising performance or security.
+
+By default, we have email signup and login enabled, which means users can create an account using their email address and a password. They can also reset their password if they forget it.
+
+Additionally, our system can integrate social logins from various platforms such as Google, GitHub, Discord, OpenID, and more. This means users can log in using their existing accounts on these platforms, without having to create a new account or remember another password.
+
+**For further details, refer to the configuration guides provided here: [Authentication](/v0.8.4/docs/configuration/authentication)**
+
+
+
diff --git a/content/docs-archive/v0.8.4/features/code_interpreter.mdx b/content/docs-archive/v0.8.4/features/code_interpreter.mdx
new file mode 100644
index 000000000..f5c52b99c
--- /dev/null
+++ b/content/docs-archive/v0.8.4/features/code_interpreter.mdx
@@ -0,0 +1,149 @@
+---
+title: Code Interpreter API
+icon: SquareTerminal
+description: Execute code securely and manage files seamlessly with LibreChat's Code Interpreter API
+---
+
+## Introduction
+
+LibreChat's Code Interpreter API provides a secure and hassle-free way to execute code and manage files through a simple API interface. Whether you're using it through LibreChat's Agents or integrating it directly into your applications, the API offers a powerful sandbox environment for running code in multiple programming languages.
+
+
+
+## Subscription
+**Access to this feature requires an [API subscription, get started here](https://code.librechat.ai/pricing).**
+
+## Getting Started
+
+1. Visit [code.librechat.ai](https://code.librechat.ai/pricing) to get your API key
+2. Integrate the API into your application or use it through LibreChat
+3. Start executing code and generating files securely
+
+## Key Features
+
+### Supported Languages
+
+Execute code in multiple programming languages:
+- Python, Node.js (JS/TS), Go, C/C++, Java, PHP, Rust, Fortran, Rscript
+
+### Seamless File Handling
+
+- Upload files for processing
+- Download generated outputs
+- Secure file management
+- Session-based file organization
+
+### Security & Convenience
+
+- Secure sandboxed execution environment
+- No local setup required
+- No server deployment needed
+- No configuration management
+
+## Using the API
+
+### In LibreChat
+
+The API has first-class support in LibreChat through two main methods:
+
+1. **[AI Agents](/v0.8.4/docs/features/agents#code-interpreter)**: Enable Code Interpreter in your agent's configuration to allow it to execute code and process files automatically.
+
+2. **Manual Execution**: Use the "Run Code" button in code blocks within the chat interface, as shown here:
+
+
+
+### Set up API key
+
+- **Per-user setup:** input your API key in LibreChat when prompted (using the above methods)
+- **Global setup:** use `LIBRECHAT_CODE_API_KEY` environment variable in the .env file of your project (provides access to all users)
+
+### Direct API Integration
+
+The Code Interpreter API can be integrated into any application using a simple API key authentication:
+
+1. Get your API key from [code.librechat.ai](https://code.librechat.ai/pricing)
+2. Include the API key in your requests using the `x-api-key` header
+
+### Enterprise
+
+The enterprise plan requires use of the `LIBRECHAT_CODE_BASEURL` environment variable to correspond with the self-hosted instance of the API, along with any generated API keys from the dashboard, used the same way as mentioned above.
+
+## Core Functionality
+
+### Code Execution
+
+- Run code snippets in supported languages
+- Receive stdout/stderr output
+- Get execution statistics (memory usage, CPU time)
+- Handle program arguments
+- Access execution status and results
+
+### File Operations
+
+- Upload input files
+- Download generated outputs
+- List available files
+- Delete unnecessary files
+- Manage file sessions
+
+### Limitations
+- Code cannot access the network
+- Only 10 files can be generated per run
+- Execution limits vary by plan:
+ - **Hobby**:
+ - 256 MB RAM per execution
+ - 25 MB per file upload
+ - 750 requests per month
+ - **Enthusiast**:
+ - 512 MB RAM per execution
+ - 50 MB per file upload
+ - 3,000 requests per month
+ - **Pro**:
+ - 512 MB RAM per execution
+ - 150 MB per file upload
+ - 7,000 requests per month
+- The [Enterprise Plan](https://code.librechat.ai/pricing) provides custom limits and features
+
+## Use Cases
+
+- **Code Testing**: Test code snippets in multiple languages
+- **File Processing**: Transform and analyze files programmatically
+- **AI Applications**: Execute AI-generated code securely
+- **Development Tools**: Build interactive coding environments
+- **Objective Logic**: Verify code logic and correctness, improving AI models
+
+## Why a Paid API?
+
+While LibreChat remains free and open source under the MIT license, the Code Interpreter API is offered as a paid service for several key reasons:
+
+1. **Project Sustainability**: Subscribing to an API plan provides direct support to the project's development, even more effectively than [GitHub Sponsors](https://github.com/sponsors/danny-avila). Your subscription helps ensure LibreChat's continued growth and improvement.
+
+2. **Technical Considerations**: Including code execution capabilities in the core project would add significant complexity and hardware requirements that not all users need. The API service eliminates these concerns while maintaining a lightweight core application.
+
+3. **Managed Service Benefits**:
+ - No complex configuration
+ - Immediate availability
+ - Regular updates and maintenance
+ - Professional support
+ - Secure, sandboxed environment
+
+4. **Intellectual Property Protection**: The Code Interpreter's architecture represents significant innovation in secure, scalable sandbox technology. While similar solutions exist, they often lack the comprehensive security measures and scalability features that make this implementation unique. Keeping this component as a closed-source API helps protect these innovations and ensures the service maintains its high security and performance standards.
+
+Even if you only use code execution occasionally, subscribing helps support LibreChat's development while enhancing your experience with professional-grade features. It's a win-win that keeps the core project free while offering optional advanced capabilities for those who need them.
+
+---
+
+## Conclusion
+
+The Code Interpreter API provides a secure, convenient way to execute code and manage files without the hassle of setting up and maintaining execution environments. Whether you're using it through LibreChat's Agents or integrating it directly into your applications, it offers a robust solution for code execution needs.
+
+For detailed technical specifications and API reference, please visit our [API Documentation](https://code.librechat.ai/docs).
+
+#LibreChat #CodeExecution #API #Development
\ No newline at end of file
diff --git a/content/docs-archive/v0.8.4/features/fork.mdx b/content/docs-archive/v0.8.4/features/fork.mdx
new file mode 100644
index 000000000..d5454cdd2
--- /dev/null
+++ b/content/docs-archive/v0.8.4/features/fork.mdx
@@ -0,0 +1,123 @@
+---
+title: Forking Chats
+icon: GitFork
+description: A guide on how to use the "Fork Messages/Conversations" feature in our app to create new conversations from specific messages with desired behavior.
+---
+
+import Image from 'next/image'
+
+
+ 
+
+
+
+ 
+
+
+
+
+
+### Include related branches:
+This option forks the visible messages, along with related branches; in other words, the direct path to the target message, including branches along the path.
+
+
+
+
+
+
+
+
+
+
+
+### Include all to/from here (default):
+This option forks all messages leading up to the target message, including its neighbors; in other words, all message branches, whether or not they are visible or along the same path, are included.
+
+
+
+
+
+
+
+
+
+
+
+## Additional Options
+
+- **Start fork here:** If checked, forking will commence from this message to the latest message in the conversation, according to the behavior selected above.
+
+
+
+
+
+
+
+
+
+
+
+- **Remember:** Check to remember the options you select for future usage, making it quicker to fork conversations as preferred.
+
+
+
+
+
+
+
+
+
+
+
+- Alternatively you can control the default behavior in the settings menu:
+
+
+
+
+
+
+
+
+
+
diff --git a/content/docs-archive/v0.8.4/features/image_gen.mdx b/content/docs-archive/v0.8.4/features/image_gen.mdx
new file mode 100644
index 000000000..93c917d4c
--- /dev/null
+++ b/content/docs-archive/v0.8.4/features/image_gen.mdx
@@ -0,0 +1,435 @@
+---
+title: Image Generation & Editing
+icon: Image
+description: Comprehensive guide to LibreChat's built-in image generation and editing tools
+---
+
+## Quick Start
+
+Get image generation working in under 5 minutes with OpenAI Image Tools (recommended).
+
+
+
+
+
+
+
+
+Can also ***edit*** the images you upload. | OpenAI API | +| **Gemini Image Tools** | Google's latest image models with context-aware generation. | Gemini API or Vertex AI | +| **DALL·E (3 / 2)** | Legacy OpenAI Image models. | OpenAI API | +| **Stable Diffusion** | Local or self-hosted generation, endless community models. | Automatic1111 API | +| **Flux** | Fast cloud renders, optional fine-tunes. | Flux API | +| **MCP** | Bring-your-own-Image-Generators | MCP server with image output support | + +**Notes:** +- API keys can be omitted in favor of allowing the user to enter their own key from the UI. +- Image Outputs are directly sent to the LLM as part of the immediate chat context following generation. + - The LLM will only get vision context from images attached to user messages, and not from generations/edits, except for immediately after generation. + - See [Image Storage and Handling](#image-storage-and-handling) for more details. +- MCP Server tool image outputs are supported, which may output images similarly to LC's built-in tools. + - Note: MCP servers may or may not use the correct format when outputting images. See details in the [MCP section below](#5--model-context-protocol-mcp). + +--- + +## 1 · OpenAI Image Tools (recommended) + +### Features + +"OpenAI Image Tools" are an agent toolkit made up of 2 separate tools. + +- **Image Generation**: + - **Create** brand-new images from text prompts (no upload required). +- **Image Editing**: + - **Edit** or **remix** the images you just uploaded—change colours, add objects, extend the canvas, etc. +- Both use OpenAI's latest image generation model, **GPT-Image-1**, for superior instruction following, text rendering, detailed editing, real-world knowledge +- See OpenAI's [Image Generation documentation](https://platform.openai.com/docs/guides/image-generation?image-generation-model=gpt-image-1) for more details. + +#### Generation vs. Editing +| Use-case | Invokes | +|----------|---------------| +| "Start from scratch" | **Image Generation** | +| "Use existing image(s)" | **Image Editing** | + +The agent decides which tool to use based on the context: + +- **Image Generation** creates brand new images from text descriptions only +- **Image Editing** modifies or remixes existing images using their image IDs + - These can be images from the current message or previously generated/referenced images + - The LLM keeps track of image IDs as long as they remain in the context window + - Includes the referenced image IDs in the tool output +- Both tools are always available, but the LLM will choose the appropriate one based on the user's request +- Both tools will include the generated image ID in the tool output + +⚠️ **Important** +- Image editing relies on image IDs, which are retained in the chat history. +- When files are uploaded to the current request, their image IDs are added to the context of the LLM before any tokens are generated. +- Previously referenced or generated image IDs can be used for editing, as long as they remain within the context window. +- The LLM can include any relevant image IDs in the `image_ids` array when calling the image editing tool. +- You can also attach previously uploaded images from the side panel without needing to upload them again. + - This also has the added benefit of providing a vision model with the image context, which can be useful for informing the `prompt` for the image editing tool. + +### Parameters + +#### Image Generation +• **prompt** – text description (required) +• **size** – `auto` (default), `1024x1024` (square), `1536x1024` (landscape), or `1024x1536` (portrait) +• **quality** – `auto` (default), `high`, `medium`, or `low` +• **background** – `auto` (default), `transparent`, or `opaque` (transparent requires PNG or WebP format) + +#### Image Editing + +• **image_ids** – array of image IDs to use as reference for editing (required) +• **prompt** – text description of the changes (required) +• **size** – `auto` (default), `1024x1024`, `1536x1024`, `1024x1536`, `256x256`, or `512x512` +• **quality** – `auto` (default), `high`, `medium`, or `low` + +### Setup +Create or reuse an OpenAI key and add to `.env`: + +```bash +IMAGE_GEN_OAI_API_KEY=sk-... +# optional extras +IMAGE_GEN_OAI_BASEURL=https://... +``` + +For Azure OpenAI deployments, you will first need access: https://aka.ms/oai/gptimage1access + +Then, add your corresponding credentials to your `.env` file: + +```bash +IMAGE_GEN_OAI_API_KEY=your-api-key +# optional extras +IMAGE_GEN_OAI_BASEURL=https://deploymentname.openai.azure.com/openai/deployments/gpt-image-1/ +IMAGE_GEN_OAI_AZURE_API_VERSION=2025-04-01-preview +``` + +Then add "OpenAI Image Tools" to your Agent's *Tools* list. + +### Advanced Configuration + +You can customize the tool descriptions and prompt guidance by setting these environment variables: + +```bash +# Image Generation Tool Descriptions +IMAGE_GEN_OAI_DESCRIPTION=... +IMAGE_GEN_OAI_PROMPT_DESCRIPTION=... + +# Image Editing Tool Descriptions +IMAGE_EDIT_OAI_DESCRIPTION=... +IMAGE_EDIT_OAI_PROMPT_DESCRIPTION=... +``` + +### Pricing +See the [GPT-Image-1 pricing page](https://platform.openai.com/docs/models/gpt-image-1) and [Image Generation Documentation](https://platform.openai.com/docs/guides/image-generation?image-generation-model=gpt-image-1#cost-and-latency) for details on costs associated with image generation. + +--- + +## 2 · Gemini Image Tools + +Gemini Image Tools integrate Google's latest image generation models, supporting both text-to-image generation and image context-aware editing. + +### Features + +- **Text-to-Image Generation**: Create high-quality images from detailed text descriptions +- **Image Context Support**: Use existing images as context or inspiration for new generations +- **Image Editing**: Generate new images based on modifications to existing ones (include original image ID) +- **Multiple Models**: Choose between `gemini-2.5-flash-image` (default) or `gemini-3-pro-image-preview` +- **Dual API Support**: Works with both simple Gemini API keys and Google Cloud Vertex AI + +### Parameters + +• **prompt** – Detailed text description of the desired image (required, up to 32,000 characters) +• **image_ids** – Optional array of image IDs to use as visual context for generation + +### Setup + +#### Option 1: Gemini API (Recommended) + +Get an API key from [Google AI Studio](https://aistudio.google.com/app/apikey): + +```bash +GEMINI_API_KEY=your_api_key_here +``` + +#### Option 2: Vertex AI (Enterprise) + +For Google Cloud users with Vertex AI access: + +```bash +GOOGLE_SERVICE_KEY_FILE=/path/to/service-account.json +GOOGLE_CLOUD_LOCATION=us-central1 # optional, default: global +``` + +### Model Selection + +```bash +# Default model (fast and efficient) +GEMINI_IMAGE_MODEL=gemini-2.5-flash-image + +# Higher quality model +GEMINI_IMAGE_MODEL=gemini-3-pro-image-preview +``` + +### Advanced Configuration + +Customize tool descriptions via environment variables: + +```bash +GEMINI_IMAGE_GEN_DESCRIPTION=... +GEMINI_IMAGE_GEN_PROMPT_DESCRIPTION=... +GEMINI_IMAGE_IDS_DESCRIPTION=... +``` + +More details can be found in the dedicated [Gemini Image Gen guide](/v0.8.4/docs/configuration/tools/gemini_image_gen). + +--- + +## 3 · DALL·E (legacy) + +DALL·E provides high-quality image generation using OpenAI's legacy image models. + +### Parameters +• **prompt** – Text description of the desired image (required, up to 4000 characters) +• **style** – `vivid` (hyper-real, dramatic - default) or `natural` (less hyper-real) +• **quality** – `standard` (default) or `hd` +• **size** – `1024x1024` (default/square), `1792x1024` (wide), or `1024x1792` (tall) + +### Setup + +```bash +# Required +DALLE_API_KEY=sk-... # or DALLE3_API_KEY=sk-... + +# Optional +DALLE_REVERSE_PROXY=https://... # Alternative endpoint +DALLE3_BASEURL=https://... # For Azure or custom endpoints +DALLE3_AZURE_API_VERSION=2023-12-01-preview # For Azure deployments +DALLE3_SYSTEM_PROMPT=... # Custom system prompt for DALL·E +``` + +### Advanced Configuration +For Azure OpenAI deployments, configure both the base URL and API version: + +```bash +DALLE3_BASEURL=https://your-resource-name.openai.azure.com/openai/deployments/your-deployment-name +DALLE3_AZURE_API_VERSION=2023-12-01-preview +DALLE3_API_KEY=your-azure-api-key +``` + +Enable the **DALL·E** tool for the Agent and start prompting. + +### Pricing +See the [DALL-E pricing page](https://platform.openai.com/docs/models/dall-e-3) and [Image Generation Documentation](https://platform.openai.com/docs/guides/image-generation?image-generation-model=dall-e-3) for details on costs associated with image generation. + +--- + +## 4 · Stable Diffusion (local) + +Run images entirely on your own machine or server. +Point LibreChat at any Automatic1111 (or compatible) endpoint and you're set. + +### Parameters +• **prompt** – Detailed keywords describing desired elements in the image (required) +• **negative_prompt** – Keywords describing elements to exclude from the image (required) + +The Stable Diffusion implementation uses these default parameters: +- cfg_scale: 4.5 +- steps: 22 +- width: 1024 +- height: 1024 + +These values are currently fixed but provide good results for most use cases. + +### Setup + +```bash +SD_WEBUI_URL=http://127.0.0.1:7860 # URL to your Automatic1111 WebUI +``` + +No API key required—just the reachable URL. + +More details on setting up Automatic1111 can be found in the dedicated [Stable Diffusion guide](/v0.8.4/docs/configuration/tools/stable_diffusion). + +--- + +## 5 · Flux + +Cloud generator with an emphasis on speed and optional fine-tuned models. + +### Features +- Fast cloud-based image generation +- Support for fine-tuned models +- Multiple quality levels and aspect ratios +- Raw mode for less processed, more natural-looking images + +### Parameters +The Flux tool supports three main actions: + +1. **generate** - Create a new image from a text prompt +2. **generate_finetuned** - Create an image using a fine-tuned model +3. **list_finetunes** - List available custom models for the user + +More details can be found in the dedicated [Flux guide](/v0.8.4/docs/configuration/tools/flux#parameters). + +### Setup + +```bash +FLUX_API_KEY=flux_live_... +FLUX_API_BASE_URL=https://api.us1.bfl.ai # default is fine for most users +``` + +Choose the **Flux** tool inside the Agent. Prompts are plain text; one call produces one image. + +### Pricing +See the [Flux pricing page](https://docs.bfl.ml/pricing/) for details on costs associated with image generation. + +--- + +## 6 · Model Context Protocol (MCP) + +Image outputs are supported from MCP servers. + +For example, the [Puppeteer MCP Server](https://github.com/modelcontextprotocol/servers/tree/main/src/puppeteer) can be used to generate screenshots of web pages, which correctly output the image in the expected format and is treated the same as LC's built-in image tools. + +> The examples below assume LibreChat is running outside of Docker, directly using Node.js. The Model Context Protocol is a relatively new framework, and many developers are still learning how to properly serve their systems with uv/node for scalable distribution. + +> As this technology is still emerging, there are currently few image-generating servers available, and many existing ones have yet to adopt the correct response format for images. + +> While many MCP servers do function well within Docker, the following examples do not, or not without more advanced configurations, showcasing some of the current inconsistency between MCP servers. + +```yaml +mcpServers: + puppeteer: + command: npx + args: + - -y + - "@modelcontextprotocol/server-puppeteer" +``` + +The following is an example of an [Image Generation server](https://github.com/GongRzhe/Image-Generation-MCP-Server) that outputs images using [Replicate API](https://replicate.com/account/api-tokens), but returns URLs of the images, which doesn't conform to MCP's image response standard. + +> Note: for this particular server, you need to install the `@gongrzhe/image-gen-server` package globally using npm, i.e. `npm install -g @gongrzhe/image-gen-server`, then point to the package's compiled files as shown below. + +```yaml +mcpServers: + image-gen: + command: "node" + # First, install the package globally using npm: + # `npm install -g @gongrzhe/image-gen-server` + # Then, point to the location of the installed package, + # which you can find by running `npm root -g` + args: + - "{REPLACE_WITH_NODE_MODULES_LOCATION}/@gongrzhe/image-gen-server/build/index.js" + # Example with output from `npm root -g`: + # - "/home/danny/.nvm/versions/node/v20.19.0/lib/node_modules/@gongrzhe/image-gen-server/build/index.js" + env: + # Do not hardcode the API token here, use the environment variable instead + # The following will pick up the token from your .env file or environment + REPLICATE_API_TOKEN: "${REPLICATE_API_TOKEN}" + MODEL: "google/imagen-3" +``` + +--- + +## Image Storage and Handling + +All generated images are: +1. Saved according to the configured [**`fileStrategy`**](/v0.8.4/docs/configuration/librechat_yaml/object_structure/config#filestrategy) +2. Displayed directly in the chat interface +3. Image tool outputs are directly sent to the LLM as part of the immediate chat context following generation. + - This may create issues if you are using an LLM that does not support image inputs. + - There will be an option to disable this behavior on a per-agent-basis in the future. + - These outputs are only directly sent to the LLM upon generation, not on every message. + - To include the image in the chat, you can directly attach it to the message from the side panel. + - To summarize, the LLM will only get vision context from images attached to user messages, and not from generations/edits, except for immediately after generation. + +--- + +## Proxy Support + +All image generation tools support proxy configuration through the `PROXY` environment variable: + +```bash +PROXY=http://proxy-url:port +``` + +## Error Handling +If any of the tools encounter an error, they will return an error message explaining what went wrong. Common issues include: +- Invalid API key +- API unavailability +- Content policy violations +- Proxy/network issues +- Invalid parameters +- Unsupported image payload (see [Image Storage and Handling](#image-storage-and-handling) above) + +--- + +## Prompting + +Though you can customize the prompts for [OpenAI Image Tools](#advanced-configuration) and [DALL·E](#advanced-configuration-1), the following tips inform the default prompts supplied by the tools, which is helpful to know for your own writing/prompting. + +1. Start with the **subject** and **style** (photo, oil painting, etc.). +2. Add **composition** and **camera / medium** ("wide-angle shot of…", "watercolour…"). +3. Mention **lighting & mood** ("golden hour", "dramatic shadows"). +4. Finish with **detail keywords** (textures, colours, expressions). +5. Keep negatives positive—describe what should be included, not what to avoid. + +Example: + +> A cinematic photo of an antique library bathed in warm afternoon sunlight. Tall wooden shelves overflow with leather-bound books, and dust particles shimmer in the light. A single green-shaded banker's lamp illuminates an open atlas on a polished mahogany desk in the foreground. 85 mm lens, shallow depth of field, rich amber tones, ultra-high detail. + +## Related Pages + +
+
+6. Click on the "Import" button and select `conversations.json` file from the extracted archive. It will start importing the conversations.
+7. Shortly you will get a notification that the import is complete.
+
+ 
+
+
+
+ 
+
+
+ 
+
diff --git a/content/docs-archive/v0.8.4/features/index.mdx b/content/docs-archive/v0.8.4/features/index.mdx
new file mode 100644
index 000000000..57c3f4b25
--- /dev/null
+++ b/content/docs-archive/v0.8.4/features/index.mdx
@@ -0,0 +1,7 @@
+---
+title: Overview
+icon: BookOpen
+description: Explore the features of LibreChat, including agents, MCP integration, code execution, multimodal chat, and more.
+---
+
+
+
+
+
+## Overview
+
+This feature enables email-based password reset functionality for your LibreChat server. You can configure it to work with various email services, including Mailgun API, Gmail, and custom mail servers.
+
+## Key Features
+
+- Supports multiple email services:
+ - **Mailgun API** - Recommended for servers that block SMTP ports
+ - **Gmail** and other predefined SMTP services
+ - **Custom mail servers** with advanced SMTP configuration
+- Allows for basic and advanced configuration options
+- Enables secure email-based password reset functionality for your LibreChat server
+
+## Setup Options
+
+- **Mailgun Configuration**: Use Mailgun's API for reliable email delivery, especially useful when SMTP ports are blocked
+- **Basic SMTP Configuration**: Use predefined services like Gmail with minimal configuration
+- **Advanced SMTP Configuration**: Configure generic SMTP services or customize settings for any mail provider
+
+**For detailed setup instructions, refer to the configuration guide: [Email Setup](/v0.8.4/docs/configuration/authentication/email)**
diff --git a/content/docs-archive/v0.8.4/features/rag_api.mdx b/content/docs-archive/v0.8.4/features/rag_api.mdx
new file mode 100644
index 000000000..8b74302f4
--- /dev/null
+++ b/content/docs-archive/v0.8.4/features/rag_api.mdx
@@ -0,0 +1,70 @@
+---
+title: RAG API (Chat with Files)
+icon: Brain
+description: Retrieval-Augmented Generation (RAG) API for document indexing and retrieval using Langchain and FastAPI. This API integrates with LibreChat to provide context-aware responses based on user-uploaded files.
+---
+
+The **RAG (Retrieval-Augmented Generation) API** is a powerful tool that integrates with LibreChat to provide context-aware responses based on user-uploaded files.
+
+It leverages LangChain, PostgresQL + PGVector, and Python FastAPI to index and retrieve relevant documents, enhancing the conversational experience.
+
+**For further details, refer to the configuration guide provided here: [RAG API Configuration](/v0.8.4/docs/configuration/rag_api)**
+
+
+
+---
+
+**Currently, this feature is available through [Agents](/v0.8.4/docs/features/agents), as well as through Custom Endpoints, OpenAI, Azure OpenAI, Anthropic, and Google.**
+
+OpenAI Assistants have their own implementation of RAG through the "Retrieval" capability. Learn more about it [here.](https://platform.openai.com/docs/assistants/tools/knowledge-retrieval)
+
+It will still be useful to implement usage of the RAG API with the Assistants API since OpenAI charges for both file storage, and use of "Retrieval," and will be introduced in a future update.
+
+**Still confused about RAG?** [Read the section I wrote below](#what-is-rag) explaining the general concept in more detail with a link to a helpful video.
+
+## What is RAG?
+
+RAG, or Retrieval-Augmented Generation, is an AI framework designed to improve the quality and accuracy of responses generated by large language models (LLMs). It achieves this by grounding the LLM on external sources of knowledge, supplementing the model's internal representation of information.
+
+
+## Features
+
+- **Document Indexing**: The RAG API indexes user-uploaded files, creating embeddings for efficient retrieval.
+- **Semantic Search**: It performs semantic search over the indexed documents to find the most relevant information based on the user's input.
+- **Context-Aware Responses**: By augmenting the user's prompt with retrieved information, the API enables LibreChat to generate more accurate and contextually relevant responses.
+- **Asynchronous Processing**: The API supports asynchronous operations for improved performance and scalability.
+- **Flexible Configuration**: It allows customization of various parameters such as chunk size, overlap, and embedding models.
+
+### Key Benefits of RAG
+
+1. **Access to up-to-date and reliable facts**: RAG ensures that the LLM has access to the most current and reliable information by retrieving relevant facts from an external knowledge base.
+2. **Transparency and trust**: Users can access the model's sources, allowing them to verify the accuracy of the generated responses and build trust in the system.
+3. **Reduced data leakage and hallucinations**: By grounding the LLM on a set of external, verifiable facts, RAG reduces the chances of the model leaking sensitive data or generating incorrect or misleading information.
+4. **Lower computational and financial costs**: RAG reduces the need for continuous training and updating of the model's parameters, potentially lowering the computational and financial costs of running LLM-powered chatbots in an enterprise setting.
+
+### How RAG Works
+
+RAG consists of two main phases: retrieval and content generation.
+
+1. **Retrieval Phase**: Algorithms search for and retrieve snippets of information relevant to the user's prompt or question from an external knowledge base. In an open-domain, consumer setting, these facts can come from indexed documents on the internet. In a closed-domain, enterprise setting, a narrower set of sources are typically used for added security and reliability.
+2. **Generative Phase**: The retrieved external knowledge is appended to the user's prompt and passed to the LLM. The LLM then draws from the augmented prompt and its internal representation of its training data to synthesize a tailored, engaging answer for the user. The answer can be passed to a chatbot with links to its sources.
+
+### Challenges and Ongoing Research
+
+While RAG is currently one of the best-known tools for grounding LLMs on the latest, verifiable information and lowering the costs of constant retraining and updating, it's not perfect. Some challenges include:
+
+1. **Recognizing unanswerable questions**: LLMs need to be explicitly trained to recognize questions they can't answer based on the available information. This may require fine-tuning on thousands of examples of answerable and unanswerable questions.
+2. **Improving retrieval and generation**: Ongoing research focuses on innovating at both ends of the RAG process: improving the retrieval of the most relevant information possible to feed the LLM, and optimizing the structure of that information to obtain the richest responses from the LLM.
+
+In summary, RAG is a powerful framework that enhances the capabilities of LLMs by grounding them on external, verifiable knowledge. It helps to ensure more accurate, up-to-date, and trustworthy responses while reducing the costs associated with continuous model retraining. As research in this area progresses, we can expect further improvements in the quality and efficiency of LLM-powered conversational AI systems.
+
+For a more detailed explanation of RAG, you can watch this informative video by IBM on Youtube:
+
+
+
+
+## Conclusion
+
+The RAG API is a powerful addition to LibreChat, enabling context-aware responses based on user-uploaded files. By leveraging Langchain and FastAPI, it provides efficient document indexing, retrieval, and generation capabilities. With its flexible configuration options and seamless integration, the RAG API enhances the conversational experience in LibreChat.
+
+For more detailed information on the RAG API, including API endpoints, request/response formats, and advanced configuration, please refer to the official RAG API documentation.
diff --git a/content/docs-archive/v0.8.4/features/resumable_streams.mdx b/content/docs-archive/v0.8.4/features/resumable_streams.mdx
new file mode 100644
index 000000000..f4932dc97
--- /dev/null
+++ b/content/docs-archive/v0.8.4/features/resumable_streams.mdx
@@ -0,0 +1,176 @@
+---
+title: Resumable Streams
+icon: Zap
+description: Never lose an AI response—seamless reconnection, multi-tab sync, and horizontal scaling for production deployments
+---
+
+LibreChat features a resilient streaming architecture that ensures you never lose AI-generated content. Whether your connection drops, you switch tabs, or you pick up on another device, your responses are always preserved and synchronized.
+
+## Why It Matters
+
+Traditional chat applications lose all streaming content when your connection drops. With resumable streams, LibreChat:
+
+- **Preserves every response** — Network hiccups, browser refreshes, or server restarts won't cause data loss
+- **Keeps multiple tabs in sync** — Open the same conversation in two browser tabs and watch them update together in real-time
+- **Enables seamless device switching** — Start a conversation on your desktop and continue on your phone
+- **Lets you multitask freely** — Start a generation, browse other tabs, and come back to a complete response
+
+## How It Works
+
+When you send a message to an AI model, LibreChat creates a generation job that tracks all streamed content. The magic happens when something interrupts your connection:
+
+1. **Automatic detection** — The client detects the disconnection instantly
+2. **State reconstruction** — Upon reconnecting, the server rebuilds all previously streamed content
+3. **Seamless sync** — Missing content is delivered via a sync event
+4. **Transparent continuation** — Streaming resumes from the current position
+
+This all happens automatically—no user action required.
+
+### Multi-Tab & Multi-Device Experience
+
+One of the most powerful aspects of resumable streams is **real-time synchronization**:
+
+- **Same chat, multiple windows** — Open a conversation in two browser tabs and both receive updates simultaneously
+- **Cross-device continuity** — Start a long generation on your laptop, then check the result on your phone
+- **Team collaboration** — In shared conversations, all viewers see content appear in real-time
+
+## Deployment Modes
+
+LibreChat supports two deployment configurations:
+
+### Single-Instance Mode (Default)
+
+Uses in-memory storage with Node.js `EventEmitter` for pub/sub. Perfect for:
+- Local development
+- Single-server deployments
+- Docker Compose setups
+
+**No configuration required** — Works out of the box.
+
+### Redis Mode (Production)
+
+Uses Redis Streams and Pub/Sub for cross-instance communication. Essential for:
+- Horizontally scaled deployments
+- Load-balanced production environments
+- High-availability setups
+- Kubernetes clusters
+
+With Redis mode, a user can start a generation on one server instance and seamlessly resume on another—perfect for rolling deployments and auto-scaling.
+
+**Note:** If you only run a single LibreChat instance, Redis for resumable streams is typically unnecessary—the in-memory mode handles everything. Redis becomes valuable when you have multiple LibreChat instances behind a load balancer. That said, Redis is still useful for other features like caching and session storage even in single-instance deployments.
+
+## Configuration
+
+### Enabling Redis Streams
+
+When Redis is enabled (`USE_REDIS=true`), resumable streams automatically use Redis. You can also explicitly enable it:
+
+```bash filename=".env"
+USE_REDIS=true
+REDIS_URI=redis://localhost:6379
+# Resumable streams will use Redis automatically when USE_REDIS=true
+# To explicitly control it:
+USE_REDIS_STREAMS=true
+```
+
+### Redis Cluster Support
+
+For Redis Cluster deployments:
+
+```bash filename=".env"
+USE_REDIS_STREAMS=true
+USE_REDIS_CLUSTER=true
+REDIS_URI=redis://node1:7001,redis://node2:7002,redis://node3:7003
+```
+
+LibreChat automatically uses hash-tagged keys to ensure multi-key operations stay within the same cluster slot.
+
+## Use Cases
+
+### Unstable Networks
+On spotty WiFi or cellular connections, responses automatically resume when connectivity returns. No need to re-send your prompt.
+
+### Mobile Users
+Switch from WiFi to cellular (or vice versa) without losing your response. The stream picks up exactly where it left off.
+
+### Long-Running Generations
+For complex prompts that generate lengthy responses, feel free to check other tabs or apps. Your response will be waiting when you return.
+
+### Multi-Device Workflows
+Start a conversation on your work computer, commute home, and check the result on your phone—the full response is there.
+
+### Production Deployments
+Scale horizontally across multiple server instances while maintaining stream continuity. Rolling deployments won't interrupt active generations.
+
+## Technical Details
+
+### Content Reconstruction
+
+The system aggregates all streamed delta events to rebuild:
+- Message content (text, tool calls, citations)
+- Agent run steps and intermediate reasoning
+- Metadata and state information
+
+### Performance Optimizations
+
+**Memory-first approach**: When reconnecting to the same server instance, LibreChat uses local cache for zero-latency content recovery, avoiding unnecessary Redis round trips.
+
+**Automatic cleanup**: Stale job entries are removed during queries to prevent memory leaks. Completed streams expire automatically.
+
+**Efficient storage**: In-memory mode uses `WeakRef` for graph storage, enabling automatic garbage collection when conversations end.
+
+### Data Flow
+
+| Component | Storage Mechanism |
+|-----------|-------------------|
+| Chunks | Redis Streams (`XADD`/`XRANGE`) |
+| Job metadata | Redis Hash structures |
+| Real-time events | Redis Pub/Sub channels |
+| Expiration | Automatic TTL after stream completion |
+
+## Testing Resumable Streams
+
+You can verify the feature is working:
+
+1. Start a streaming conversation with any AI model
+2. **Tab test**: Open the same chat in a new browser tab—both should sync
+3. **Disconnect test**: Turn off your network briefly, then reconnect
+4. **Navigation test**: Navigate away mid-stream, then return
+
+In all cases, you should see the complete response with no data loss.
+
+## Troubleshooting
+
+### Streams not resuming?
+
+**Check Redis connectivity:**
+```bash
+docker exec -it librechat-redis redis-cli ping
+# Should return: PONG
+```
+
+**Verify environment variables:**
+```bash
+# Ensure USE_REDIS_STREAMS is set
+echo $USE_REDIS_STREAMS
+```
+
+### Content appears duplicated?
+
+This typically indicates a client version mismatch. Ensure you're running the latest version of LibreChat.
+
+### High memory usage in single-instance mode?
+
+Completed streams are automatically garbage collected. If you're seeing high memory usage, check for:
+- Very long-running streams that haven't completed
+- Streams that errored without proper cleanup
+
+## Related Documentation
+
+- [Redis Configuration](/v0.8.4/docs/configuration/redis) — Setting up Redis for caching and horizontal scaling
+- [Agents](/v0.8.4/docs/features/agents) — AI agents with tool use capabilities
+- [Docker Deployment](/v0.8.4/docs/local/docker) — Container-based deployment guide
+
+---
+
+For implementation details, see [PR #10926](https://github.com/danny-avila/LibreChat/pull/10926).
diff --git a/content/docs-archive/v0.8.4/features/search.mdx b/content/docs-archive/v0.8.4/features/search.mdx
new file mode 100644
index 000000000..c3a215da9
--- /dev/null
+++ b/content/docs-archive/v0.8.4/features/search.mdx
@@ -0,0 +1,19 @@
+---
+title: Message Search
+icon: ListFilter
+description: Quickly search in past conversations with LibreChat's integrated Meilisearch
+---
+
+LibreChat has integrated **Meilisearch** to enhance the user experience by providing a fast and efficient way to search through past conversations. Meilisearch is a powerful, open-source search engine that is known for its speed and ease of use, making it an excellent choice for applications like LibreChat that require quick access to a large volume of data.
+
+
+
+
+
+
+The integration allows users to:
+- Perform **full-text searches** on their conversation history.
+- Utilize **typo-tolerance** for more forgiving search queries.
+- Experience **instant results** as they type, thanks to Meilisearch's as-you-type search capabilities.
+
+This feature significantly improves the functionality of LibreChat, making it easier for users to find specific messages or topics within their chat history. It's a testament to the platform's commitment to providing a seamless and user-friendly experience. For those interested in the technical details or implementation, further information can be found in the [Meilisearch Configuration Guide](/v0.8.4/docs/configuration/meilisearch).
diff --git a/content/docs-archive/v0.8.4/features/shareable_links.mdx b/content/docs-archive/v0.8.4/features/shareable_links.mdx
new file mode 100644
index 000000000..e951657be
--- /dev/null
+++ b/content/docs-archive/v0.8.4/features/shareable_links.mdx
@@ -0,0 +1,185 @@
+---
+title: Shareable Links
+icon: Share2
+description: Share your conversations with others using LibreChat's shareable links feature, complete with QR codes, branching messages, and artifacts support.
+---
+
+import Image from 'next/image'
+
+## Overview
+
+Shareable Links in LibreChat allow you to share your conversations with others through automatically generated links and QR codes. Whether you're collaborating with teammates, showcasing AI interactions, or sharing generated artifacts, this feature makes it easy to allow others to view your conversations with the click of a button.
+
+## Key Features
+
+- **Easy Sharing**: Generate shareable links with just a few clicks
+- **QR Code Generation**: Quickly share conversations via QR codes for mobile access
+- **Conversation Branching**: Recipients can see branched conversations in your shared links
+- **Artifacts Support**: Shared conversations now include generated artifacts and interactive components
+- **Customizable Appearance**: Recipients can adjust language and theme preferences
+- **Link Management**: Centralized dashboard to manage all your shared links
+
+## How to Share a Conversation
+There are two ways to make a conversation shareable:
+
+### Option 1: From the Conversation Menu
+
+
+*Access the share option from the conversation menu*
+
+### Option 2: From the Share Button
+
+
+*Use the dedicated share button in your active conversation*
+
+## Share Link Options
+
+When you create a shareable link, you'll see a modal with several options to customize how your conversation appears to recipients.
+
+
+
+
+### Available Options:
+
+- **Refresh Link**: Generate a new URL for the shared conversation
+- **Generate QR code**: Create and show a QR code for easy mobile access
+- **Copy Link to clipboard**: Copy the shareable URL to your clipboard
+- **Delete Link**: Remove the shared link, revoking access to anyone who has it
+
+## QR Code Feature
+
+Generate QR codes for your shared conversations for easy mobile sharing. Simply scan the code with any smartphone camera to instantly access the conversation.
+
+
+ 
+ *Initial share link creation modal*
+
+
+ 
+ *Shared link configuration modal*
+
+
+
+
+This is particularly useful for:
+- Sharing during presentations
+- Quick mobile access
+- Offline sharing via printed materials
+- Conference or event demonstrations
+
+## Viewing Shared Conversations
+
+When someone opens your shared link, they'll see a clean, focused view of the conversation with all the context you chose to include.
+
+
+*How recipients see your shared conversation*
+
+### Features Available to Recipients:
+
+- The date the shareable link was published
+- Ability to scroll through the entire conversation
+- Access to any included artifacts or generated content
+
+## Branching in Shared Conversations
+
+Conversation branches are preserved in shared links, allowing recipients to explore different conversation paths and see how the discussion evolved.
+
+
+ 
+ *Generate QR codes for instant mobile access to shared conversations*
+
+
+ 
+ *QR code will link to the shared conversation URL*
+
+
+
+
+This feature is essential for:
+- Demonstrating different AI approaches to the same problem
+- Illustrating how solutions and interactions can take multiple different paths depending on user input
+
+## Artifacts in Shared Conversations
+
+All artifacts generated during the conversation are fully functional in shared links, including React components, HTML code, and Mermaid diagrams.
+
+
+*Generated artifacts remain interactive in shared conversations*
+
+Recipients can:
+- View interactive React components
+- See HTML previews
+- Examine Mermaid diagrams
+- Access the underlying code
+- Understand the context in which artifacts were generated
+
+## Customization Options for Recipients
+
+Recipients can customize their viewing experience by adjusting language and theme preferences to match their preferences.
+
+
+*Recipients can customize language and theme preferences*
+
+Available customizations:
+- **Theme selection**: Light, dark, or system preference
+- **Language**: View the interface in their preferred language
+
+## Managing Your Shared Links
+
+Access the Shared Links Management dashboard under the Data Controls section of the Settings menu to view and manage all your shared conversations in one place.
+
+
+ 
+ *Access different conversation branches using the branch navigation arrows*
+
+
+ 
+ *Recipients can navigate through conversation branches in shared links*
+
+
+
+
+### Management Features:
+
+- **View all links**: See a list of all conversations you've shared
+- **Search & filter**: Quickly find and view the content of specific shared links
+- **Revoke access**: Delete links to immediately stop sharing
+
+## Configuration
+
+Shareable links behavior is controlled by the following environment variables in your `.env` file:
+
+- **`ALLOW_SHARED_LINKS`** (default: `true`) — Enables or disables the shared links feature entirely. Set to `false` to prevent users from creating shared links.
+- **`ALLOW_SHARED_LINKS_PUBLIC`** (default: `false`) — Controls whether shared links can be accessed without authentication. By default, recipients must be logged in to view shared conversations. Set to `true` to allow public (unauthenticated) access.
+
+```bash
+# Enable shared links (default)
+ALLOW_SHARED_LINKS=true
+
+# Require authentication to view shared links (default)
+ALLOW_SHARED_LINKS_PUBLIC=false
+```
+
+> **Note:** For full environment variable reference, see the [.env Configuration](/v0.8.4/docs/configuration/dotenv#shared-links) page.
+
+## Frequently Asked Questions
+
+**Q: Can recipients respond to shared conversations?**
+A: No, shared links are read-only. Recipients can view the conversation but cannot add messages or interact with the AI.
+
+**Q: What happens if I delete a conversation after sharing it?**
+A: The shared link will no longer be accessible, and any user which navigates to that link will be served a page stating "Shared link not found".
+
+**Q: Can I edit a conversation after sharing it?**
+A: The shared link captures the conversation at the time of creation. Additional messages will not be reflected in the shared view - however, edits made to the existing messages will be shown.
+
+**Q: Do shared links work offline?**
+A: No, recipients need an internet connection to view shared conversations.
\ No newline at end of file
diff --git a/content/docs-archive/v0.8.4/features/temporary_chat.mdx b/content/docs-archive/v0.8.4/features/temporary_chat.mdx
new file mode 100644
index 000000000..aea135218
--- /dev/null
+++ b/content/docs-archive/v0.8.4/features/temporary_chat.mdx
@@ -0,0 +1,26 @@
+---
+title: Temporary Chat
+icon: Clock
+description: Temporary chats allow users to exclude specific conversations from their chat history, search results, and bookmarks, providing a private and focused experience.
+---
+
+Keep your chat history clean and focused by using temporary chats for sensitive topics, quick experiments, or anything you don't need to permanently save. These chats are excluded from search results, cannot be bookmarked, and are automatically deleted after 30 days.
+
+## Activating Temporary Chat
+
+1. Open the model list dropdown menu located on the top left side of LibreChat.
+2. Toggle the "Temporary Chat" slider to the ON position.
+
+
+
+3. A notification will appear above the chat input area, confirming that Temporary Chat mode is active. Pressing (x) will disable the Temporary Chat.
+
+
+
+
+## What Happens When a Chat is Marked as Temporary?
+
+* Temporary Chats do not appear in the chat history sidebar.
+* Temporary Chats are excluded from search results.
+* Temporary Chats cannot be bookmarked.
+* Temporary Chats are stored in the database for 30 days and then automatically deleted.
diff --git a/content/docs-archive/v0.8.4/features/upload_as_text.mdx b/content/docs-archive/v0.8.4/features/upload_as_text.mdx
new file mode 100644
index 000000000..153b7be2a
--- /dev/null
+++ b/content/docs-archive/v0.8.4/features/upload_as_text.mdx
@@ -0,0 +1,321 @@
+---
+title: Upload Files as Text
+icon: Upload
+description: Upload files to include their full content in conversations without requiring OCR configuration.
+---
+
+Upload as Text allows you to upload documents and have their full content included directly in your conversation with the AI. This feature works out-of-the-box using text parsing methods, with optional OCR enhancement for improved extraction quality.
+
+## Overview
+
+- **No OCR required** - Uses text parsing with fallback methods by default
+- **Enhanced by OCR** - If OCR is configured, extraction quality improves for images and scanned documents
+- **Full document content** - Entire file content available to the model in the conversation
+- **Works with all models** - No special tool capabilities needed
+- **Token limit control** - Configurable via `fileTokenLimit` to manage context usage
+
+## The `context` Capability
+
+Upload as Text is controlled by the `context` capability in your LibreChat configuration.
+
+```yaml
+# librechat.yaml
+endpoints:
+ agents:
+ capabilities:
+ - "context" # Enables "Upload as Text"
+```
+
+**Default:** The `context` capability is included by default. You only need to explicitly add it if you've customized the capabilities list.
+
+## How It Works
+
+When you upload a file using "Upload as Text":
+
+1. LibreChat checks the file MIME type against `fileConfig` patterns
+2. **Processing method determined by precedence: OCR > STT > text parsing**
+3. If file matches `fileConfig.ocr.supportedMimeTypes` AND OCR is configured: **Use OCR**
+4. If file matches `fileConfig.stt.supportedMimeTypes` AND STT is configured: **Use STT**
+5. If file matches `fileConfig.text.supportedMimeTypes`: **Use text parsing**
+6. Otherwise: **Fallback to text parsing**
+7. Text is truncated to `fileConfig.fileTokenLimit` before prompt construction
+8. Full extracted text included in conversation context
+
+### Text Processing Methods
+
+**Text Parsing (Default):**
+- Uses a robust parsing library (same as the RAG API)
+- Handles PDFs, Word docs, text files, code files, and more
+- No external service required
+- Works immediately without configuration
+- Fallback method if no other match
+
+**OCR Enhancement (Optional):**
+- Improves extraction from images, scanned documents, and complex PDFs
+- Requires OCR service configuration
+- Automatically used for files matching `fileConfig.ocr.supportedMimeTypes` when available
+- See [OCR Configuration](/v0.8.4/docs/features/ocr)
+
+**STT Processing (Optional):**
+- Converts audio files to text
+- Requires STT service configuration
+- See [Speech-to-Text Configuration](/v0.8.4/docs/configuration/librechat_yaml/object_structure/file_config#stt)
+
+## Usage
+
+1. Click the attachment icon in the chat input
+2. Select "Upload as Text" from the menu
+3. Choose your file
+4. File content is extracted and included in your message
+
+**Note:** If you don't see "Upload as Text", ensure the `context` capability is enabled in your [`endpoints.agents.capabilities` configuration](/v0.8.4/docs/configuration/librechat_yaml/object_structure/agents#capabilities).
+
+## Configuration
+
+### Basic Configuration
+
+The `context` capability is enabled by default. No additional configuration is required for basic text parsing functionality.
+
+### File Handling Configuration
+
+Control text processing behavior with `fileConfig`:
+
+```yaml
+fileConfig:
+ # Maximum tokens from text files before truncation
+ fileTokenLimit: 100000
+
+ # Files matching these patterns use OCR (if configured)
+ ocr:
+ supportedMimeTypes:
+ - "^image/(jpeg|gif|png|webp|heic|heif)$"
+ - "^application/pdf$"
+ - "^application/vnd\\.openxmlformats-officedocument\\.(wordprocessingml\\.document|presentationml\\.presentation|spreadsheetml\\.sheet)$"
+ - "^application/vnd\\.ms-(word|powerpoint|excel)$"
+ - "^application/epub\\+zip$"
+
+ # Files matching these patterns use text parsing
+ text:
+ supportedMimeTypes:
+ - "^text/(plain|markdown|csv|json|xml|html|css|javascript|typescript|x-python|x-java|x-csharp|x-php|x-ruby|x-go|x-rust|x-kotlin|x-swift|x-scala|x-perl|x-lua|x-shell|x-sql|x-yaml|x-toml)$"
+
+ # Files matching these patterns use STT (if configured)
+ stt:
+ supportedMimeTypes:
+ - "^audio/(mp3|mpeg|mpeg3|wav|wave|x-wav|ogg|vorbis|mp4|x-m4a|flac|x-flac|webm)$"
+```
+
+**Processing Priority:** OCR > STT > text parsing > fallback
+
+For more details, see [File Config Object Structure](/v0.8.4/docs/configuration/librechat_yaml/object_structure/file_config).
+
+### Optional: Configure OCR for Enhanced Extraction
+
+OCR is **not required** but enhances extraction quality when configured:
+
+```yaml
+# librechat.yaml
+ocr:
+ strategy: "mistral_ocr"
+ apiKey: "${OCR_API_KEY}"
+ baseURL: "https://api.mistral.ai/v1"
+ mistralModel: "mistral-ocr-latest"
+```
+
+See [OCR Configuration](/v0.8.4/docs/features/ocr) for full details.
+
+## When to Use Each Upload Option
+
+LibreChat offers three different ways to upload files, each suited for different use cases:
+
+### Use "Upload as Text" when:
+- ✅ You want the AI to read the complete document content
+- ✅ Working with smaller files that fit in context
+- ✅ You need "chat with files" functionality
+- ✅ Using models without tool capabilities
+- ✅ You want direct content access without semantic search
+
+### Use "Upload for File Search" when:
+- ✅ Working with large documents or multiple files
+- ✅ You want to optimize token usage
+- ✅ You need semantic search for relevant sections
+- ✅ Building knowledge bases
+- ✅ The `file_search` capability is enabled and toggled ON
+
+### Use standard "Upload Files" when:
+- ✅ Using vision models to analyze images
+- ✅ Using code interpreter to execute code
+- ✅ Files don't need text extraction
+
+## Supported File Types
+
+### Text Files (text parsing)
+- Plain text, Markdown, CSV, JSON, XML, HTML
+- Programming languages (Python, JavaScript, Java, C++, etc.)
+- Configuration files (YAML, TOML, INI, etc.)
+- Shell scripts, SQL files
+
+### Documents (text parsing or OCR)
+- PDF documents
+- Word documents (.docx, .doc)
+- PowerPoint presentations (.pptx, .ppt)
+- Excel spreadsheets (.xlsx, .xls)
+- EPUB books
+
+### Images (OCR if configured)
+- JPEG, PNG, GIF, WebP
+- HEIC, HEIF (Apple formats)
+- Screenshots, photos of documents, scanned images
+
+### Audio (STT if configured)
+- MP3, WAV, OGG, FLAC
+- M4A, WebM
+- Voice recordings, podcasts
+
+## File Processing Priority
+
+LibreChat processes files based on MIME type matching with the following **priority order**:
+
+1. **OCR** - If file matches `ocr.supportedMimeTypes` AND OCR is configured
+2. **STT** - If file matches `stt.supportedMimeTypes` AND STT is configured
+3. **Text Parsing** - If file matches `text.supportedMimeTypes`
+4. **Fallback** - Text parsing as last resort
+
+### Processing Examples
+
+**PDF file with OCR configured:**
+- Matches `ocr.supportedMimeTypes`
+- **Uses OCR** to extract text
+- Better quality for scanned PDFs
+
+**PDF file without OCR configured:**
+- Matches `text.supportedMimeTypes` (fallback)
+- **Uses text parsing** library
+- Works well for digital PDFs
+
+**Python file:**
+- Matches `text.supportedMimeTypes`
+- **Uses text parsing** (no OCR needed)
+- Direct text extraction
+
+**Audio file with STT configured:**
+- Matches `stt.supportedMimeTypes`
+- **Uses STT** to transcribe
+
+## Token Limits
+
+Files are truncated to `fileTokenLimit` tokens to manage context window usage:
+
+```yaml
+fileConfig:
+ fileTokenLimit: 100000 # Default: 100,000 tokens
+```
+
+- Truncation happens at runtime before prompt construction
+- Helps prevent exceeding model context limits
+- Configurable based on your needs and model capabilities
+- Larger limits allow more content but use more tokens
+
+## Comparison with Other File Features
+
+| Feature | Capability | Requires Service | Persistence | Best For |
+|---------|-----------|------------------|-------------|----------|
+| **Upload as Text** | `context` | No (enhanced by OCR) | Single conversation | Temporary document questions |
+| **Agent File Context** | `context` | No (enhanced by OCR) | Agent system instructions | Specialized agent knowledge |
+| **File Search** | `file_search` | Yes (vector DB) | Stored in vector store | Large documents, semantic search |
+
+### Upload as Text vs Agent File Context
+
+**Upload as Text (`context`):**
+- Available in any chat conversation
+- Content included in current conversation only
+- No OCR service required (text parsing by default)
+- Best for one-off document questions
+
+**Agent File Context (`context`):**
+- Only available in Agent Builder
+- Content stored in agent's system instructions
+- No OCR service required (text parsing by default)
+- Best for creating specialized agents with persistent knowledge
+- See [OCR for Documents](/v0.8.4/docs/features/ocr)
+
+### Upload as Text vs File Search
+
+**Upload as Text (`context`):**
+- Full document content in conversation context
+- Direct access to all text
+- Token usage: entire file (up to limit)
+- Works without RAG API configuration
+
+**File Search (`file_search`):**
+- Semantic search over documents
+- Returns relevant chunks via tool use
+- Token usage: only relevant sections
+- Requires RAG API and vector store configuration
+- See [RAG API](/v0.8.4/docs/features/rag_api)
+
+## Example Use Cases
+
+- **Document Analysis**: Upload contracts, reports, or articles for analysis
+- **Code Review**: Upload source files for review and suggestions
+- **Data Extraction**: Extract information from structured documents
+- **Translation**: Translate document contents
+- **Summarization**: Summarize articles, papers, or reports
+- **Research**: Discuss academic papers or technical documentation
+- **Troubleshooting**: Share log files for analysis
+- **Content Editing**: Review and edit written content
+- **Data Processing**: Work with CSV or JSON data files
+
+## Troubleshooting
+
+### "Upload as Text" option not appearing
+
+**Solution:** Ensure the `context` capability is enabled:
+
+```yaml
+endpoints:
+ agents:
+ capabilities:
+ - "context" # Add this if missing
+```
+
+### File content not extracted properly
+
+**Solutions:**
+1. Check if file type is supported (matches `fileConfig` patterns)
+2. For images/scanned documents: Configure OCR for better extraction
+3. For audio files: Configure STT service
+4. Verify file is not corrupted
+
+### Content seems truncated
+
+**Solution:** Increase the token limit:
+
+```yaml
+fileConfig:
+ fileTokenLimit: 150000 # Increase as needed
+```
+
+### Poor extraction quality from images
+
+**Solution:** Configure OCR to enhance extraction:
+
+```yaml
+ocr:
+ strategy: "mistral_ocr"
+ apiKey: "${OCR_API_KEY}"
+```
+
+See [OCR Configuration](/v0.8.4/docs/configuration/librechat_yaml/object_structure/ocr) for details.
+
+## Related Features
+
+- [File Context](/v0.8.4/docs/features/agents#file-context) - Files used as Agent Context
+- [OCR for Documents](/v0.8.4/docs/features/ocr) - Learn about and configure OCR services
+- [File Configuration](/v0.8.4/docs/configuration/librechat_yaml/object_structure/file_config) - Configure file handling
+
+---
+
+Upload as Text provides a simple, powerful way to work with documents in LibreChat without requiring complex configuration or external services.
+
+
diff --git a/content/docs-archive/v0.8.4/features/url_query.mdx b/content/docs-archive/v0.8.4/features/url_query.mdx
new file mode 100644
index 000000000..4a08f05b3
--- /dev/null
+++ b/content/docs-archive/v0.8.4/features/url_query.mdx
@@ -0,0 +1,255 @@
+---
+title: Query Parameters
+icon: Link
+description: Learn how to configure chat conversations using URL query parameters in LibreChat. Set models, endpoints, and conversation settings dynamically.
+---
+
+LibreChat supports dynamic configuration of chat conversations through URL query parameters. This feature allows you to initiate conversations with specific settings, models, and endpoints directly from the URL.
+
+### Chat Paths
+
+Query parameters must follow a valid chat path:
+- For new conversations: `/c/new?`
+- For existing conversations: `/c/[conversation-id]?` (where conversation-id is an existing one)
+
+Examples:
+
+```bash
+https://your-domain.com/c/new?endpoint=ollama&model=llama3%3Alatest
+https://your-domain.com/c/03debefd-6a50-438a-904d-1a806f82aad4?endpoint=openAI&model=o1-mini
+```
+
+## Basic Usage
+
+The most common parameters to use are `endpoint` and `model`. Using both is recommended for the most predictable behavior:
+
+```bash
+https://your-domain.com/c/new?endpoint=azureOpenAI&model=o1-mini
+```
+
+### URL Encoding
+
+Special characters in query params must be properly URL-encoded to work correctly. Common characters that need encoding:
+
+- `:` → `%3A`
+- `/` → `%2F`
+- `?` → `%3F`
+- `#` → `%23`
+- `&` → `%26`
+- `=` → `%3D`
+- `+` → `%2B`
+- Space → `%20` (or `+`)
+
+Example with special characters:
+```ts
+Original: `Write a function: def hello()`
+Encoded: `/c/new?prompt=Write%20a%20function%3A%20def%20hello()`
+```
+
+You can use JavaScript's built-in `encodeURIComponent()` function to properly encode prompts:
+```javascript
+const prompt = "Write a function: def hello()";
+const encodedPrompt = encodeURIComponent(prompt);
+const url = `/c/new?prompt=${encodedPrompt}`;
+console.log(url);
+```
+
+Try running the code in your browser console to see the encoded URL (browser shortcut: `Ctrl+Shift+I`).
+
+### Endpoint Selection
+
+The `endpoint` parameter can be used alone:
+```bash
+https://your-domain.com/c/new?endpoint=google
+```
+
+When only `endpoint` is specified:
+- It will use the last selected model from localStorage
+- If no previous model exists, it will use the first available model in the endpoint's model list
+
+#### Notes
+
+- The `endpoint` value must be one of the following:
+```bash
+openAI, azureOpenAI, google, anthropic, assistants, azureAssistants, bedrock, agents
+```
+- If using a [custom endpoint](/v0.8.4/docs/quick_start/custom_endpoints), you can use its name as the value (case-insensitive)
+
+```bash
+# using `endpoint=perplexity` for a custom endpoint named `Perplexity`
+https://your-domain.com/c/new?endpoint=perplexity&model=llama-3.1-sonar-small-128k-online
+```
+
+### Model Selection
+
+The `model` parameter can be used alone:
+```bash
+https://your-domain.com/c/new?model=gpt-4o
+```
+
+When only `model` is specified:
+- It will only select the model if it's available in the current endpoint
+- The current endpoint is either the default endpoint or the last selected endpoint
+
+### Prompt Parameter
+
+The `prompt` parameter allows you to pre-populate the chat input field:
+```bash
+https://your-domain.com/c/new?prompt=Explain quantum computing
+```
+
+You can also use `q` as a shorthand, which is interchangeable with `prompt`:
+```bash
+https://your-domain.com/c/new?q=Explain quantum computing
+```
+
+You can combine these with other parameters:
+```bash
+https://your-domain.com/c/new?endpoint=anthropic&model=claude-3-5-sonnet-20241022&prompt=Explain quantum computing
+```
+
+### Automatic Prompt Submission
+
+The `submit` parameter allows you to automatically submit the prompt without manual intervention:
+```bash
+https://your-domain.com/c/new?prompt=Explain quantum computing&submit=true
+```
+
+This feature is particularly useful for:
+- Creating automated workflows (e.g., Raycast, Alfred, Automater)
+- Building external integrations
+
+You can combine it with other parameters for complete automation:
+```bash
+https://your-domain.com/c/new?endpoint=openAI&model=gpt-4&prompt=Explain quantum computing&submit=true
+```
+
+### Special Endpoints
+
+#### Model Specs
+You can select a specific model spec by name:
+```bash
+https://your-domain.com/c/new?spec=meeting-notes-gpt4
+```
+This will load all the settings defined in the model spec. When using the `spec` parameter, other model parameters in the URL will be ignored.
+
+#### Agents
+You can directly load an agent using its ID without specifying the endpoint:
+```bash
+https://your-domain.com/c/new?agent_id=your-agent-id
+```
+This will automatically set the endpoint to `agents`.
+
+#### Assistants
+Similarly, you can load an assistant directly:
+```bash
+https://your-domain.com/c/new?assistant_id=your-assistant-id
+```
+This will automatically set the endpoint to `assistants`.
+
+## Supported Parameters
+
+LibreChat supports a wide range of parameters for fine-tuning your conversation settings:
+
+### LibreChat Settings
+- `maxContextTokens`: Override the system-defined context window
+- `resendFiles`: Control file resubmission in subsequent messages
+- `promptPrefix`: Set custom instructions/system message
+- `imageDetail`: 'low', 'auto', or 'high' for image quality
+ - Note: while this is a LibreChat-specific parameter, it only affects the following endpoints:
+ - OpenAI, Custom Endpoints, which are OpenAI-like, and Azure OpenAI, for which this defaults to 'auto'
+- `spec`: Select a specific LibreChat [Model Spec](/v0.8.4/docs/configuration/librechat_yaml/object_structure/model_specs) by name
+ - Must match the exact name of a configured model spec
+ - When specified, other model parameters will not take effect, only those defined by the model spec
+ - **Important:** If model specs are configured with `enforce: true`, using this parameter may be required for URL query params to work properly
+- `fileTokenLimit`: Set maximum token limit for file processing to control costs and resource usage.
+ - Note: Request value overrides YAML default.
+
+### Model Parameters
+Different endpoints support various parameters:
+
+**OpenAI, Custom, Azure OpenAI:**
+```bash
+# Note: these should be valid values according to the provider's API
+temperature, presence_penalty, frequency_penalty, stop, top_p, max_tokens,
+reasoning_effort, reasoning_summary, verbosity, useResponsesApi, web_search, disableStreaming
+```
+
+**Google, Anthropic:**
+```bash
+# Note: these should be valid values according to the provider's API
+topP, topK, maxOutputTokens, thinking, thinkingBudget, thinkingLevel, web_search
+```
+
+**Anthropic, Bedrock (Anthropic models):**
+
+Set this to `true` or `false` to toggle the "prompt-caching":
+```bash
+promptCache
+```
+
+More info: https://www.anthropic.com/news/prompt-caching, https://docs.aws.amazon.com/bedrock/latest/userguide/prompt-caching.html#prompt-caching-get-started
+
+**Bedrock:**
+```bash
+# Bedrock region
+region=us-west-2
+# Bedrock equivalent of `max_tokens`
+maxTokens=200
+# Bedrock reasoning effort (for supported models like ZAI, MoonshotAI)
+reasoning_effort=medium
+```
+
+**Assistants/Azure Assistants:**
+```bash
+# overrides existing assistant instructions for current run
+instructions=your+instructions
+```
+```bash
+# Adds the current date and time to `additional_instructions` for each run.
+append_current_datetime=true
+```
+
+## More Info
+
+For more information on any of the above, refer to [Model Spec Preset Fields](/v0.8.4/docs/configuration/librechat_yaml/object_structure/model_specs), which shares most parameters.
+
+**Example with multiple parameters:**
+```bash
+https://your-domain.com/c/new?endpoint=google&model=gemini-2.0-flash-exp&temperature=0.7&prompt=Oh hi mark
+```
+
+**Example with model spec:**
+```bash
+https://your-domain.com/c/new?spec=meeting-notes-gpt4&prompt=Here%20is%20the%20transcript...
+```
+Note: When using `spec`, other model parameters are ignored in favor of the model spec's configuration.
+
+## ⚠️ Warning
+
+Exercise caution when using query parameters:
+- Misuse or exceeding provider limits may result in API errors
+- If you encounter bad request errors, reset the conversation by clicking "New Chat"
+- Some parameters may have no effect if they're not supported by the selected endpoint
+
+## Best Practices
+
+1. Always use both `endpoint` and `model` when possible
+2. Verify parameter support for your chosen endpoint
+3. Use reasonable values within provider limits
+4. Test your parameter combinations before sharing URLs
+
+## Parameter Validation
+
+All parameters are validated against LibreChat's schema before being applied. Invalid parameters or values will be ignored, and valid settings will be applied to the conversation.
+
+---
+
+This feature enables powerful use cases like:
+- Sharing specific conversation configurations
+- Creating bookmarks for different chat settings
+- Automating chat setup through URL parameters
+
+---
+
+#LibreChat #ChatConfiguration #AIParameters #OpenSource #URLQueryParameters
diff --git a/content/docs-archive/v0.8.4/features/web_search.mdx b/content/docs-archive/v0.8.4/features/web_search.mdx
new file mode 100644
index 000000000..362794a6a
--- /dev/null
+++ b/content/docs-archive/v0.8.4/features/web_search.mdx
@@ -0,0 +1,206 @@
+---
+title: "Web Search"
+icon: Search
+---
+
+LibreChat's web search feature allows you to search the internet and retrieve relevant information to enhance your conversations. The feature consists of three main components that work together to provide comprehensive search results.
+
+## Quick Start
+
+To get started with web search, you'll need to configure API keys for all three components to ensure effective search results. You can do this in two ways:
+
+1. **Environment Variables** (Recommended for admins):
+ ```bash
+ # Search Provider (Required)
+ SERPER_API_KEY=your_serper_api_key
+ # or
+ SEARXNG_INSTANCE_URL=your_searxng_instance_url
+ SEARXNG_API_KEY=your_searxng_api_key # Optional
+
+ # Scraper (Required)
+ FIRECRAWL_API_KEY=your_firecrawl_api_key
+ # Optional: Custom Firecrawl API URL
+ FIRECRAWL_API_URL=your_firecrawl_api_url
+ # Optional: Firecrawl API version (v0 or v1)
+ # FIRECRAWL_VERSION=v1
+
+ # Reranker (Required)
+ JINA_API_KEY=your_jina_api_key
+ # Optional: Custom Jina API URL
+ JINA_API_URL=your_jina_api_url
+ # or
+ COHERE_API_KEY=your_cohere_api_key
+ ```
+
+2. **User Interface** (If environment variables are not set):
+ - Users will be prompted to enter the required API keys when they first use the web search feature
+ - They can choose which search provider (Serper or SearXNG) and which reranker service to use (Jina or Cohere)
+
+## Obtaining API Keys
+
+Each component of the web search feature requires its own API key. Here's how to obtain them:
+
+### Search Providers
+
+#### Serper
+1. Visit [Serper.dev](https://serper.dev)
+2. Sign up for an account
+3. Navigate to the API Key section
+4. Copy your API key
+5. Set it in your environment variables or provide it through the UI
+
+#### SearXNG
+1. Follow the setup instructions in the [Web Search Configuration](/v0.8.4/docs/configuration/librechat_yaml/object_structure/web_search#setting-up-searxng) documentation
+2. Set `SEARXNG_INSTANCE_URL` to your instance URL
+3. Optionally set `SEARXNG_API_KEY` if your instance requires authentication
+
+### Scraper: Firecrawl
+
+1. Visit [Firecrawl.dev](https://docs.firecrawl.dev/introduction#api-key)
+2. Sign up for an account
+3. Navigate to the API Key section
+4. Copy your API key
+5. Set it in your environment variables or provide it through the UI
+6. (Optional) If you're using a custom Firecrawl instance, you'll also need to set the API URL
+
+### Rerankers
+
+#### Jina
+1. Visit [Jina.ai](https://jina.ai/api-dashboard/)
+2. Sign up for an account
+3. Navigate to the API Dashboard
+4. Copy your API key
+5. Set it in your environment variables or provide it through the UI
+
+#### Cohere
+1. Visit [Cohere Dashboard](https://dashboard.cohere.com/welcome/login)
+2. Sign up for an account
+3. Navigate to the API Keys section
+4. Copy your API key
+5. Set it in your environment variables or provide it through the UI
+
+## Components
+
+### 1. Search Providers
+
+Search providers are responsible for performing the initial web search and returning relevant results.
+
+**Available Providers:**
+- **Serper**: A Google Search API that provides high-quality search results
+ - Get your API key from [Serper.dev](https://serper.dev/api-key)
+- **SearXNG**: Open-source, self-hosted meta search engine
+ - Self-host your own instance
+ - Privacy-focused search results
+
+### 2. Scrapers
+
+Scrapers extract the actual content from web pages returned by the search provider.
+
+**Available Scrapers:**
+- **Firecrawl**: A powerful web scraping service that extracts content from web pages
+ - Get your API key from [Firecrawl.dev](https://docs.firecrawl.dev/introduction#api-key)
+ - API URL is optional (defaults to Firecrawl's hosted service)
+
+**Planned Scrapers:**
+- **Local Firecrawl**: Self-hosted version of Firecrawl
+- Additional third-party scraping services
+
+### 3. Rerankers
+
+Rerankers analyze the scraped content to determine the most relevant parts and reorder them for better results.
+
+**Available Rerankers:**
+- **Jina**: AI-powered reranking service
+ - Get your API key from [Jina.ai](https://jina.ai/api-dashboard/)
+ - API URL is optional (defaults to Jina's hosted service)
+- **Cohere**: Advanced reranking service
+ - Get your API key from [Cohere Dashboard](https://dashboard.cohere.com/welcome/login)
+
+**Planned Rerankers:**
+- **RAG API**: Open-source reranking using RAG (Retrieval-Augmented Generation)
+- Additional third-party reranking services
+
+## Configuration
+
+### Admin Configuration
+
+Admins can configure the web search feature using environment variables. The YAML configuration allows you to specify custom environment variable names for each component.
+
+⚠️ **Important: Never put actual API keys or values in the YAML file (they won't work)- only use environment variable names.**
+
+```yaml
+webSearch:
+ # Search Provider Configuration
+ serperApiKey: "${CUSTOM_SERPER_API_KEY}" # ✅ Correct: Using environment variable name
+ # serperApiKey: "sk-123..." # ❌ Wrong: Never put actual API keys here
+ # or
+ searxngInstanceUrl: "${CUSTOM_SEARXNG_INSTANCE_URL}" # ✅ Correct: Using environment variable name
+ searxngApiKey: "${CUSTOM_SEARXNG_API_KEY}" # ✅ Correct: Using environment variable name
+ # searxngInstanceUrl: "http://..." # ❌ Wrong: Never put actual URLs here
+ # searxngApiKey: "sk-123..." # ❌ Wrong: Never put actual API keys here
+
+ # Scraper Configuration
+ firecrawlApiKey: "${CUSTOM_FIRECRAWL_API_KEY}"
+ firecrawlApiUrl: "${CUSTOM_FIRECRAWL_API_URL}"
+ # firecrawlApiKey: "fc-123..." # ❌ Wrong: Never put actual API keys here
+ # firecrawlApiUrl: "https://..." # ❌ Wrong: Never put actual URLs here
+
+ # Reranker Configuration
+ jinaApiKey: "${CUSTOM_JINA_API_KEY}"
+ jinaApiUrl: "${CUSTOM_JINA_API_URL}"
+ cohereApiKey: "${CUSTOM_COHERE_API_KEY}"
+ # jinaApiKey: "jn-123..." # ❌ Wrong: Never put actual API keys here
+ # jinaApiUrl: "https://..." # ❌ Wrong: Never put actual URLs here
+ # cohereApiKey: "ch-123..." # ❌ Wrong: Never put actual API keys here
+
+ # General Settings
+ safeSearch: 1 # Options: 0 (OFF), 1 (MODERATE - default), 2 (STRICT)
+```
+
+**Note:** The YAML configuration should only contain environment variable names (in the format `${VARIABLE_NAME}`). This flexibility enables:
+- Using different variable names in different environments
+- Supporting multiple configurations for different user groups
+- Future integration with role-based configurations
+
+If you want to restrict the system to use only specific services, you can specify the service types:
+
+```yaml
+webSearch:
+ # ... variable configurations ...
+ searchProvider: "serper" # Only use Serper for search
+ # searchProvider: "searxng" # Only use SearXNG for search
+ scraperProvider: "firecrawl" # Only use Firecrawl for scraping
+ rerankerType: "jina" # Only use Jina for reranking
+```
+
+### User Configuration
+
+If the admin hasn't configured all the necessary API keys, users will be prompted to provide them through the UI. The interface allows users to:
+
+1. Choose their preferred reranker (Jina or Cohere)
+2. Enter API keys for the required services
+3. Configure the Firecrawl API URL if needed (optional)
+4. Configure the Jina API URL if needed (optional)
+
+## Usage
+
+Once configured, you can use web search in two ways:
+
+1. **Chat Interface**: Click the web search button in the chat interface to enable web search for your conversation
+2. **Agents**: Use the `web_search` capability in agents to allow them to search the web
+
+## Notes
+
+- All three components (search provider, scraper, and reranker) are required for effective search results
+- The Firecrawl API URL is optional and defaults to their hosted service
+- The Jina API URL is optional and defaults to their hosted service
+- Safe search provides three levels of content filtering: OFF (0), MODERATE (1 - default), and STRICT (2)
+- The scraper timeout is set to 7.5 seconds (7500ms) by default
+- API keys can be revoked at any time through the UI
+- Future updates will include more open-source, self-hosted options for all components
+- Additional customization options are planned, including:
+ - Control over the number of links to scrape
+ - Domain allowlist/blocklist for scraping
+ - Custom scraping rules and filters
+ - Advanced result filtering and ranking options
+ - Rate limiting and request throttling controls
diff --git a/content/docs-archive/v0.8.4/index.mdx b/content/docs-archive/v0.8.4/index.mdx
new file mode 100644
index 000000000..038c8847c
--- /dev/null
+++ b/content/docs-archive/v0.8.4/index.mdx
@@ -0,0 +1,7 @@
+---
+title: Quick Start
+icon: Rocket
+description: Choose your setup method and get LibreChat running in minutes.
+---
+
+
+ 
+ *Centralized dashboard for managing all your shared links*
+
+
+ 
+ *View details and manage individual shared links*
+
+
+ ./helm/librechat`
+
+
+Similar to other Helm charts, there exists a [values file](https://github.com/danny-avila/LibreChat/blob/main/helm/librechat/values.yaml) that outlines the default settings and indicates which configuration options can be modified.
+
+Create a `values.yaml` file populated with the values you want to modify from the default.
+
+Install the Helm chart: `helm install librechat oci://ghcr.io/danny-avila/librechat-chart/librechat --values Development version
+ +In the repo's root directory, run: + +`helm install
+
+
+
+
|
+| **Arabic (ar)** | |
+| **Tibetan (bo)** | |
+| **Bosnian (bs)** | |
+| **Catalan (ca)** | |
+| **Czech (cs)** | |
+| **Danish (da)** | |
+| **German (de)** | |
+| **Spanish (es)** | |
+| **Estonian (et)** | |
+| **Persian (fa)** | |
+| **Finnish (fi)** | |
+| **French (fr)** | |
+| **Hebrew (he)** | |
+| **Hungarian (hu)** | |
+| **Armenian (hy)** | |
+| **Indonesian (id)** | |
+| **Icelandic (is)** | |
+| **Italian (it)** | |
+| **Japanese (ja)** | |
+| **Georgian (ka)** | |
+| **Korean (ko)** | |
+| **Lithuanian (lt)** | |
+| **Latvian (lv)** | |
+| **Norwegian Bokmål (nb)** | |
+| **Norwegian Nynorsk (nn)** | |
+| **Dutch (nl)** | |
+| **Polish (pl)** | |
+| **Portuguese (pt-PT)** | |
+| **Brazilian Portuguese (pt-BR)** | |
+| **Russian (ru)** | |
+| **Slovak (sk)** | |
+| **Slovenian (sl)** | |
+| **Swedish (sv)** | |
+| **Thai (th)** | |
+| **Turkish (tr)** | |
+| **Uyghur (ug)** | |
+| **Ukrainian (uk)** | |
+| **Vietnamese (vi)** | |
+| **Chinese (Simplified) (zh-Hans)** | |
+| **Chinese (Traditional) (zh-Hant)** | |
+
+---
+
+
+## Getting Started
+
+Before you begin translating, please follow the steps below to set up your Locize account and start contributing.
+
+
+### Step 1: Create a Locize Account
+
+1. Visit the Registration Page
+
+ Choose your preferred language and click the corresponding link to register:
+
+ - **[English (en)](https://www.locize.app/register?invitation=tTHVYwI9TzWuOeJnKyWxSuuaDrSS5TsZqRh0BAHzebuuljz5OUXnlqbksio5WnXp)**
+ - **[Arabic (ar)](https://www.locize.app/register?invitation=Cn7hc6teYyY89nvQdosfXkubbj2MZi2XMzcxUP6fGglcPkAgd1AwS5Pfbr1Wu4lz)**
+ - **[Tibetan (bo)](https://www.locize.app/register?invitation=183Kk5eTUvr0oeKkZqsIrSG1iflQPk5WjZzH5tb1uwDS7MdS3nFo55frHm86lz78)**
+ - **[Bosnian (bs)](https://www.locize.app/register?invitation=JA2zNrFrvoEbrXQgoZAxRrEStscwrCCAhTP7t44NBxa7XAJbdhwpqntq3xQ6Wltw)**
+ - **[Catalan (ca)](https://www.locize.app/register?invitation=c7ZQ0OT9k6c5kWRXMspgRQZXoZk2vZYIZ3RTpDkVrtShlauJ55YpeMo9EOBsYXgS)**
+ - **[Czech (cs)](https://www.locize.app/register?invitation=ypNUvwJG9ynzZabWS4X1bD2b8qSmhbvyXsytm1sbkVmqN0A6inKhiny2FuNVcvC2)**
+ - **[Danish (da)](https://www.locize.app/register?invitation=xClNgP4A7SNcMdhkTsf6xm8wP24mNbSW3YhnOtDNd7nMHhAZPJsWV8UIyTR6lLxI)**
+ - **[German (de)](https://www.locize.app/register?invitation=rAXIyYNuO53txcygphdOClUR5YnNccd1MZ1Vs66p4ziOqHfM3MFiKnymdK6wLMpW)**
+ - **[Spanish (es)](https://www.locize.app/register?invitation=gkrRvUjxvFnRfUtynbaREj2zdbvd2FU95OFGcixGMOkcCxSwmrvOBclBZJWmERw6)**
+ - **[Estonian (et)](https://www.locize.app/register?invitation=q1ye9gNpYsVKvs2JS5CEjp4SBy6ovq2aUeIhAMsRoW2iVcdfxpc4GiOaHGDV85VZ)**
+ - **[Persian (fa)](https://www.locize.app/register?invitation=DfuKT56Y4KxlPOm6biYl9zbgMo3kBjWJA3Flbd7X5H4hJluUWTsFiQ3MQH07fH0d)**
+ - **[Finnish (fi)](https://www.locize.app/register?invitation=weERAttD7ax0Zfo5w9LyfWbaP50WPbS4Vk7BF1P6wM0fe5Q0xlrJACVjTAGbkv2c)**
+ - **[French (fr)](https://www.locize.app/register?invitation=wz5EbZiwE9Bxev4TTAyG09PKvnFSQoOaLomxVgEKOyaLhm9oCDdhDi4TkJp8rcq5)**
+ - **[Hebrew (he)](https://www.locize.app/register?invitation=3LSHQxUsHYumNhw5ZJNu6Re6x699i6RGnpdKzt2BrDeNFNObxjj2lKXfZFUhb1jP)**
+ - **[Hungarian (hu)](https://www.locize.app/register?invitation=3TaJ2SnDnYfTJQLalKK751cQ04AK5A2gRahC2poeZYXj8MymZ5T0rt4V688e0H7M)**
+ - **[Armenian (hy)](https://www.locize.app/register?invitation=jLAFuEOvlBR86IcF1dZFHobsYdINvFoi0dMxxrJHvXIyxnosWcDblcXn6FtOhcOo)**
+ - **[Indonesian (id)](https://www.locize.app/register?invitation=S94A2D6glr7w64Nf27XwmvzkcnTRAWhxFoxcl7ZRnmm1dMx23kfpZCx8ROlqb6X2)**
+ - **[Icelandic (is)](https://www.locize.app/register?invitation=zgnniaPHGcML0dX5TdZ7Cv9fVkWkVGbrShol4JZYaYQXyk7t2oNlITaImx5n3wZe)**
+ - **[Italian (it)](https://www.locize.app/register?invitation=LI6zvAH82797Gro6lc490d34zrw8vthQPdN01n9nfk2c1LW5VVpf4Db6WL5GFHir)**
+ - **[Japanese (ja)](https://www.locize.app/register?invitation=VVJLuv7WjjBs0wShxZheCIvwzk7XszVsHCAMZmCQ34SJYrwIeB1GW6u2vkYNJdzk)**
+ - **[Georgian (ka)](https://www.locize.app/register?invitation=WK5hB5nznxioaDGOXXPDmcULrNfFA3wkcvS2YiUbrU6b73gKOWix5Qg7uGjpPtkH)**
+ - **[Korean (ko)](https://www.locize.app/register?invitation=nbL4LZMwehlTvFKNmNGgTTJt9YsZuuyCMjF9yAc92bVIWEjAc9C1G0ujsEl76dYb)**
+ - **[Lithuanian (lt)](https://www.locize.app/register?invitation=mObXVLL1r0IpkldNhVvahfdBSxo1AtqytlBavTU9jAb2M5K1HdbEADfpXpJWkyQK)**
+ - **[Latvian (lv)](https://www.locize.app/register?invitation=ey55PwxruCkT1EJ95oluthUzDbXwYJL4pXEd2xQoEHLwleVWND4VRND13a7EsioC)**
+ - **[Norwegian Bokmål (nb)](https://www.locize.app/register?invitation=14FVJmxYhd7ZSzjmxkF1XEU0jO9HDG7lpRRiOwVNKi19Ad6hD58NWASD0bN8JgaK)**
+ - **[Norwegian Nynorsk (nn)](https://www.locize.app/register?invitation=0upNDr8hxNUkMCAu0Lzo1MQnM0i7VXbli9x2wvygCz0q8sAK2z1AwxkgUDOD4n9R)**
+ - **[Dutch (nl)](https://www.locize.app/register?invitation=BQoligTqND5E4jlGmXJZVzkLOpo4pTf9wUyN19zZbgNB38JHaciJ2FnIbsLOXPbe)**
+ - **[Polish (pl)](https://www.locize.app/register?invitation=ZPiib1OoPM3OHBUow79I8iQNiFk4SHO7HASO3rHdJpKSlJwA4oxsORR2w4yJaPig)**
+ - **[Portuguese (pt-PT)](https://www.locize.app/register?invitation=c11DbWJk7O5TNIKon9leIfIbqARz60URaGB0WFQPT2ym3wxUDR8DgIiOlXNIBz13)**
+ - **[Brazilian Portuguese (pt-BR)](https://www.locize.app/register?invitation=99JdsEgKuVR9XhQJWi91Jq0LkqigiSz4EOf4gVGSr5RwZPp6ad4JQZLHVwhumNvB)**
+ - **[Russian (ru)](https://www.locize.app/register?invitation=rz4C3pVFdfr5XPPNTsYJvjjnC7vHDVWVOfyUzCf33MxhccdYB7vM7jxcHLacGl14)**
+ - **[Slovak (sk)](https://www.locize.app/register?invitation=wQkVqwu4Xr2KzmCgsXmqI7nMjyBzT2EKNFS3P6rNe4Kii3DgQG1i5ozeQeVEBmNd)**
+ - **[Slovenian (sl)](https://www.locize.app/register?invitation=NyNTniuVwwvEkKoKoOvAT4nzbVuvxE5X4kVUhBE9KSb3sEwEARQtMTeBCqpuV9dk)**
+ - **[Swedish (sv)](https://www.locize.app/register?invitation=RYtYhip5O5ACNCth1cIZpByGnZC1b3JttimEe8mrz5NDyEjVAs1PVcMIQ1in4j7D)**
+ - **[Thai (th)](https://www.locize.app/register?invitation=3xMjJPqupRNO2BU7K3WMWhxFtoGNzL97hxKIGjE8Yoa4v7lJj8ZjTy5p5dmcfLjW)**
+ - **[Turkish (tr)](https://www.locize.app/register?invitation=x3Ov59Gdrk2b76gn5pSVCwuekDs817YOYElXJn9zCYClPG2XlBORQDRygZmdBH4B)**
+ - **[Uyghur (ug)](https://www.locize.app/register?invitation=TeQX9ECX0oqhtkyBswm8BeOqlSaA5dKZaptvaEpYlfBhGBSl8PGIYfdVvPvgQnQF)**
+ - **[Ukrainian (uk)](https://www.locize.app/register?invitation=4Z060E9kPjmOqO8BmRSvuIujLydZiRCc0lu90iwQSaCche1tSdFcGOrdlDgPZ2ec)**
+ - **[Vietnamese (vi)](https://www.locize.app/register?invitation=rhADX8GuhgQmYrmbHT13YVg2WqMLJpgPdh1OBuujn9GoNUVW6RPipYvC20aH1xcQ)**
+ - **[Chinese (Simplified) (zh-Hans)](https://www.locize.app/register?invitation=HXXM2h8SJsBLIPJol3usRct0aPPcr809xzfV4DQHolyEfeSjBwEjChd37vE3ZrRw)**
+ - **[Chinese (Traditional) (zh-Hant)](https://www.locize.app/register?invitation=9PWBDcMascIBGG6wwobkVT6cL7p7IncFZVqwIe0e7VZd14MJOAMQGk6IjlvgmA00)**
+
+
+2. **Fill in Your Details:**
+Enter your email, password, and any other required information, then click **Sign Up**.
+
+
+
+
+### Step 2: Explore the Locize Dashboard
+
+After signing up, you’ll be directed to the Locize dashboard, where you can see an overview of the translation project.
+
+- **Dashboard Overview:**
+This page displays the available languages and progress statistics for the project.
+
+
+
+
+### Step 3: Select Your Language
+
+1. **Open the Language Dropdown:**
+Click the dropdown menu that lists all supported languages.
+
+2. **Choose Your Preferred Language:**
+For example, if you want to translate into Dutch, scroll down and select **Dutch**.
+
+
+
+
+### Step 4: Navigate to the Translation Page
+
+After selecting your language, click on the translation progress indicator (for example, "35.61% translated"). This will take you to the page where you can contribute translations.
+
+
+
+
+### Step 5: Contribute Your Translation
+
+1. **Browse the Translation Strings:**
+The interface displays a list of translation keys along with their original texts.
+
+2. **Select a String to Translate:**
+Click on the string you wish to work on.
+
+3. **Enter Your Translation:**
+Type your translated text into the input field provided next to the original text.
+
+4. **Review Your Work:**
+Ensure that your translation is accurate and clear.
+
+
+
+
+### Step 6: Save and Submit Your Translation
+
+1. **Submit Your Translation:**
+Once you’re satisfied with your translation, click the **Save** button to submit it for review.
+
+2. **Pending Review:**
+Your submitted translation will be marked as pending and will be reviewed by project maintainers.
+
+
+
+
+### Step 7: Translation Approval
+
+After review, your translation will be approved and integrated into the project.
+
+- **Approved Translation:**
+Once approved, your contribution will be reflected in the Locize dashboard and the overall translation progress.
+
+
+
+---
+
+## Handling `{{0}}` and `{{1}}` in Translation Strings
+
+Sometimes translation strings need to include dynamic content. These dynamic parts, called **interpolations**, are represented by placeholders enclosed in double curly brackets (e.g., `{{0}}` or `{{1}}`). When translating such strings, it's important to maintain these placeholders in the correct positions.
+
+Below are two examples to help guide you:
+
+### Example 1: Single Interpolation
+
+Consider the translation key `com_assistants_completed_action`. The original English text is:
+
+```text
+Talked to {{0}}
+```
+
+For the German translation, ensure the placeholder remains intact and is placed appropriately:
+
+```text
+Mit {{0}} gesprochen
+```
+
+This image shows how a single interpolation is represented in a translation string:
+
+
+
+---
+
+### Example 2: Multiple Interpolations
+
+Now, look at the translation key `com_files_number_selected`, which includes two placeholders. The English version is:
+
+```text
+{{0}} of {{1}} item(s) selected
+```
+
+In the German translation, both placeholders must be preserved and positioned correctly:
+
+```text
+{{0}} von {{1}} Datei(en) ausgewählt
+```
+
+This image illustrates how multiple interpolations appear in translation strings:
+
+
+
+---
+
+
+## Adding a New Language
+
+If you don't see your language listed in our translation table, you can help us expand our language support:
+
+1. **Create a New Issue:**
+Open a new issue in our GitHub repository: [LibreChat Issues](https://github.com/danny-avila/LibreChat/issues).
+
+2. **Select the New Language Request Template:**
+Use the **New Language Request** template and provide:
+ - The full name of your language (e.g., Spanish, Mandarin).
+ - The [ISO 639-1](https://www.w3schools.com/tags/ref_language_codes.asp) code for your language (e.g., `es` for Spanish).
+
+3. **Collaborate with Maintainers:**
+Our maintainers will review your request and work with you to integrate the new language. Once approved, your language will appear in the translation progress table, and you can start contributing.
+
+---
+
+## Need Help?
+
+If you have any questions or need assistance, please feel free to:
+
+- **Open an Issue:**
+Submit an issue in our repository: [LibreChat Issues](https://github.com/danny-avila/LibreChat/issues).
+
+- **Join Our Discord Community:**
+Connect with fellow translators on our [Discord server](https://discord.librechat.ai).
+
+- **Contact a Maintainer:**
+Reach out directly to one of our project maintainers for additional support.
+
+Your contributions help make LibreChat accessible to users worldwide. Thank you for supporting our project, and happy translating!
+
+
+---
+
+We thank [Locize](https://locize.com) for their translation management tools that support multiple languages in LibreChat.
+
+
+
+
+
+
+
+
+
+## 1. Flexible Data Model
+MongoDB's document-based data model allows for storing and retrieving data in a flexible and dynamic manner. Unlike traditional relational databases, MongoDB doesn't require a fixed schema, making it easier to adapt to changing data requirements. This flexibility is essential for LibreChat, as it needs to store various types of data, such as conversation histories, user profiles, presets, API keys, and more, without being constrained by a rigid table structure.
+
+## 2. Efficient Storage of Conversation Histories
+One of the primary use cases for LibreChat is to store and retrieve conversation histories. MongoDB's ability to store nested data structures as JSON-like documents makes it an excellent choice for storing conversation histories, which can include complex data structures like messages, timestamps, and metadata.
+
+## 3. Secure Storage of Sensitive Data
+LibreChat handles sensitive data, such as API keys and encrypted user passwords. MongoDB's built-in support for data encryption at rest and in transit ensures that this sensitive information remains secure and protected from unauthorized access.
+
+## 4. Horizontal Scalability
+As LibreChat grows and attracts more users, its data storage requirements will increase. MongoDB's horizontal scalability allows for scaling out by adding more servers to a cluster, providing the ability to handle larger amounts of data and higher traffic loads without compromising performance.
+
+## 5. Cross-Device Accessibility
+LibreChat aims to provide a seamless experience across multiple devices, allowing users to access their data and conversation histories from different devices. MongoDB's replication and sharding capabilities ensure that data is consistently available and accessible, enabling users to pick up their conversations where they left off, regardless of the device they're using.
+
+## 6. Developer Productivity
+MongoDB's intuitive query language and rich ecosystem of tools and libraries contribute to faster development cycles and increased developer productivity. This aligns well with LibreChat's goal of being an open-source project, fostering collaboration and contributions from the developer community.
+
+By leveraging MongoDB's strengths, LibreChat can efficiently manage and store diverse data structures, ensure data security and availability, and provide a seamless cross-device experience for its users. MongoDB's flexibility, scalability, and developer-friendly features make it an ideal choice for powering the core functionalities of LibreChat.
+
+
+## Note
+
+
+
+
+
+
+## OAuth2
+
+- [Apple](/v0.8.5/docs/configuration/authentication/OAuth2-OIDC/apple)
+- [Discord](/v0.8.5/docs/configuration/authentication/OAuth2-OIDC/discord)
+- [Facebook](/v0.8.5/docs/configuration/authentication/OAuth2-OIDC/facebook)
+- [GitHub](/v0.8.5/docs/configuration/authentication/OAuth2-OIDC/github)
+- [Google](/v0.8.5/docs/configuration/authentication/OAuth2-OIDC/google)
+
+## OpenID Connect
+
+- [Auth0](/v0.8.5/docs/configuration/authentication/OAuth2-OIDC/auth0)
+- [AWS Cognito](/v0.8.5/docs/configuration/authentication/OAuth2-OIDC/aws)
+- [Azure Entra/AD](/v0.8.5/docs/configuration/authentication/OAuth2-OIDC/azure)
+- [Keycloak](/v0.8.5/docs/configuration/authentication/OAuth2-OIDC/keycloak)
+- [Re-use OpenID Tokens for Login Session](/v0.8.5/docs/configuration/authentication/OAuth2-OIDC/token-reuse)
+
+## Troubleshooting OpenID Connect
+
+If you encounter issues with OpenID Connect authentication:
+
+1. **Enable Header Debug Logging**: Set `DEBUG_OPENID_REQUESTS=true` in your environment variables to log request headers in addition to URLs (with sensitive data masked). Note: Request URLs are always logged at debug level
+2. **Check Redirect URIs**: Ensure your callback URL matches exactly between your provider and LibreChat configuration
+3. **Verify Scopes**: Make sure all required scopes are properly configured
+4. **Review Provider Logs**: Check your identity provider's logs for authentication errors
+5. **Validate Tokens**: Ensure your provider is issuing valid tokens with the expected claims
+6. **Ensure _nonce_ is generated**: Some identity providers generate `nonce` url parameter if it's missing in the request. Set `OPENID_GENERATE_NONCE=true` to force the openid-client to generate it.
+
diff --git a/content/docs-archive/v0.8.5/configuration/authentication/OAuth2-OIDC/keycloak.mdx b/content/docs-archive/v0.8.5/configuration/authentication/OAuth2-OIDC/keycloak.mdx
new file mode 100644
index 000000000..7f1289bc8
--- /dev/null
+++ b/content/docs-archive/v0.8.5/configuration/authentication/OAuth2-OIDC/keycloak.mdx
@@ -0,0 +1,70 @@
+---
+title: Keycloak
+icon: KeyRound
+description: Learn how to configure LibreChat to use Keycloak for user authentication.
+---
+
+1. **Access Keycloak Admin Console:**
+- Open the Keycloak Admin Console in your web browser. This is usually
+found at a URL like `http://localhost:8080/auth/admin/`.
+
+2. **Create a Realm (if necessary):**
+- If you don't already have a realm for your application, create one. Click on 'Add Realm' and give it a name.
+
+3. **Create a Client:**
+- Within your realm, click on 'Clients' and then 'Create'.
+- Enter a client ID and select 'openid-connect' as the Client Protocol.
+- Set 'Client Authentication' to 'On'.
+- In 'Valid Redirect URIs', enter `http://localhost:3080/oauth/openid/callback` or the appropriate URI for
+your application.
+
+
+
+
+
+
+
+
+4. **Configure Client:**
+- After creating the client, you will be redirected to its settings page.
+- Note the 'Client ID' and 'Secret' from the 'Credentials' tab – you'll need these for your application.
+
+
+
+
+5. **Add Roles (Optional):**
+If you want to restrict access to users with specific roles, you can define roles in Keycloak and assign them to users.
+- Go to the 'Roles' tab in your client or realm (depending on where you want to define the roles).
+- Create roles that match the value(s) you have in `OPENID_REQUIRED_ROLE`.
+
+
+
+6. **Assign Roles to Users (Optional):**
+- Go to 'Users', select a user, and go to the 'Role Mappings' tab.
+- Assign at least one of the roles specified in `OPENID_REQUIRED_ROLE` to the user.
+
+
+
+7. **Get path of roles list inside token (Optional):**
+- Decode your jwtToken from OpenID provider and determine path for roles list inside access token. For example, if you are
+ using Keycloak, the path is `realm_access.roles`.
+- Put this path in `OPENID_REQUIRED_ROLE_PARAMETER_PATH` variable in `.env` file.
+- By parameter `OPENID_REQUIRED_ROLE_TOKEN_KIND` you can specify which token kind you want to use.
+ Possible values are `access` and `id`.
+
+8. **Update Your Project's Configuration:**
+- Open the `.env` file in your project folder and add the following variables:
+ ```bash filename=".env"
+ OPENID_ISSUER=http://localhost:8080/realms/[YourRealmName]
+ OPENID_CLIENT_ID=[YourClientID]
+ OPENID_CLIENT_SECRET=[YourClientSecret]
+ OPENID_SESSION_SECRET=[JustGenerateARandomSessionSecret]
+ OPENID_CALLBACK_URL=/oauth/openid/callback
+ OPENID_SCOPE="openid profile email"
+ OPENID_REQUIRED_ROLE=[YourRequiredRole] # Single role or comma-separated roles (e.g., role1,role2,admin)
+ OPENID_REQUIRED_ROLE_TOKEN_KIND=(access|id) # that means, `access` or `id`
+ OPENID_REQUIRED_ROLE_PARAMETER_PATH="realm_access.roles"
+
+ # Optional: redirects the user to the end session endpoint after logging out
+ OPENID_USE_END_SESSION_ENDPOINT=true
+ ```
diff --git a/content/docs-archive/v0.8.5/configuration/authentication/OAuth2-OIDC/meta.json b/content/docs-archive/v0.8.5/configuration/authentication/OAuth2-OIDC/meta.json
new file mode 100644
index 000000000..61a56c8e3
--- /dev/null
+++ b/content/docs-archive/v0.8.5/configuration/authentication/OAuth2-OIDC/meta.json
@@ -0,0 +1,20 @@
+{
+ "title": "OAuth2 & OIDC",
+ "icon": "KeyRound",
+ "pages": [
+ "---OAuth2---",
+ "apple",
+ "discord",
+ "facebook",
+ "github",
+ "google",
+ "---OIDC---",
+ "auth0",
+ "authelia",
+ "authentik",
+ "aws",
+ "azure",
+ "keycloak",
+ "token-reuse"
+ ]
+}
diff --git a/content/docs-archive/v0.8.5/configuration/authentication/OAuth2-OIDC/token-reuse.mdx b/content/docs-archive/v0.8.5/configuration/authentication/OAuth2-OIDC/token-reuse.mdx
new file mode 100644
index 000000000..75bd07c5a
--- /dev/null
+++ b/content/docs-archive/v0.8.5/configuration/authentication/OAuth2-OIDC/token-reuse.mdx
@@ -0,0 +1,144 @@
+---
+title: OpenID Connect Token Reuse
+icon: Fingerprint
+description: How to configure OpenID Connect token reuse with LibreChat
+---
+
+LibreChat supports reusing access and refresh tokens issued by your OpenID Connect provider (like Azure Entra ID or Auth0) to manage user authentication state. When this feature is active, the refresh token passed to the user as a cookie is issued by your OpenID provider instead of LibreChat, allowing LibreChat servers to refresh it and request access tokens from your provider.
+
+## Prerequisites
+
+- A configured OpenID Connect provider (like Azure Entra ID, Auth0, etc.)
+- Basic OpenID Connect setup completed
+
+## Configuration Steps
+
+1. Set `OPENID_REUSE_TOKENS=true` in your environment variables.
+
+## Provider-Specific Configuration
+
+### Auth0 Configuration
+
+
+
+
+
+
+
+
+
+
+
+
+## Session Expiry and Refresh Token
+
+- Default values: session expiry: 15 minutes, refresh token expiry: 7 days
+ - For more information: **[GitHub PR #927 - Refresh Token](https://github.com/danny-avila/LibreChat/pull/927)**
+
+
+ 
+
+
+
+ 
+
+