feat(chat): add deep search toggle to chat composer - #142
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Cherry-pick of the Deep search toggle (PR #141, targeting staging) onto
main, resolved for the oldermainhistory.Adds a Deep search toggle to the chat composer so users can enable or disable agentic retrieval per message. Defaults to on (
useAgentic=true), matchingmaincurrent hardcoded behavior.The toggle state flows from the composer through the chat send path into
POST /api/chat, then into the Knowhere retrieval query asuseAgentic(SDK param for the APIuse_agenticfield). The hover tooltip explains the tradeoff:Changes
ChatComposer: new Deep search checkbox toggle (checked by default, disabled while sending), tooltip, andonSendnow passes{ useAgentic }.ChatPanel/WorkspaceShellLayout/ chat workflow: thread the send option through tosendChatMessage.POST /api/chat: accepts optionaluseAgentic(defaults totrueserver-side), passed intohandleChatTurn->answerQuestionWithRetrieval-> retrieval query params.buildRetrievalQueryParams: replaced the hardcodeduseAgenticvalue with the per-request value (defaulttrue).Cherry-pick notes
Conflicts were limited to chat-domain files because
mainis older thanstaging. Resolved by keepingmainversion wherestaging-only features (Knowhere tool runtime, knowledge/remote-document tests) do not exist, and applying only this feature delta.Verification
pnpm typecheckpasses.pnpm teston this branch: 592 passed, 14 skipped.