{"version":"2.1.321","anchor":"windows-git-launcher-keep-and-artifact-publish-marker","canonical_anchor":"windows-git-launcher-keep-and-artifact-publish-marker","heading":"Windows keeps a Git for Windows launcher setting, and artifact publishing is marked","tier":"notice","area":"Windows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/windows-git-launcher-keep-and-artifact-publish-marker","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Windows keeps a Git for Windows launcher setting, and artifact publishing is marked\n\nOn Windows, startup keeps a Git for Windows launcher value in the global config, and MCP tools that publish artifacts are marked as doing so\n\n**Unclear.** What the stored Git for Windows launcher value is used for is not stated.\n\n**What**\n\nTwo small changes:\n\n- On Windows, Claude Code at startup keeps a `gitForWindowsLauncher` value in the global configuration file\n\n- When an MCP tool (an outside tool connected through the Model Context Protocol) publishes an artifact, the entry shown for that tool call is marked as publishing one, when that marking is turned on\n\n**Why**\n\nA small Windows startup change, plus a hint for how artifact publishing is shown.\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}