Rohan Mehta

[2/n] Add MCP support to Runner ### Summary: This enables users to **use** MCP inside the SDK. 1. You add a list of MCP servers to `Agent`, via `mcp_server=[...]` 2. When an agent runs, we look up its MCP tools and add them to the list of tools. 3. When a tool call occurs, we call the relevant MCP server. Notes: 1. There's some refactoring to make sure we send the full list of tools to the Runner/Model etc. 2. Right now, you could have a locally defined tool that conflicts with an MCP defined tool. I didn't add errors for that, will do in a followup. ### Test Plan: See unit tests. Also has an end to end example next PR.

Allow full web search tool config (#13675) Previously, we could only configure whether web search was on/off. This PR enables sending along a web search config, which includes all the stuff responsesapi supports: filters, location, etc.

Tests for realtime session (#1080)

Prompts support (#876) Add support for the new openai prompts feature.

Realtime: use SDK types for all messages (#1134) To ensure we are using correct events, using the realtime types from the openai sdk. Added conversion tests as well. --- [//]: # (BEGIN SAPLING FOOTER) * #1135 * __->__ #1134

Realtime: enable a playback tracker (#1242) So far, we've been assuming that audio is played: - immediately (i.e. with 0 delay/latency) - at realtime This causes issues with our interrupt tracking. The model wants to know how much audio the user has actually heard. For example in a phone call agent, this wouldn't work (bc theres a delay of a few hundred ms between model sending audio and the user hearing it). This PR allows you to pass a playback tracker. --- [//]: # (BEGIN SAPLING FOOTER) * #1252 * #1216 * #1243 * __->__ #1242

Realtime: forward exceptions from transport layer (#1107) The model listens to websocket events in a separate task, and the session receives those events in on_event. So if there's e.g. a websocket or json exception, it's silently dropped. Similar to the streaming text agents, we should: - capture exceptions separately - raise them in `async for event in session` loop. Added tests to verify. --- [//]: # (BEGIN SAPLING FOOTER) * #1112 * #1111 * __->__ #1107 * #1106

[1/n] Add MCP types to the SDK ### Summary: 1. Add the MCP dep for python 3.10, since it doesn't support 3.9 and below 2. Create MCPServer, which is the agents SDK representation of an MCP server 3. Create implementations for HTTP-SSE and StdIO servers, directly copying the [MCP SDK example](https://github.com/modelcontextprotocol/python-sdk/blob/main/examples/clients/simple-chatbot/mcp_simple_chatbot/main.py) 4. Add a util to transform MCP tools into Agent SDK tools Note: I added optional caching support to the servers. That way, if you happen to know a server's tools don't change, you can just cache them. ### Test Plan: Checks pass. I added tests at the end of the stack.

Introduce tool_use_behavior on agents

[1/n] Add MCP types to the SDK ### Summary: 1. Add the MCP dep for python 3.10, since it doesn't support 3.9 and below 2. Create MCPServer, which is the agents SDK representation of an MCP server 3. Create implementations for HTTP-SSE and StdIO servers, directly copying the [MCP SDK example](https://github.com/modelcontextprotocol/python-sdk/blob/main/examples/clients/simple-chatbot/mcp_simple_chatbot/main.py) 4. Add a util to transform MCP tools into Agent SDK tools Note: I added optional caching support to the servers. That way, if you happen to know a server's tools don't change, you can just cache them. ### Test Plan: Checks pass. I added tests at the end of the stack.