You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Show web search sources as one expandable Sources row in chat
#38958
When an agent searches the web, the pages it found sit three clicks deep: expand the tool group, expand a search row, read its output. The rows are labelled with the query, not with what came back. Readers who want to check a claim against its sources have to dig, and the reply itself offers nothing readable (#30979).
Suggestion: one "Sources" row per search group
Under any tool group that searched the web, show a single collapsed row, Sources · N. It stays visible while the group is collapsed. Clicking it expands a deduped list of the pages the searches returned (title and site), and each one opens in the browser.
No server or contract change.web_search turn items already carry results (title, url) to the client. The Claude adapter fills them today.
It follows an existing pattern. It's built like the viewed-images row that tool groups already show, on web, desktop and mobile, and its open state lives in the same expanded-groups state.
Providers without result URLs get no row. Codex sends only queries, so it is unchanged. Show Codex web search citations as links to their sources #34919 covers matching Codex's inline citation ids to web_run output, and the two fit together: if Codex results become structured, they appear here too.
Working implementation
A working branch is on my fork: akash9676#2. The shared derivation is in client-runtime, with a row on web/desktop and on mobile and a focused test. I haven't captured screenshots yet.
Questions for maintainers
Is a per-group row the right place, or should sources gather once under the final answer of the turn?
Should the label say Sources · N, or is the count noise?
Want this as a PR upstream if the direction looks right?
Drafted with Claude Opus 5.5 in Claude Code, running in T3 Code.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Web search sources are hard to find in chat
When an agent searches the web, the pages it found sit three clicks deep: expand the tool group, expand a search row, read its output. The rows are labelled with the query, not with what came back. Readers who want to check a claim against its sources have to dig, and the reply itself offers nothing readable (#30979).
Suggestion: one "Sources" row per search group
Under any tool group that searched the web, show a single collapsed row, Sources · N. It stays visible while the group is collapsed. Clicking it expands a deduped list of the pages the searches returned (title and site), and each one opens in the browser.
web_searchturn items already carryresults(title,url) to the client. The Claude adapter fills them today.web_runoutput, and the two fit together: if Codex results become structured, they appear here too.Working implementation
A working branch is on my fork: akash9676#2. The shared derivation is in
client-runtime, with a row on web/desktop and on mobile and a focused test. I haven't captured screenshots yet.Questions for maintainers
Drafted with Claude Opus 5.5 in Claude Code, running in T3 Code.
All reactions