-
-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve support for sync/async & streaming/non-streaming #76
Comments
I agree - I think the way it's currently setup was a little against convention and may have tripped me up.
|
Yes exactly, my implementation was creating some false expectations so no worries! |
Hi, when will new run_async available? |
Closing this as a duplicate of #100 due to the fact that it is better worded. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now we can use the .run() method in BaseAgent for normal responses, and .run_async() for streaming responses.
It would be even better to support all 4 possible configurations and have:
(Exact naming scheme to be decided)
The text was updated successfully, but these errors were encountered: