{"version":"2.1.251","anchor":"plugin-eval-sandbox-separates-its-git-config-from-the-host","canonical_anchor":"plugin-eval-sandbox-separates-its-git-config-from-the-host","heading":"Plugin eval sandbox separates its git config from the host","tier":"internal","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/plugin-eval-sandbox-separates-its-git-config-from-the-host","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Plugin eval sandbox separates its git config from the host\n\nEval sandboxes get their own git config so they don't read your machine's setup.\n\n**What**\n\nSetting up an eval sandbox now records a separate operator config directory and writes its own shared git config, common-directory pointer and hooks directory, so evals do not read the surrounding machine's git setup. On macOS the sandbox uses prefixed temp paths under `\/tmp`.\n\n**Details**\n\n- the temp path layout differs by platform; the config and hooks setup is unconditional\n\n**Evidence**\n\n`operatorConfigDir: He()`\n\n- Area: Plugin Eval\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}