{"version":"2.1.318","anchor":"workspace-diff-when-launch-folder-is-not-a-git-repo","canonical_anchor":"workspace-diff-when-launch-folder-is-not-a-git-repo","heading":"Changed files can be listed when the launch folder isn't a git repository","tier":"notice","area":"Diffs","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/workspace-diff-when-launch-folder-is-not-a-git-repo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Changed files can be listed when the launch folder isn't a git repository\n\nClaude Code can list files changed in a launch folder that isn't a git repository, using a temporary repository; needs git 2.32+\n\n**What**\n\nClaude Code normally works out which files changed by asking git, the version control tool. It can now list changes in the folder you launched it from even when that folder is not a git repository, by using a temporary repository behind the scenes. Files that look like secrets, dotfiles (files whose names start with a dot) and denied paths are skipped. This needs git 2.32 or later.\n\n**Why**\n\nRemote or bridge sessions can show which files changed even outside a git repository.\n\n- Area: Diffs\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}