Native "Commit" button ignores custom Git instructions and generates empty commit body (unlike Chat command)
Open 💬 13 comments Opened Feb 10, 2026 by coygeek
What version of the Codex App are you using (From “About Codex” dialog)?
Version 260208.1016 (571)
What subscription do you have?
Pro
What issue are you seeing?
There is a discrepancy in behavior between the native "Commit" / "Commit and push" button (located in the top right of the UI) and the Chat Agent.
I have configured Settings > Git > Commit instructions with a specific prompt (Conventional Commits 1.0.0).
- The Bug: When using the UI "Commit" button, Codex generates a short, single-line commit message (Title only). It creates no description/body and completely ignores the custom instructions in Settings.
- The Working Path: When I type "commit and push" directly into the Chat input, Codex correctly follows the custom instructions, generates a Conventional Commit title, and includes a detailed description body.
The UI button seems to use a different, inferior logic path than the Chat Agent.
What steps can reproduce the bug?
- Go to Settings > Git.
- Add custom text to Commit instructions (e.g., "Use Conventional Commits 1.0.0...").
- Make changes to a file in the repository so there are unstaged changes.
- Click the Commit (or "Commit and push") button in the top right header of the app.
- Observe: The pop-up dialog generates a commit message. It will usually be a single line (Title only) and ignores the formatting rules defined in settings.
- Contrast: Cancel that, and type "commit these changes" into the main Chat window.
- Observe: The Agent generates a full commit message with Title + Body, adhering strictly to the custom instructions.
What is the expected behavior?
The native "Commit" button in the UI should utilize the same context and logic as the Chat Agent. It should:
- Respect the Commit instructions defined in Settings.
- Generate both a Title and a Body/Description for the commit, rather than just a title.
Additional information
My custom instruction is set to:Conventional Commits 1.0.0 Summary... The commit message should be structured as follows: <type>[optional scope]: <description> [optional body]...
13 Comments
Encountered the same issue; hoping for a prompt fix
same issue here, seems like it wasn't loaded at all
@etraut-openai Hi, would it be possible to address this in the next release? It looks like many users are encountering the same issue. It would be great if AI-generated commit messages could follow the Conventional Commits specification, so they pass commitlint validation.
https://github.com/conventional-changelog/commitlint/#what-is-commitlint
The Codex macOS app Commit button keeps generating commit messages in Ukrainian. My repository requires commit messages to be English ASCII only, so the commit fails every time. The Codex UI language is already set to English (United States), but it still ignores this setting. It seems the Commit button may be using the conversation language instead of the configured UI language.
<img width="549" height="370" alt="Image" src="https://github.com/user-attachments/assets/49f37ffc-085b-40b7-ac64-f37726b5f075" />
Encountered the same issue; hoping for a prompt fix
seems like it's working now. (I've not updated the app. It started working suddenly)
It's still not working :(
26.309.31024 (962)
Still not woking
26.311.21342 (993)
The commit instructions are working for me in Version 26.422.30944 (2080)
In the desktop app: Go to
Codex > Settings > Git > Commit instructionsAdd
use conventional commitand save.I need to wait a day for my limit to run out to verify this.
You tested this with the 'commit' button on top?
<img width="442" height="144" alt="Image" src="https://github.com/user-attachments/assets/fea4772d-9064-4df5-9068-eaae3feed715" />
Yep. I am also using lefthook with commitlint, not that it makes a difference.
Does not yet work in Codex App on Mac, version: 26.513.31313 (2867)
I added the same git message instructions i use at several tools where it works nicely. Here Codex ignores it and generates no commit description. This is very annoying, because it breaks the workflow. Now, I commit with codex, generate the message elsewhere and Rebase with "Reword the message" - that can not be the intention. 😬
macOS 26.5.1 (25F80)
Codex 26.609.71450
Still not work