{"version":"2.1.299","anchor":"sandbox-override-and-git-config-env","canonical_anchor":"sandbox-override-and-git-config-env","heading":"Sandbox override confirmation now reflects the save result","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/sandbox-override-and-git-config-env","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Sandbox override confirmation now reflects the save result\n\nThe sandbox override dialog's confirmation now includes the result of saving the settings, and git config reads can use a fixed set of variables\n\n**What**\n\nThe sandbox limits what commands run by Claude Code can reach, and its \"Configure overrides\" dialog lets you change some of its settings. The confirmation message there now includes the result of saving those settings. Before, the same message was shown regardless.\n\nSeparately, when Claude Code reads git settings with a given set of environment variables (named values a program reads at start-up), it now runs git with only those variables instead of adding them to its own.\n\n**Why**\n\nThese are small fixes that make the confirmation and the git settings read more accurate.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}