📝 docs: Clarify Web Search Toggle Location and Assistants API Shutdown (#799)

* docs: explain where the web search toggle lives and why it may be hidden

Feedback: 1553520676223066243

* docs: note that OpenAI has shut down the Assistants API

Feedback: 1554214244860301335

Author: berry-13

content/docs/configuration/librechat_yaml/object_structure/assistants_endpoint.mdx

@@ -5,6 +5,10 @@ icon: OpenAI
 
 This page applies to both the `assistants` and `azureAssistants` endpoints.
 
+<Callout type="warning">
+OpenAI removed the Assistants API on August 26, 2026, so the OpenAI `assistants` endpoint no longer works against OpenAI. Use [Agents](/docs/features/agents) instead. See [Assistants](/docs/configuration/pre_configured_ai/assistants) for details.
+</Callout>
+
 **Note:** To enable `azureAssistants`, see the [Azure OpenAI Configuration](/docs/configuration/librechat_yaml/ai_endpoints/azure#using-assistants-with-azure) for more information.
 
 ## Example

content/docs/configuration/pre_configured_ai/assistants.mdx

@@ -3,6 +3,12 @@ title: "Assistants"
 icon: OpenAI
 ---
 
+<Callout type="warning" title="OpenAI has shut down the Assistants API">
+OpenAI deprecated the Assistants API on August 26, 2025 and removed it on August 26, 2026 (see [OpenAI's deprecations page](https://developers.openai.com/api/docs/deprecations)). Requests from the `assistants` endpoint to OpenAI no longer succeed. Use [Agents](/docs/features/agents) instead: they work with OpenAI models and provide the same capabilities (code execution, file search, actions, and tools) without depending on the Assistants API.
+
+The rest of this page is kept for reference.
+</Callout>
+
 - The [Assistants API by OpenAI](https://platform.openai.com/docs/assistants/overview) has a dedicated endpoint.
 - The Assistants API enables the creation of AI assistants, offering functionalities like code interpreter, knowledge retrieval of files, and function execution.
     - [Read here for an in-depth documentation](https://platform.openai.com/docs/assistants/overview) of the feature, how it works, what it's capable of.

content/docs/features/web_search.mdx

@@ -268,8 +268,17 @@ If the admin hasn't configured all the necessary API keys, users will be prompte
 
 Once configured, you can use web search in two ways:
 
-1. **Chat Interface**: Open the **+** palette in the [message composer](/docs/features/composer) and select **Web Search** to enable web search for your conversation
-2. **Agents**: Use the `web_search` capability in agents to allow them to search the web
+1. **Chat Interface**: Open the **+** palette in the [message composer](/docs/features/composer) and select **Web Search** to turn it on for the conversation. It then appears as a chip on the composer; remove the chip to turn it off. If any required API keys are missing, you are prompted to enter them.
+2. **Agents**: Enable the **Web Search** [capability](/docs/features/agents#agent-capabilities) for an agent in the Agent Builder so the agent can search the web.
+
+### Web Search option is not visible
+
+There is no separate web search button. The option lives in the **Tools** section of the **+** palette and only appears when all of the following are true:
+
+- The selected endpoint is not Agents or Assistants. Agents carry their own tool configuration, so for an agent you enable Web Search in the Agent Builder instead.
+- `web_search` is included in [`endpoints.agents.capabilities`](/docs/configuration/librechat_yaml/object_structure/agents#capabilities). It is included by default, so this only matters if you set a custom list.
+- The user's role has the web search permission. Manage it in the [Admin Panel](/docs/features/admin_panel); [`interface.webSearch`](/docs/configuration/librechat_yaml/object_structure/interface#websearch) only seeds it for the default `USER` role at startup.
+- The selected model spec does not set [`hideBadgeRow: true`](/docs/configuration/librechat_yaml/object_structure/model_specs#hidebadgerow), which hides the **Tools** section.
 
 ## Notes