{"version":"2.1.292","anchor":"websearch-ccr-proxy-check-simplified","canonical_anchor":"websearch-ccr-proxy-check-simplified","heading":"Web search in remote sessions no longer skips the proxy when web fetch is disabled","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/websearch-ccr-proxy-check-simplified","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Web search in remote sessions no longer skips the proxy when web fetch is disabled\n\nWhether web search goes through the remote-session proxy no longer depends on web fetch being disabled\n\n**Unclear.** It is not clear whether the new host check still keeps sessions with web fetch disabled away from the proxy.\n\n**What**\n\nWebSearch is the tool Claude uses to search the web. In a remote session, Claude Code can send those searches through a proxy. The rules for using that proxy have been simplified.\n\nBefore, a remote session did not use the proxy if `CLAUDE_CODE_DISABLE_WEB_FETCH` was set or a server-side check failed. Those conditions have been removed. The proxy is now used based on whether you sign in directly with Anthropic and on `CLAUDE_CODE_WEBSEARCH_USE_CCR_PROXY`, followed by a check on the host.\n\n**Why**\n\nRemote sessions that have web fetch disabled may now send their searches through the proxy.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}