{"version":"2.1.295","anchor":"web-search-proxy-results-are-post-processed-for-subagents","canonical_anchor":"web-search-proxy-results-are-post-processed-for-subagents","heading":"Web search results are processed differently for subagents","tier":"internal","area":"Web Search","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/web-search-proxy-results-are-post-processed-for-subagents","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Web search results are processed differently for subagents\n\nOn one proxied web search route, results for subagents now pass through an extra processing step before use\n\n**Unclear.** What the extra processing does to subagent search results is not known.\n\n**What**\n\nA subagent is a helper Claude starts to handle part of a task. On one web search route that goes through a proxy, results for the main conversation are passed on unchanged as before. Results for a subagent now go through an extra processing step first. Before, every caller got the results unchanged.\n\n**Why**\n\nSubagents can now get search output that differs from what the main conversation gets.\n\n- Area: Web Search\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}