-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Description
Is your feature request related to a problem? Please describe.
Currently, when using Algolia DocSearch with the Ask AI side panel enabled, there is no way to keep the search modal as a pure keyword search while also showing the Ask AI side panel as a separate, independent UI element.
The four available mode options each have trade-offs that make this combination impossible:
| Mode | Search box | AI side panel |
|---|---|---|
auto / hybrid |
AI-integrated | ✅ |
sidePanel |
❌ | ✅ |
modal |
AI-integrated | ❌ |
There is no mode that combines a plain keyword search modal with an Ask AI side panel, and there is no way at all to combine VitePress's built-in local search with the Ask AI side panel.
Describe the solution you'd like
New modes:
Combination A — Algolia keyword search + Ask AI side panel:
The Algolia search modal behaves as a pure keyword search, while the Ask AI side panel is available as a fully separate UI element triggered independently.
Combination B — Local search + Ask AI side panel:
VitePress's built-in local search (provider: 'local') is used for the search box, while the Algolia Ask AI side panel runs independently.
Describe alternatives you've considered
Some documentation sites prefer to keep search and AI as clearly separated experiences — users who want fast keyword lookup should not be pushed into an AI flow, while users who want to ask open-ended questions can opt in via the side panel. Mixing both into the search box can feel disorienting and increases cognitive load for users who just want to find a specific page.
Additionally, Combination B (local search + AI side panel) addresses a real cost concern: every keystroke in an AI-integrated search box potentially triggers an API call, whereas a local search index is completely free to query. The two allow site owners to offer AI assistance without incurring unnecessary API costs from routine search activity.
Additional context
No response
Validations
- Follow our Code of Conduct
- Read the docs.
- Read the Contributing Guidelines.
- Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.