feat: Add custom fetch logic for agent #1010
Merged
Conversation
This file contains 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
v1xingyue
changed the title
v1xingyue
changed the title
v1xingyue
changed the title
|
I don't love it but I see the utility and I can't offer anything better. Thanks for the PR. |
odilitime
approved these changes
Dec 12, 2024
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.
Background
When user want to see what happend when generate text or image with llm, They may want to what eliza send to llm model endpoint.
What does this PR do?
Mostly llm api has fetch opts which can be passed from agent construtor.
Testing
Where should a reviewer start?
You can run pnpm run start --character
Then you will see custom fetch output.