Codex Windows App ignores commit message instructions

What version of the Codex App are you using (From “About Codex” dialog)?

23.306.11636

What subscription do you have?

Business

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Codex ignores any commit text instructions

What steps can reproduce the bug?

1. Go to settings
2. Git
3. Commit instructions:

When proposing a git commit message, never use the chat title, task title, branch name, or a generic summary. Base the message only on the actual staged git diff.

Use Conventional Commits and infer the most accurate type from the staged changes:
- feat: new functionality
- fix: bug fix
- security: security fix or hardening
- refactor: internal restructuring without behavior change
- perf: measurable performance improvement
- test: tests added/updated
- docs: documentation only
- style: formatting or styling only
- chore: maintenance, config, tooling, deps
- ci: CI/CD only
- build: build system only
- revert: revert

Infer scope from changed paths when possible:
- use a short lowercase scope like auth, api, ui, components, app, docs, deps
- omit scope if changes span unrelated areas

Write the subject line in imperative mood, lowercase, with no trailing period.

Primary format:
type(scope): concise summary

Rules:
- Use only facts visible in the staged diff
- Focus on what changed and why, not implementation trivia
- Do not mention the assistant, AI, Codex, chat, prompt, or generation process
- Do not write vague messages like "update files", "fix stuff", "changes", "misc", "wip"
- Do not copy the chat name
- Keep the first line under 72 characters, ideally under 50
- Prefer specific verbs: add, fix, update, remove, refactor, simplify, document, rename
- If the diff is docs/style/chore only, keep the message short
- If the diff is feat/fix/perf/security, include a short body when useful

Tiered output:
1. For feat, fix, perf, security:
   Output:
   type(scope): summary

   - key change 1
   - key change 2
   - impact or reason

2. For refactor, test, build, ci:
   Output:
   type(scope): summary

   Brief explanation of what changed and why.

3. For docs, style, chore:
   Output:
   type(scope): summary

If there are multiple unrelated changes, say so and suggest splitting into separate commits.

Always return:
1. PRIMARY commit message
2. 2 ALTERNATIVES
3. 1-line ANALYSIS explaining detected type/scope

Never return only the chat title.

Still end up with commit messages like "Save chat state".

What is the expected behavior?

Commit messages are meaningful, following conventions.

Additional information

_No response_