{"version":"2.1.291","anchor":"task-output-symlink-repointing-after-a-session-transcript-re","canonical_anchor":"task-output-symlink-repointing-after-a-session-transcript-re","heading":"Background task output links are fixed up correctly after a session moves","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.291\/e\/task-output-symlink-repointing-after-a-session-transcript-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.291","markdown":"### Background task output links are fixed up correctly after a session moves\n\nAfter a session moves to another directory, Claude Code now repoints background task output links only when the move worked, using the right paths\n\n**What**\n\nBackground tasks keep their output in files that Claude Code reaches through links, shortcuts that point at the real file. When a session moves to a different working directory, those links have to be updated to the new location.\n\nClaude Code now updates them only when the session's folder actually moved successfully, and it points them from the old location to the new one. Before, this step checked the wrong condition and passed the wrong locations.\n\n**Why**\n\nAfter a session changes directory, for example following a `cd`, the output of background tasks should stay reachable instead of pointing at the wrong place.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}