Fix Page Content Not Being Passed to LLM When useContext=true#754
Open
007DXR wants to merge 2 commits intomlc-ai:mainfrom
Open
Fix Page Content Not Being Passed to LLM When useContext=true#754007DXR wants to merge 2 commits intomlc-ai:mainfrom
007DXR wants to merge 2 commits intomlc-ai:mainfrom
Conversation
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.
Fix Page Content Not Being Passed to LLM When useContext=true
🐛 Issue Description
When
useContext = true, the browser extension is unable to access the current page content, and the LLM responds with "I cannot directly access or display webpage content."🔍 Root Cause
fetchPageContents()function retrieves page content, it is never added tochatHistory.window.onload, which may not trigger in certain cases, causingfetchPageContents()not to be called.✅ Solution
1. Add Page Context Storage
2. Add Page Content to Chat History
3. Improve Page Load Detection