Repository navigation
🔎 docs: Rewrite the Search, Knowledge and File Feature Pages - #884
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
berry-13
changed the title
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9b2d79c497
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ## Upload a file for search | ||
|
|
||
|  | ||
| Click **+** in the [message composer](/docs/features/composer) to open the palette, expand **More upload options**, then choose **Upload for File Search** and pick your files. Searching the palette for it works too. Uploading this way also switches on **File Search** for the chat. Large files can take a moment to index; the upload finishes once indexing is done. |
There was a problem hiding this comment.
On the default configuration (legacyFileUploadUX: false), readers cannot follow these instructions: More upload options and Upload for File Search belong to the legacy destination menu. The composer guide (content/docs/features/composer.mdx, lines 28–43) and this commit's fileConfig reference distinguish that menu from the default From Local Computer uploader. Explain how to enable File Search and attach files with the default uploader, and qualify the existing steps as applying only to deployments with the legacy menu; otherwise the primary file-search walkthrough directs default-install users to controls they do not have.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Not a legacy-only control. On dev, useAttachItems pushes the Upload for File Search item without any unified-mode check (only the code-environment item is gated on !isUnifiedMode), and Palette.tsx folds every non-primary destination under More upload options in the default mode; Palette.spec.tsx 'the folded upload destinations' asserts that. The screenshot on this page was captured on a deployment without legacyFileUploadUX and shows the item there. Leaving the steps as written.
| The keys are stored with your account and only used for your searches. To change provider or replace a key later, open the palette and click **Configure** (the gear) on the **Web Search** row. Once you have saved keys, **Revoke** in the same dialog deletes them. When the admin has set every key on the server, there is no dialog and no gear. | ||
|
|
||
| #### Keenable | ||
| A URL you enter is never paired with a key the admin set on the server. If you enter your own Firecrawl or SearXNG URL, enter your own key for it too. Otherwise Firecrawl ignores your URL and uses its default endpoint, and SearXNG does not run at all. |
There was a problem hiding this comment.
For a SearXNG instance that does not require authentication, users can supply just its URL; they do not need to enter a key. This paragraph instead says SearXNG will not run without their own key, contradicting both the optional-key instructions above and content/docs/configuration/librechat_yaml/object_structure/web_search.mdx, lines 90–92. The initialization failure applies specifically when a user-owned URL would otherwise be paired with a server-owned key. Restore that condition and the keyless exception so users of unauthenticated instances are not directed to obtain an unnecessary credential.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in fb72b03: the paragraph now limits the rule to an admin-set key and states that a keyless SearXNG instance works with just the URL.
3bdd2d4 to
fb72b03
Compare
📦 Next.js Bundle Analysis for librechat.aiThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
fb72b03 to
f6fa415
Compare
📦 Next.js Bundle Analysis for librechat.aiThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
f6fa415 to
0f657cc
Compare
📦 Next.js Bundle Analysis for librechat.aiThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
0f657cc to
dc9b8da
Compare
📦 Next.js Bundle Analysis for librechat.aiThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
Summary
Third of five stacked PRs (base: the agentic pages PR).
Rewrites Web Search, Search, Memory, Chat with Files (RAG), Upload as Text, OCR, Resumable Streams, Projects and Smooth Streaming, and moves their setup into the matching configuration pages (web search, memory, file config, OCR, Meilisearch, RAG API, Redis).
Corrections found against dev include: the memory agent only runs when
memory.agent.enabledis true,personalize: falseremoves the user opt-out rather than disabling memory,fileConfig.sttis not in the schema, the default text MIME list matches any type, and resumable streams survive a lost client connection but not an in-memory server restart.Change Type
Testing
pnpm buildpasses on the tip of the stackChecklist
Stack
Merge from the bottom up. Each PR is based on the one before it, so its diff shows only its own changes.