{"version":"2.1.269","anchor":"omitgitstatus-forced-when-customsystemprompt-is-set","canonical_anchor":"omitgitstatus-forced-when-customsystemprompt-is-set","heading":"omitGitStatus forced when customSystemPrompt is set","tier":"notice","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/omitgitstatus-forced-when-customsystemprompt-is-set","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### omitGitStatus forced when customSystemPrompt is set\n\nSessions with a custom system prompt now automatically omit git status from prompt context\n\n**What**\n\nWhen a session is started with a custom system prompt (typically an SDK or other non-interactive use of Claude Code), it now automatically sets `omitGitStatus: true`, which leaves out the current git status from the context given to the model.\n\n**Why**\n\nGit status is normally included to give Claude awareness of uncommitted changes, but a custom system prompt usually means the caller is building a specialized setup where that default context may not be wanted or relevant, so it's now skipped automatically in that case.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}