[BOT ISSUE] OpenAI: Responses API built-in tool output items not decomposed into tool spans #249

Closed
Feature
#253
Closed
[BOT ISSUE] OpenAI: Responses API built-in tool output items not decomposed into tool spans#249
Feature
#253
Assignees
AbhiPrasad
Labels
bot-automationintegration: openai

Description

@braintrust-bot
braintrust-bot
bot
opened on Apr 10, 2026

Summary

When the OpenAI Responses API returns output items from built-in tools (web_search_call, file_search_call, code_interpreter_call, computer_call, image_generation_call, mcp_call), the Braintrust wrapper stores them as opaque entries in the LLM span's output array. No child TOOL spans are created for these server-side tool invocations.

This contrasts with how other integrations in this same repo handle equivalent tool outputs — notably the Google GenAI integration, which creates dedicated SpanTypeAttribute.TOOL child spans for function calls, code execution, file search, URL context, and MCP tool calls.

What is missing

The ResponseWrapper class (py/src/braintrust/integrations/openai/tracing.py) handles all response output items uniformly:

  • Non-streaming (_parse_event_from_result, line 763): stores result["output"] as the span's output field with no item-type inspection.
  • Streaming (_postprocess_streaming_results, line 783): accumulates output items from streaming events into a flat list. Tracks response.output_item.added and content deltas, but does not differentiate by item type.

Built-in tool output items that should produce child TOOL spans:

Output item typeDescriptionChild span created?
web_search_callServer-side web search with resultsNo
file_search_callServer-side file/vector search with resultsNo
code_interpreter_callServer-side code execution with code + outputsNo
computer_callComputer use tool invocationNo
image_generation_callServer-side image generationNo
mcp_callMCP tool invocation with arguments + outputNo
function_callUser-defined function call requestNo

Comparison with other integrations in this repo

The Google GenAI integration (py/src/braintrust/integrations/google_genai/tracing.py) creates dedicated SpanTypeAttribute.TOOL spans via _log_posthoc_interaction_tool_span and _activate_interaction_tool_span for:

  • function_call / function_result
  • code_execution_call / code_execution_result
  • file_search_call / file_search_result
  • url_context_call / url_context_result
  • mcp_server_tool_call / mcp_server_tool_result

The Claude Agent SDK, Pydantic AI, Agno, ADK, AgentScope, and OpenAI Agents SDK integrations also create dedicated tool spans.

Test coverage

There are zero tests for any built-in tool type in the Responses API test file (py/src/braintrust/integrations/openai/test_openai.py). No cassettes exist for web search, file search, code interpreter, computer use, image generation, or MCP tool responses.

Braintrust docs status

not_found — The OpenAI integration page does not mention Responses API built-in tools, tool span decomposition, or server-side tool instrumentation.

Upstream sources

  • OpenAI Python SDK response output item types: openai/types/responses/ — defines response_web_search_call_*, response_file_search_call_*, response_code_interpreter_call_*, response_computer_tool_call*, response_image_gen_call_*, response_mcp_call_* event and item types (220+ type files).
  • OpenAI built-in tools documentation: https://platform.openai.com/docs/guides/tools

Local files inspected

  • py/src/braintrust/integrations/openai/tracing.py:
    • ResponseWrapper._parse_event_from_result() (line 763) — stores output as flat blob, no type inspection
    • ResponseWrapper._postprocess_streaming_results() (line 783) — accumulates output items generically, no type-specific handling for tool items
  • py/src/braintrust/integrations/openai/patchers.py (lines 282-347) — patches create() and parse() only
  • py/src/braintrust/integrations/openai/test_openai.py — no tests for any built-in tool type
  • py/src/braintrust/integrations/google_genai/tracing.py (lines 771-838) — creates SpanTypeAttribute.TOOL child spans for equivalent tool outputs (for comparison)

Metadata

Metadata

Assignees

Labels

bot-automationintegration: openai

Type

Feature

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    , 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
     blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

    Skip to content
    [BOT ISSUE] OpenAI: Responses API built-in tool output items not decomposed into tool spans #249
    Closed
    Feature
    #253
    Closed
    [BOT ISSUE] OpenAI: Responses API built-in tool output items not decomposed into tool spans#249
    Feature
    #253
    Assignees
    AbhiPrasad
    Labels
    bot-automationintegration: openai
    Description
    @braintrust-bot
    braintrust-bot
    bot
    opened on Apr 10, 2026
    Summary
    When the OpenAI Responses API returns output items from built-in tools (web_search_call, file_search_call, code_interpreter_call, computer_call, image_generation_call, mcp_call), the Braintrust wrapper stores them as opaque entries in the LLM span's output array. No child TOOL spans are created for these server-side tool invocations.
    This contrasts with how other integrations in this same repo handle equivalent tool outputs — notably the Google GenAI integration, which creates dedicated SpanTypeAttribute.TOOL child spans for function calls, code execution, file search, URL context, and MCP tool calls.
    What is missing
    The ResponseWrapper class (py/src/braintrust/integrations/openai/tracing.py) handles all response output items uniformly:
    • Non-streaming (_parse_event_from_result, line 763): stores result["output"] as the span's output field with no item-type inspection.
    • Streaming (_postprocess_streaming_results, line 783): accumulates output items from streaming events into a flat list. Tracks response.output_item.added and content deltas, but does not differentiate by item type.
    Built-in tool output items that should produce child TOOL spans:
    Output item typeDescriptionChild span created?
    web_search_callServer-side web search with resultsNo
    file_search_callServer-side file/vector search with resultsNo
    code_interpreter_callServer-side code execution with code + outputsNo
    computer_callComputer use tool invocationNo
    image_generation_callServer-side image generationNo
    mcp_callMCP tool invocation with arguments + outputNo
    function_callUser-defined function call requestNo
    Comparison with other integrations in this repo
    The Google GenAI integration (py/src/braintrust/integrations/google_genai/tracing.py) creates dedicated SpanTypeAttribute.TOOL spans via _log_posthoc_interaction_tool_span and _activate_interaction_tool_span for:
    • function_call / function_result
    • code_execution_call / code_execution_result
    • file_search_call / file_search_result
    • url_context_call / url_context_result
    • mcp_server_tool_call / mcp_server_tool_result
    The Claude Agent SDK, Pydantic AI, Agno, ADK, AgentScope, and OpenAI Agents SDK integrations also create dedicated tool spans.
    Test coverage
    There are zero tests for any built-in tool type in the Responses API test file (py/src/braintrust/integrations/openai/test_openai.py). No cassettes exist for web search, file search, code interpreter, computer use, image generation, or MCP tool responses.
    Braintrust docs status
    not_found — The OpenAI integration page does not mention Responses API built-in tools, tool span decomposition, or server-side tool instrumentation.
    Upstream sources
    • OpenAI Python SDK response output item types: openai/types/responses/ — defines response_web_search_call_*, response_file_search_call_*, response_code_interpreter_call_*, response_computer_tool_call*, response_image_gen_call_*, response_mcp_call_* event and item types (220+ type files).
    • OpenAI built-in tools documentation: https://platform.openai.com/docs/guides/tools
    Local files inspected
    • py/src/braintrust/integrations/openai/tracing.py:

      • ResponseWrapper._parse_event_from_result() (line 763) — stores output as flat blob, no type inspection
      • ResponseWrapper._postprocess_streaming_results() (line 783) — accumulates output items generically, no type-specific handling for tool items
    • py/src/braintrust/integrations/openai/patchers.py (lines 282-347) — patches create() and parse() only
    • py/src/braintrust/integrations/openai/test_openai.py — no tests for any built-in tool type
    • py/src/braintrust/integrations/google_genai/tracing.py (lines 771-838) — creates SpanTypeAttribute.TOOL child spans for equivalent tool outputs (for comparison)
    Metadata
    Metadata
    Assignees
    Labels
    bot-automationintegration: openai
    Type
    Feature
    Projects
    No projects
      Milestone
      No milestone
      Relationships
      None yet
      Development
      No branches or pull requests
      Issue actions
      
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

      Skip to content
      [BOT ISSUE] OpenAI: Responses API built-in tool output items not decomposed into tool spans #249
      Closed
      Feature
      #253
      Closed
      [BOT ISSUE] OpenAI: Responses API built-in tool output items not decomposed into tool spans#249
      Feature
      #253
      Assignees
      AbhiPrasad
      Labels
      bot-automationintegration: openai
      Description
      @braintrust-bot
      braintrust-bot
      bot
      opened on Apr 10, 2026
      Summary
      When the OpenAI Responses API returns output items from built-in tools (web_search_call, file_search_call, code_interpreter_call, computer_call, image_generation_call, mcp_call), the Braintrust wrapper stores them as opaque entries in the LLM span's output array. No child TOOL spans are created for these server-side tool invocations.
      This contrasts with how other integrations in this same repo handle equivalent tool outputs — notably the Google GenAI integration, which creates dedicated SpanTypeAttribute.TOOL child spans for function calls, code execution, file search, URL context, and MCP tool calls.
      What is missing
      The ResponseWrapper class (py/src/braintrust/integrations/openai/tracing.py) handles all response output items uniformly:
      • Non-streaming (_parse_event_from_result, line 763): stores result["output"] as the span's output field with no item-type inspection.
      • Streaming (_postprocess_streaming_results, line 783): accumulates output items from streaming events into a flat list. Tracks response.output_item.added and content deltas, but does not differentiate by item type.
      Built-in tool output items that should produce child TOOL spans:
      Output item typeDescriptionChild span created?
      web_search_callServer-side web search with resultsNo
      file_search_callServer-side file/vector search with resultsNo
      code_interpreter_callServer-side code execution with code + outputsNo
      computer_callComputer use tool invocationNo
      image_generation_callServer-side image generationNo
      mcp_callMCP tool invocation with arguments + outputNo
      function_callUser-defined function call requestNo
      Comparison with other integrations in this repo
      The Google GenAI integration (py/src/braintrust/integrations/google_genai/tracing.py) creates dedicated SpanTypeAttribute.TOOL spans via _log_posthoc_interaction_tool_span and _activate_interaction_tool_span for:
      • function_call / function_result
      • code_execution_call / code_execution_result
      • file_search_call / file_search_result
      • url_context_call / url_context_result
      • mcp_server_tool_call / mcp_server_tool_result
      The Claude Agent SDK, Pydantic AI, Agno, ADK, AgentScope, and OpenAI Agents SDK integrations also create dedicated tool spans.
      Test coverage
      There are zero tests for any built-in tool type in the Responses API test file (py/src/braintrust/integrations/openai/test_openai.py). No cassettes exist for web search, file search, code interpreter, computer use, image generation, or MCP tool responses.
      Braintrust docs status
      not_found — The OpenAI integration page does not mention Responses API built-in tools, tool span decomposition, or server-side tool instrumentation.
      Upstream sources
      • OpenAI Python SDK response output item types: openai/types/responses/ — defines response_web_search_call_*, response_file_search_call_*, response_code_interpreter_call_*, response_computer_tool_call*, response_image_gen_call_*, response_mcp_call_* event and item types (220+ type files).
      • OpenAI built-in tools documentation: https://platform.openai.com/docs/guides/tools
      Local files inspected
      • py/src/braintrust/integrations/openai/tracing.py:

        • ResponseWrapper._parse_event_from_result() (line 763) — stores output as flat blob, no type inspection
        • ResponseWrapper._postprocess_streaming_results() (line 783) — accumulates output items generically, no type-specific handling for tool items
      • py/src/braintrust/integrations/openai/patchers.py (lines 282-347) — patches create() and parse() only
      • py/src/braintrust/integrations/openai/test_openai.py — no tests for any built-in tool type
      • py/src/braintrust/integrations/google_genai/tracing.py (lines 771-838) — creates SpanTypeAttribute.TOOL child spans for equivalent tool outputs (for comparison)
      Metadata
      Metadata
      Assignees
      Labels
      bot-automationintegration: openai
      Type
      Feature
      Projects
      No projects
        Milestone
        No milestone
        Relationships
        None yet
        Development
        No branches or pull requests
        Issue actions
        
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

        Skip to content
        [BOT ISSUE] OpenAI: Responses API built-in tool output items not decomposed into tool spans #249
        Closed
        Feature
        #253
        Closed
        [BOT ISSUE] OpenAI: Responses API built-in tool output items not decomposed into tool spans#249
        Feature
        #253
        Assignees
        AbhiPrasad
        Labels
        bot-automationintegration: openai
        Description
        @braintrust-bot
        braintrust-bot
        bot
        opened on Apr 10, 2026
        Summary
        When the OpenAI Responses API returns output items from built-in tools (web_search_call, file_search_call, code_interpreter_call, computer_call, image_generation_call, mcp_call), the Braintrust wrapper stores them as opaque entries in the LLM span's output array. No child TOOL spans are created for these server-side tool invocations.
        This contrasts with how other integrations in this same repo handle equivalent tool outputs — notably the Google GenAI integration, which creates dedicated SpanTypeAttribute.TOOL child spans for function calls, code execution, file search, URL context, and MCP tool calls.
        What is missing
        The ResponseWrapper class (py/src/braintrust/integrations/openai/tracing.py) handles all response output items uniformly:
        • Non-streaming (_parse_event_from_result, line 763): stores result["output"] as the span's output field with no item-type inspection.
        • Streaming (_postprocess_streaming_results, line 783): accumulates output items from streaming events into a flat list. Tracks response.output_item.added and content deltas, but does not differentiate by item type.
        Built-in tool output items that should produce child TOOL spans:
        Output item typeDescriptionChild span created?
        web_search_callServer-side web search with resultsNo
        file_search_callServer-side file/vector search with resultsNo
        code_interpreter_callServer-side code execution with code + outputsNo
        computer_callComputer use tool invocationNo
        image_generation_callServer-side image generationNo
        mcp_callMCP tool invocation with arguments + outputNo
        function_callUser-defined function call requestNo
        Comparison with other integrations in this repo
        The Google GenAI integration (py/src/braintrust/integrations/google_genai/tracing.py) creates dedicated SpanTypeAttribute.TOOL spans via _log_posthoc_interaction_tool_span and _activate_interaction_tool_span for:
        • function_call / function_result
        • code_execution_call / code_execution_result
        • file_search_call / file_search_result
        • url_context_call / url_context_result
        • mcp_server_tool_call / mcp_server_tool_result
        The Claude Agent SDK, Pydantic AI, Agno, ADK, AgentScope, and OpenAI Agents SDK integrations also create dedicated tool spans.
        Test coverage
        There are zero tests for any built-in tool type in the Responses API test file (py/src/braintrust/integrations/openai/test_openai.py). No cassettes exist for web search, file search, code interpreter, computer use, image generation, or MCP tool responses.
        Braintrust docs status
        not_found — The OpenAI integration page does not mention Responses API built-in tools, tool span decomposition, or server-side tool instrumentation.
        Upstream sources
        • OpenAI Python SDK response output item types: openai/types/responses/ — defines response_web_search_call_*, response_file_search_call_*, response_code_interpreter_call_*, response_computer_tool_call*, response_image_gen_call_*, response_mcp_call_* event and item types (220+ type files).
        • OpenAI built-in tools documentation: https://platform.openai.com/docs/guides/tools
        Local files inspected
        • py/src/braintrust/integrations/openai/tracing.py:

          • ResponseWrapper._parse_event_from_result() (line 763) — stores output as flat blob, no type inspection
          • ResponseWrapper._postprocess_streaming_results() (line 783) — accumulates output items generically, no type-specific handling for tool items
        • py/src/braintrust/integrations/openai/patchers.py (lines 282-347) — patches create() and parse() only
        • py/src/braintrust/integrations/openai/test_openai.py — no tests for any built-in tool type
        • py/src/braintrust/integrations/google_genai/tracing.py (lines 771-838) — creates SpanTypeAttribute.TOOL child spans for equivalent tool outputs (for comparison)
        Metadata
        Metadata
        Assignees
        Labels
        bot-automationintegration: openai
        Type
        Feature
        Projects
        No projects
          Milestone
          No milestone
          Relationships
          None yet
          Development
          No branches or pull requests
          Issue actions
          
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

          Skip to content
          [BOT ISSUE] OpenAI: Responses API built-in tool output items not decomposed into tool spans #249
          Closed
          Feature
          #253
          Closed
          [BOT ISSUE] OpenAI: Responses API built-in tool output items not decomposed into tool spans#249
          Feature
          #253
          Assignees
          AbhiPrasad
          Labels
          bot-automationintegration: openai
          Description
          @braintrust-bot
          braintrust-bot
          bot
          opened on Apr 10, 2026
          Summary
          When the OpenAI Responses API returns output items from built-in tools (web_search_call, file_search_call, code_interpreter_call, computer_call, image_generation_call, mcp_call), the Braintrust wrapper stores them as opaque entries in the LLM span's output array. No child TOOL spans are created for these server-side tool invocations.
          This contrasts with how other integrations in this same repo handle equivalent tool outputs — notably the Google GenAI integration, which creates dedicated SpanTypeAttribute.TOOL child spans for function calls, code execution, file search, URL context, and MCP tool calls.
          What is missing
          The ResponseWrapper class (py/src/braintrust/integrations/openai/tracing.py) handles all response output items uniformly:
          • Non-streaming (_parse_event_from_result, line 763): stores result["output"] as the span's output field with no item-type inspection.
          • Streaming (_postprocess_streaming_results, line 783): accumulates output items from streaming events into a flat list. Tracks response.output_item.added and content deltas, but does not differentiate by item type.
          Built-in tool output items that should produce child TOOL spans:
          Output item typeDescriptionChild span created?
          web_search_callServer-side web search with resultsNo
          file_search_callServer-side file/vector search with resultsNo
          code_interpreter_callServer-side code execution with code + outputsNo
          computer_callComputer use tool invocationNo
          image_generation_callServer-side image generationNo
          mcp_callMCP tool invocation with arguments + outputNo
          function_callUser-defined function call requestNo
          Comparison with other integrations in this repo
          The Google GenAI integration (py/src/braintrust/integrations/google_genai/tracing.py) creates dedicated SpanTypeAttribute.TOOL spans via _log_posthoc_interaction_tool_span and _activate_interaction_tool_span for:
          • function_call / function_result
          • code_execution_call / code_execution_result
          • file_search_call / file_search_result
          • url_context_call / url_context_result
          • mcp_server_tool_call / mcp_server_tool_result
          The Claude Agent SDK, Pydantic AI, Agno, ADK, AgentScope, and OpenAI Agents SDK integrations also create dedicated tool spans.
          Test coverage
          There are zero tests for any built-in tool type in the Responses API test file (py/src/braintrust/integrations/openai/test_openai.py). No cassettes exist for web search, file search, code interpreter, computer use, image generation, or MCP tool responses.
          Braintrust docs status
          not_found — The OpenAI integration page does not mention Responses API built-in tools, tool span decomposition, or server-side tool instrumentation.
          Upstream sources
          • OpenAI Python SDK response output item types: openai/types/responses/ — defines response_web_search_call_*, response_file_search_call_*, response_code_interpreter_call_*, response_computer_tool_call*, response_image_gen_call_*, response_mcp_call_* event and item types (220+ type files).
          • OpenAI built-in tools documentation: https://platform.openai.com/docs/guides/tools
          Local files inspected
          • py/src/braintrust/integrations/openai/tracing.py:

            • ResponseWrapper._parse_event_from_result() (line 763) — stores output as flat blob, no type inspection
            • ResponseWrapper._postprocess_streaming_results() (line 783) — accumulates output items generically, no type-specific handling for tool items
          • py/src/braintrust/integrations/openai/patchers.py (lines 282-347) — patches create() and parse() only
          • py/src/braintrust/integrations/openai/test_openai.py — no tests for any built-in tool type
          • py/src/braintrust/integrations/google_genai/tracing.py (lines 771-838) — creates SpanTypeAttribute.TOOL child spans for equivalent tool outputs (for comparison)
          Metadata
          Metadata
          Assignees
          Labels
          bot-automationintegration: openai
          Type
          Feature
          Projects
          No projects
            Milestone
            No milestone
            Relationships
            None yet
            Development
            No branches or pull requests
            Issue actions
            
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

            Skip to content
            [BOT ISSUE] OpenAI: Responses API built-in tool output items not decomposed into tool spans #249
            Closed
            Feature
            #253
            Closed
            [BOT ISSUE] OpenAI: Responses API built-in tool output items not decomposed into tool spans#249
            Feature
            #253
            Assignees
            AbhiPrasad
            Labels
            bot-automationintegration: openai
            Description
            @braintrust-bot
            braintrust-bot
            bot
            opened on Apr 10, 2026
            Summary
            When the OpenAI Responses API returns output items from built-in tools (web_search_call, file_search_call, code_interpreter_call, computer_call, image_generation_call, mcp_call), the Braintrust wrapper stores them as opaque entries in the LLM span's output array. No child TOOL spans are created for these server-side tool invocations.
            This contrasts with how other integrations in this same repo handle equivalent tool outputs — notably the Google GenAI integration, which creates dedicated SpanTypeAttribute.TOOL child spans for function calls, code execution, file search, URL context, and MCP tool calls.
            What is missing
            The ResponseWrapper class (py/src/braintrust/integrations/openai/tracing.py) handles all response output items uniformly:
            • Non-streaming (_parse_event_from_result, line 763): stores result["output"] as the span's output field with no item-type inspection.
            • Streaming (_postprocess_streaming_results, line 783): accumulates output items from streaming events into a flat list. Tracks response.output_item.added and content deltas, but does not differentiate by item type.
            Built-in tool output items that should produce child TOOL spans:
            Output item typeDescriptionChild span created?
            web_search_callServer-side web search with resultsNo
            file_search_callServer-side file/vector search with resultsNo
            code_interpreter_callServer-side code execution with code + outputsNo
            computer_callComputer use tool invocationNo
            image_generation_callServer-side image generationNo
            mcp_callMCP tool invocation with arguments + outputNo
            function_callUser-defined function call requestNo
            Comparison with other integrations in this repo
            The Google GenAI integration (py/src/braintrust/integrations/google_genai/tracing.py) creates dedicated SpanTypeAttribute.TOOL spans via _log_posthoc_interaction_tool_span and _activate_interaction_tool_span for:
            • function_call / function_result
            • code_execution_call / code_execution_result
            • file_search_call / file_search_result
            • url_context_call / url_context_result
            • mcp_server_tool_call / mcp_server_tool_result
            The Claude Agent SDK, Pydantic AI, Agno, ADK, AgentScope, and OpenAI Agents SDK integrations also create dedicated tool spans.
            Test coverage
            There are zero tests for any built-in tool type in the Responses API test file (py/src/braintrust/integrations/openai/test_openai.py). No cassettes exist for web search, file search, code interpreter, computer use, image generation, or MCP tool responses.
            Braintrust docs status
            not_found — The OpenAI integration page does not mention Responses API built-in tools, tool span decomposition, or server-side tool instrumentation.
            Upstream sources
            • OpenAI Python SDK response output item types: openai/types/responses/ — defines response_web_search_call_*, response_file_search_call_*, response_code_interpreter_call_*, response_computer_tool_call*, response_image_gen_call_*, response_mcp_call_* event and item types (220+ type files).
            • OpenAI built-in tools documentation: https://platform.openai.com/docs/guides/tools
            Local files inspected
            • py/src/braintrust/integrations/openai/tracing.py:

              • ResponseWrapper._parse_event_from_result() (line 763) — stores output as flat blob, no type inspection
              • ResponseWrapper._postprocess_streaming_results() (line 783) — accumulates output items generically, no type-specific handling for tool items
            • py/src/braintrust/integrations/openai/patchers.py (lines 282-347) — patches create() and parse() only
            • py/src/braintrust/integrations/openai/test_openai.py — no tests for any built-in tool type
            • py/src/braintrust/integrations/google_genai/tracing.py (lines 771-838) — creates SpanTypeAttribute.TOOL child spans for equivalent tool outputs (for comparison)
            Metadata
            Metadata
            Assignees
            Labels
            bot-automationintegration: openai
            Type
            Feature
            Projects
            No projects
              Milestone
              No milestone
              Relationships
              None yet
              Development
              No branches or pull requests
              Issue actions
              
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

              Skip to content
              [BOT ISSUE] OpenAI: Responses API built-in tool output items not decomposed into tool spans #249
              Closed
              Feature
              #253
              Closed
              [BOT ISSUE] OpenAI: Responses API built-in tool output items not decomposed into tool spans#249
              Feature
              #253
              Assignees
              AbhiPrasad
              Labels
              bot-automationintegration: openai
              Description
              @braintrust-bot
              braintrust-bot
              bot
              opened on Apr 10, 2026
              Summary
              When the OpenAI Responses API returns output items from built-in tools (web_search_call, file_search_call, code_interpreter_call, computer_call, image_generation_call, mcp_call), the Braintrust wrapper stores them as opaque entries in the LLM span's output array. No child TOOL spans are created for these server-side tool invocations.
              This contrasts with how other integrations in this same repo handle equivalent tool outputs — notably the Google GenAI integration, which creates dedicated SpanTypeAttribute.TOOL child spans for function calls, code execution, file search, URL context, and MCP tool calls.
              What is missing
              The ResponseWrapper class (py/src/braintrust/integrations/openai/tracing.py) handles all response output items uniformly:
              • Non-streaming (_parse_event_from_result, line 763): stores result["output"] as the span's output field with no item-type inspection.
              • Streaming (_postprocess_streaming_results, line 783): accumulates output items from streaming events into a flat list. Tracks response.output_item.added and content deltas, but does not differentiate by item type.
              Built-in tool output items that should produce child TOOL spans:
              Output item typeDescriptionChild span created?
              web_search_callServer-side web search with resultsNo
              file_search_callServer-side file/vector search with resultsNo
              code_interpreter_callServer-side code execution with code + outputsNo
              computer_callComputer use tool invocationNo
              image_generation_callServer-side image generationNo
              mcp_callMCP tool invocation with arguments + outputNo
              function_callUser-defined function call requestNo
              Comparison with other integrations in this repo
              The Google GenAI integration (py/src/braintrust/integrations/google_genai/tracing.py) creates dedicated SpanTypeAttribute.TOOL spans via _log_posthoc_interaction_tool_span and _activate_interaction_tool_span for:
              • function_call / function_result
              • code_execution_call / code_execution_result
              • file_search_call / file_search_result
              • url_context_call / url_context_result
              • mcp_server_tool_call / mcp_server_tool_result
              The Claude Agent SDK, Pydantic AI, Agno, ADK, AgentScope, and OpenAI Agents SDK integrations also create dedicated tool spans.
              Test coverage
              There are zero tests for any built-in tool type in the Responses API test file (py/src/braintrust/integrations/openai/test_openai.py). No cassettes exist for web search, file search, code interpreter, computer use, image generation, or MCP tool responses.
              Braintrust docs status
              not_found — The OpenAI integration page does not mention Responses API built-in tools, tool span decomposition, or server-side tool instrumentation.
              Upstream sources
              • OpenAI Python SDK response output item types: openai/types/responses/ — defines response_web_search_call_*, response_file_search_call_*, response_code_interpreter_call_*, response_computer_tool_call*, response_image_gen_call_*, response_mcp_call_* event and item types (220+ type files).
              • OpenAI built-in tools documentation: https://platform.openai.com/docs/guides/tools
              Local files inspected
              • py/src/braintrust/integrations/openai/tracing.py:

                • ResponseWrapper._parse_event_from_result() (line 763) — stores output as flat blob, no type inspection
                • ResponseWrapper._postprocess_streaming_results() (line 783) — accumulates output items generically, no type-specific handling for tool items
              • py/src/braintrust/integrations/openai/patchers.py (lines 282-347) — patches create() and parse() only
              • py/src/braintrust/integrations/openai/test_openai.py — no tests for any built-in tool type
              • py/src/braintrust/integrations/google_genai/tracing.py (lines 771-838) — creates SpanTypeAttribute.TOOL child spans for equivalent tool outputs (for comparison)
              Metadata
              Metadata
              Assignees
              Labels
              bot-automationintegration: openai
              Type
              Feature
              Projects
              No projects
                Milestone
                No milestone
                Relationships
                None yet
                Development
                No branches or pull requests
                Issue actions
                
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

                Skip to content
                [BOT ISSUE] OpenAI: Responses API built-in tool output items not decomposed into tool spans #249
                Closed
                Feature
                #253
                Closed
                [BOT ISSUE] OpenAI: Responses API built-in tool output items not decomposed into tool spans#249
                Feature
                #253
                Assignees
                AbhiPrasad
                Labels
                bot-automationintegration: openai
                Description
                @braintrust-bot
                braintrust-bot
                bot
                opened on Apr 10, 2026
                Summary
                When the OpenAI Responses API returns output items from built-in tools (web_search_call, file_search_call, code_interpreter_call, computer_call, image_generation_call, mcp_call), the Braintrust wrapper stores them as opaque entries in the LLM span's output array. No child TOOL spans are created for these server-side tool invocations.
                This contrasts with how other integrations in this same repo handle equivalent tool outputs — notably the Google GenAI integration, which creates dedicated SpanTypeAttribute.TOOL child spans for function calls, code execution, file search, URL context, and MCP tool calls.
                What is missing
                The ResponseWrapper class (py/src/braintrust/integrations/openai/tracing.py) handles all response output items uniformly:
                • Non-streaming (_parse_event_from_result, line 763): stores result["output"] as the span's output field with no item-type inspection.
                • Streaming (_postprocess_streaming_results, line 783): accumulates output items from streaming events into a flat list. Tracks response.output_item.added and content deltas, but does not differentiate by item type.
                Built-in tool output items that should produce child TOOL spans:
                Output item typeDescriptionChild span created?
                web_search_callServer-side web search with resultsNo
                file_search_callServer-side file/vector search with resultsNo
                code_interpreter_callServer-side code execution with code + outputsNo
                computer_callComputer use tool invocationNo
                image_generation_callServer-side image generationNo
                mcp_callMCP tool invocation with arguments + outputNo
                function_callUser-defined function call requestNo
                Comparison with other integrations in this repo
                The Google GenAI integration (py/src/braintrust/integrations/google_genai/tracing.py) creates dedicated SpanTypeAttribute.TOOL spans via _log_posthoc_interaction_tool_span and _activate_interaction_tool_span for:
                • function_call / function_result
                • code_execution_call / code_execution_result
                • file_search_call / file_search_result
                • url_context_call / url_context_result
                • mcp_server_tool_call / mcp_server_tool_result
                The Claude Agent SDK, Pydantic AI, Agno, ADK, AgentScope, and OpenAI Agents SDK integrations also create dedicated tool spans.
                Test coverage
                There are zero tests for any built-in tool type in the Responses API test file (py/src/braintrust/integrations/openai/test_openai.py). No cassettes exist for web search, file search, code interpreter, computer use, image generation, or MCP tool responses.
                Braintrust docs status
                not_found — The OpenAI integration page does not mention Responses API built-in tools, tool span decomposition, or server-side tool instrumentation.
                Upstream sources
                • OpenAI Python SDK response output item types: openai/types/responses/ — defines response_web_search_call_*, response_file_search_call_*, response_code_interpreter_call_*, response_computer_tool_call*, response_image_gen_call_*, response_mcp_call_* event and item types (220+ type files).
                • OpenAI built-in tools documentation: https://platform.openai.com/docs/guides/tools
                Local files inspected
                • py/src/braintrust/integrations/openai/tracing.py:

                  • ResponseWrapper._parse_event_from_result() (line 763) — stores output as flat blob, no type inspection
                  • ResponseWrapper._postprocess_streaming_results() (line 783) — accumulates output items generically, no type-specific handling for tool items
                • py/src/braintrust/integrations/openai/patchers.py (lines 282-347) — patches create() and parse() only
                • py/src/braintrust/integrations/openai/test_openai.py — no tests for any built-in tool type
                • py/src/braintrust/integrations/google_genai/tracing.py (lines 771-838) — creates SpanTypeAttribute.TOOL child spans for equivalent tool outputs (for comparison)
                Metadata
                Metadata
                Assignees
                Labels
                bot-automationintegration: openai
                Type
                Feature
                Projects
                No projects
                  Milestone
                  No milestone
                  Relationships
                  None yet
                  Development
                  No branches or pull requests
                  Issue actions