-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix: #1942 Enable async tool calling in Realtime sessions #1984
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
Conversation
|
|
||
| self._guardrail_tasks: set[asyncio.Task[Any]] = set() | ||
| self._tool_call_tasks: set[asyncio.Task[Any]] = set() | ||
| self._async_tool_calls: bool = bool(self._run_config.get("async_tool_calls", True)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I mentioned in the PR description, the default value is true. If we'd like to make this opt-in, we can change this part for it, and switch the default behavior to true in future minor/major versions. But I personally think setting true should be beneficial for everyone.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
codex seems right
ffd4c09 to
8f37010
Compare
This pull request resolves #1942 and the new behavior aligns with TS SDK. I think this is a kind of behavioral bug for most use cases, so I've switched the default behavior to this new one by default. If a developer wants to switch back to the current behavior, they can customize this way. That said, I cannot think of those use cases: