Problem

The Grok web_search provider returns "No response" when the xAI API uses its newer /v1/responses format.

Root Cause

The xAI Responses API returns output blocks with type: 'message' containing content blocks with type: 'output_text' and url_citation annotations. The previous code checked output[0].content[0].text without type filtering, which could fail with multiple output entries.

Fix

• Filter output blocks by type='message' and content by type='output_text'
• Extract url_citation annotations as fallback citations
• Deduplicate annotation-derived URLs
• Update GrokSearchResponse type to include annotation fields

Tests

All 26 web-search tests pass, including 4 new/updated tests for Grok response parsing.

Closes #13520

Greptile Overview

Greptile Summary

This change updates the Grok (grok) web_search provider to correctly parse xAI /v1/responses output by selecting output blocks with type: "message" and content blocks with type: "output_text", and adds a fallback path that extracts url_citation annotation URLs when top-level citations are absent. Unit tests were updated/added to cover message-block parsing, annotation citation extraction (including deduplication), and deprecated output_text fallback.

The parsing logic lives in src/agents/tools/web-search.ts and is exercised via the __testing.extractGrokContent export in src/agents/tools/web-search.test.ts.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk.
• Changes are narrowly scoped to Grok response parsing, keep backwards compatibility via the deprecated output_text fallback, and are covered by focused unit tests. No broken call sites were found beyond the updated usage in runGrokSearch.
• No files require special attention