Tin Chi Lo c7c656e8a9 fix(cursor): convert tools and tool_choice through one envelope rule ... Chat Completions nests a named tool_choice under its tool type while the Responses API keeps it flat; ChatCompletionNamedToolChoiceParam and ChatCompletionNamedToolChoiceCustomParam both mark the nested key required. The messages arm normalized tool definitions but forwarded tool_choice at whatever level Cursor sent it, so a flat {"type": "custom", "name": "ApplyPatch"} reached OpenAI unchanged and was rejected while the tool defs beside it nested correctly A tool definition and a named tool_choice carry the same envelope, so both now convert through a single _convert_tool_envelope, and _normalize_tool_dialect moves tools and tool_choice together on each arm. That covers all four cells of {tool def, tool_choice} x {to chat, to responses} and removes the shape where one field can be converted while the other is missed, replacing three helpers with two and cutting 24 lines Also restores the end-to-end assertion that a flat tool_choice reaches chat_completion nested, which had been flipped to pin the passthrough behavior		2026-08-01 11:26:09 -07:00
..
__init__.py	[Fix] - Responses API - add /openai routes for responses API. (Azure OpenAI SDK Compatibility) (#15988)	2025-10-27 19:12:13 -07:00
test_endpoints.py	fix(cursor): convert tools and tool_choice through one envelope rule	2026-08-01 11:26:09 -07:00