-
Notifications
You must be signed in to change notification settings - Fork 5k
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
[ENH] accessing the run steps with GPTAssistantAgent #715
Comments
Thanks @gagb, But I don't quite see how the PR addresses the issue. You still can't access the run.id after invoking the assistant, right? |
It doesn't yet, but perhaps
|
@IANTHEREAL FYI |
@YannDubs We have implemented a feature that logs more (the parameters and results) on function calls, which should fulfill the requirements for tracing function calls. I am also considering to extend this tracing capability to other tools, such as the code interpreter, in a subsequent phase. |
Thanks, @IANTHEREAL #717 seems useful but still only concerns the function execution, right? It won't show all the steps in the assistant if you use the code interpreter, right? I might be wrong, but I was under the impression that OpenAI controls those substeps and you can only access them using |
@YannDubs Yes. Currently, I have resolved the issue with function call tracing, which is controlled by the external program itself (not openai api). To tracing openai built-in tools like code interpreter, it is necessary to utilize the |
Closing this issue due to inactivity. If you have further questions, please open a new issue or join the discussion in AutoGen Discord server: https://discord.com/invite/Yb5gwGVkE5 |
The current GPTAssistantAgent only returns the output from the last step when you call
_invoke_assistant
. But in many cases I would like to be able to see what were the intermediate calls that were made. You can get that information usingself.openai_client.beta.beta.threads.runs.steps.list(thread_id=..., run_id=..., order="asc")
as shown here. But I don't think you can currently get the run_id of the last call to get those steps. For more interpretability and when developing, it would be nice to either:run_id
to be able to get the stepsand/or
_invoke_assistant
to return all the stepsE.g. this i useful when using web search or code_interpreter to know what were the arguments and how many calls were there.
Ps: thanks for the great library 💯
The text was updated successfully, but these errors were encountered: