Conversation
#33 In short, it'll 1. [Frontend] Recognize that user is trying to add a citation (trigger text is `\cite{`) 2. [Frontend] Temporarily suppress default Overleaf dropdown suggestions 3. [Frontend] Get the last sentence as context for LLM 4. [Backend] Fetch bibliography in `.bib` files as raw text, and remove irrelevant fields to save tokens 5. [Backend] Call XtraMCP to get paper abstract, using paper title as key 6. [Backend] Query a fast LLM (hardcoded to `gpt-5.2` for now) to get at most 3 citation keys 7. [Frontend] Suppress default Overleaf tab-completion to allow users to accept citation suggestions
Member
Author
wjiayis
changed the title
staging)
Member
|
@wjiayis Yes please merge it into main |
- Updated `LoadingIndicator` to use `useReducer` for better state handling. - Refactored `OnboardingGuide` to utilize `useReducer` for image loading state. - Enhanced accessibility by adding `role` and `tabIndex` attributes to various interactive elements across components. - Simplified state updates in `ChatHistoryModal` and `LoginWithOverleaf` by consolidating state management. - Improved performance in `CodeBlock` by using `useMemo` for highlighted code. - General code cleanup and consistency improvements across multiple components.
) - Updated `LoadingIndicator` to use `useReducer` for better state handling. - Refactored `OnboardingGuide` to utilize `useReducer` for image loading state. - Enhanced accessibility by adding `role` and `tabIndex` attributes to various interactive elements across components. - Simplified state updates in `ChatHistoryModal` and `LoginWithOverleaf` by consolidating state management. - Improved performance in `CodeBlock` by using `useMemo` for highlighted code. - General code cleanup and consistency improvements across multiple components.
- Improved accessibility by standardizing `onKeyDown` event handlers to use consistent formatting for key checks across multiple components. - Refactored layout of JSX elements for better readability in `chat.pb.go`, `embed-sidebar`, and various components in the message entry container. - General code cleanup to enhance maintainability and readability.
- Improved accessibility by standardizing `onKeyDown` event handlers to use consistent formatting for key checks across multiple components. - Refactored layout of JSX elements for better readability in `chat.pb.go`, `embed-sidebar`, and various components in the message entry container. - General code cleanup to enhance maintainability and readability. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > <sup>[Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) is generating a summary for commit 0a06800. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Junyi-99
approved these changes
Feb 18, 2026
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
3 participants
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.
Tested on staging. Functionality works as expected. Latency increased from 2s to 5s, but I suspect it's because the API key was at the brink of having no credits left. Will look into the latency more.