Skip to content
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

Typo fixes - Update Orchestrating_agents.ipynb #1640

Merged
merged 1 commit into from
Feb 14, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions examples/Orchestrating_agents.ipynb
Original file line number Diff line number Diff line change
@@ -575,7 +575,7 @@
"messages.extend(response)\n",
"\n",
"\n",
"user_query = \"Actually, I want a refund.\" # implitly refers to the last item\n",
"user_query = \"Actually, I want a refund.\" # implicitly refers to the last item\n",
"print(\"User:\", user_query)\n",
"messages.append({\"role\": \"user\", \"content\": user_query})\n",
"response = run_full_turn(refund_agent, messages) # refund agent"
@@ -596,7 +596,7 @@
"\n",
"Now that agent can express the _intent_ to make a handoff, we must make it actually happen. There's many ways to do this, but there's one particularly clean way.\n",
"\n",
"For the agent functions we've defined so far, like `execute_refund` or `place_order` they return a string, which will be provided to the model. What if instead, we return an `Agent` object to indate which agent we want to transfer to? Like so:"
"For the agent functions we've defined so far, like `execute_refund` or `place_order` they return a string, which will be provided to the model. What if instead, we return an `Agent` object to indicate which agent we want to transfer to? Like so:"
]
},
{