01e4a28f0a
Some upstream providers (e.g. Antigravity) return non-standard finish_reason values like 'other' instead of the OpenAI-standard 'tool_calls' when the model invokes tools. This causes downstream consumers (e.g. OpenClaw) to fail to execute tool calls, breaking agentic sub-agent workflows. Changes: - nonStreamingHandler: post-translation guard that normalizes finish_reason to 'tool_calls' when message.tool_calls is present - sseToJsonHandler: accumulate tool_calls from streaming deltas in parseSSEToOpenAIResponse; extract function_call items from Responses API output in handleForcedSSEToJson - openai-responses translator: use toolCallIndex to choose between 'tool_calls' and 'stop' in flush and response.completed events Tested: 7 scenarios (non-stream text, single/multiple tool calls, stream text/tool calls, multi-turn tool conversation, tools present but unused) |
||
|---|---|---|
| .. | ||
| claude-to-openai.js | ||
| cursor-to-openai.js | ||
| gemini-to-openai.js | ||
| kiro-to-openai.js | ||
| ollama-to-openai.js | ||
| openai-responses.js | ||
| openai-to-antigravity.js | ||
| openai-to-claude.js | ||