{"version":"2.1.282","anchor":"automatic-recovery-when-the-api-rejects-encrypted-web-search","canonical_anchor":"automatic-recovery-when-the-api-rejects-encrypted-web-search","heading":"Conversations recover when old web search results can no longer be read","tier":"notice","area":"Web Search","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/automatic-recovery-when-the-api-rejects-encrypted-web-search","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Conversations recover when old web search results can no longer be read\n\nIf the API rejects old web search results in a conversation, Claude Code now removes them and retries instead of failing\n\n**What**\n\nWhen Claude searches the web, the results are kept in the conversation in an encrypted form. If a request fails because the API says it cannot decrypt those saved results, Claude Code now fixes the conversation itself. It:\n\n- removes past web searches, their results and the citations that pointed to them\n\n- puts a \"[Web search removed]\" note in their place where needed\n\n- tries the request again once\n\nEvery later request in that conversation also leaves the old search content out. A warning is written to the log.\n\n**Why**\n\nBefore, a conversation that had used web search could get stuck on an error it could not get past. Now it carries on. The trade-off is that Claude no longer sees the earlier search results, so you may need to ask it to search again.\n\n- Area: Web Search\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}