{"version":"2.1.315","anchor":"savedbackground-output-folders-detected-in-shell-commands","canonical_anchor":"savedbackground-output-folders-detected-in-shell-commands","heading":"Claude Code notices shell commands that touch its saved-output folders","tier":"internal","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/savedbackground-output-folders-detected-in-shell-commands","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Claude Code notices shell commands that touch its saved-output folders\n\nClaude Code can now tell when a shell command refers to its saved-result folder, its background-output folder, or both\n\n**Unclear.** It is not clear what Claude Code does with the result of this check.\n\n**What**\n\nClaude Code keeps some tool results and the output of background tasks in folders on disk. It now checks each shell command for a mention of those folders and sorts it as touching the saved-result folder, the background-output folder, or both.\n\nIf Claude Code cannot find where those folders are, it logs \"The folders of saved output could not be looked up\".\n\n**Why**\n\nThis lets Claude Code recognise when a command is reading back output it saved earlier, rather than ordinary files.\n\n- Area: Bash Tool\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}