{"version":"2.1.318","anchor":"diff-panel-hook-replaced-by-a-relaunch-pinned-to-the-current","canonical_anchor":"diff-panel-hook-replaced-by-a-relaunch-pinned-to-the-current","heading":"A step that used to open the diff panel now restarts Claude Code instead","tier":"notice","area":"Diffs","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/diff-panel-hook-replaced-by-a-relaunch-pinned-to-the-current","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### A step that used to open the diff panel now restarts Claude Code instead\n\nA step that used to switch the diff panel on now restarts Claude Code, using the same program file that is already running\n\n**Unclear.** It is not clear which action triggers this restart.\n\n**What**\n\nA step in Claude Code that used to make the diff panel visible now restarts Claude Code instead. The diff panel is the side view that shows file changes. The restart deliberately uses the same program file that is running now, rather than looking for a different or newer copy.\n\n**Why**\n\nIn practice, whatever used to bring up the diff panel at this point now relaunches Claude Code from its current program file. This may be part of how Claude Code restarts itself after an update.\n\n- Area: Diffs\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}