{"version":"2.1.232","anchor":"files-saved-from-web-fetches-and-artifacts-are-tracked-in-se","canonical_anchor":"files-saved-from-web-fetches-and-artifacts-are-tracked-in-se","heading":"Files saved from web fetches and artifacts are tracked in session state","tier":"internal","area":"Session State","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/files-saved-from-web-fetches-and-artifacts-are-tracked-in-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Files saved from web fetches and artifacts are tracked in session state\n\nFiles Claude saves from web fetches, artifacts and binary tool output are now tracked in session state.\n\n**What**\n\nWhen Claude Code writes fetched web content, saved artifact HTML, or persisted binary tool output to disk, the file path and its directory are now recorded in app state rather than being written and forgotten.\n\n**Details**\n\n- Tool-use context carries a persisted-files list, threaded into the artifact save path and the web fetch tool; app state gains a saved-web-fetch-files list.\n- The binary persistence path records the file alongside the existing `tengu_binary_content_persisted` event.\n\n**Evidence**\n\n`persistedToolResultFiles`\n\n- Area: Session State\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5"}