Repository navigation
fixing research tool - #55
Merged
Merged
Conversation
SumanthPal
approved these changes
Feb 11, 2026
SumanthPal
left a comment
SumanthPal
left a comment
Collaborator
There was a problem hiding this comment.
seems good for now, but i don't reccomend hardcoding the uuid in the db. tests dont matter at our stage.
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
2 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.
Changed the previous implementation of the tool and the database table (primary key is now the crypto_token). Added recency rules and a "shared agent cache" where the agents reference the research_artifact_table before calling Perplexity.