@tejas-dharani I have removed custom tools from OpenAIAgent as it is not currently implemented properly.

It doesn't seem unreachable to grab code from the Assistants API agent and carry over it in the Responses API agent?

It doesn't seem unreachable to grab code from the Assistants API agent and carry over it in the Responses API agent?

Would love to get help with that :)

For now I would like to make a release to fix various bugs related to the OpenAIAgent's validation code

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.97%. Comparing base (fbc7888) to head (868e2ab).
⚠️ Report is 1 commits behind head on main.

@@            Coverage Diff             @@
##             main    #6943      +/-   ##
==========================================
+ Coverage   80.80%   80.97%   +0.17%     
==========================================
  Files         237      237              
  Lines       18351    18148     -203     
==========================================
- Hits        14829    14696     -133     
+ Misses       3522     3452      -70     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

re: fixing various bugs - fully support, just please don't do that in the same commit as removal (if you really want to remove) the function tool population code so that it can be reverted easily if needed.

Otherwise I'd love to help with the proper function support however I'll be able to address this no earlier than this weekend, I'm not familiar with the code yet.

re: fixing various bugs - fully support, just please don't do that in the same commit as removal (if you really want to remove) the function tool population code so that it can be reverted easily if needed.

We can always go back to the older commit for pieces that we need, right? However, what I have seen is that the code behind OpenAIAgent likely needs a big refactor to make it work like the OpenAIAssistantAgent. So it's probably better to start with a clean slate.