Problem

Grok web search via tools.web.search.provider: grok always returned 'No response'.

Root Cause

The xAI /v1/responses API returns multiple output items when web search is used:

• output[0]: web_search_call (tool invocation, no text)
• output[1]: message (actual response with text)

extractGrokContent() was hardcoded to read output[0].content[0].text, which is the web search tool call — it has no text content.

Fix

Find the message type output item via .find() instead of assuming index 0. Added fallbacks for non-search responses and the legacy output_text field.

Testing

Verified with live xAI API — search queries now return full content with citations.

Greptile Overview

Greptile Summary

This change updates Grok (xAI /v1/responses) web-search parsing to pull the assistant text from the output[] item with type === "message", instead of assuming output[0] contains text. It also keeps a fallback to the first output item for non-search responses and preserves support for the legacy output_text field.

Overall, the change is localized to extractGrokContent() in src/agents/tools/web-search.ts and aligns with the described xAI response shape when web search is enabled (tool call item followed by message item).

Confidence Score: 5/5

• This PR is safe to merge with minimal risk.
• The change is small, isolated to Grok response text extraction, and adds a more correct selection of the message output item while preserving existing fallbacks. No breaking interface changes or broader behavioral changes were found in the diff.
• No files require special attention

_{(2/5) Greptile learns from your feedback when you react with thumbs up/down!}