We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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:
The text was updated successfully, but these errors were encountered:
I agree - I think the way it's currently setup was a little against convention and may have tripped me up.
run_async to me means it is the same as run() but done in an async manner. e.g.
run_async
run() -> OutputT run_async() -> Coroutine[None, None, OutputT]
Sorry, something went wrong.
Yes exactly, my implementation was creating some false expectations so no worries!
No branches or pull requests
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: