Enable Tool Calls

[SailorJoe6]

Why are these changes needed?

AutoGen supports the OpenAI "tool calls" API but AutoGenStudio lacks support. Instead, the "Skills" in AutoGenStudio are currently handled via standard code execution, which doesn't always work as expected, especially when the code execution environment is Docker.

Related issue number

addresses roadmap #3058

Checks

• I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
• I've added tests (if relevant) corresponding to the changes introduced in this PR.
• I've made sure all auto checks have passed.

[SailorJoe6]

@victordibia - Here you go. Let me know what you think.

[SailorJoe6]

Ooof... another experiment I was doing. Never mind the "hard coded agents" message. I'll get that out of there.

[SailorJoe6]

Hey @victordibia, I was thinking about the conversation we were having in the older PR.
Salient points for reference:

• Configuring for Tool Calls should be done on the Agent or on the Workflow? (current thinking is on the Agent)
• Currently only have a tools_call flag, we will modify later with an agent field
• Will use a down and dirty hack for DB update, and then a more organized alembic upgrade process later on.

So, I thought of a reason we may want to configure tool calls on the Workflow after all. When configuring tool calls in code, there always needs to be 2 agents. 1) You have to decide which agent gets to call the tool, and 2) choose which agent will execute it. In the current iteration of this code, I always chose the Agent that has the "Skill" as the Agent who gets to call the code. Then, I randomly pick any old Agent to execute it (because it seemed to hardly matter to me). This works. However, I realized users may want to choose a UserProxy with Human_Input_Mode = always so they can intercept tool calls and decide if they agree or disagree with the tool being chosen.

Anyway, food for thought.

[rysweet]

This PR is against AutoGen 0.2. AutoGen 0.2 has been moved to the 0.2 branch. Please rebase your PR on the 0.2 branch or update it to work with the new AutoGen 0.4 that is now in main.

[rysweet]

This PR is against AutoGen 0.2. AutoGen 0.2 has been moved to the 0.2 branch. Please rebase your PR on the 0.2 branch or update it to work with the new AutoGen 0.4 that is now in main.