Codex App blank commit message autofill ignores configured Git commit message format (creates subject-only commit)[/-]
Resolved 💬 9 comments Opened Feb 7, 2026 by deinspanjer Closed Jul 2, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
Version 260206.1448 (565)
What subscription do you have?
Enterprise
What issue are you seeing?
When I leave the commit message field blank in Codex Desktop and let Codex auto-fill, it produces a one-line subject-only commit message, even though my configured Git instructions require a multi-line conventional commit message with a body.
Feedback reported with id 019c3657-bbcb-7842-8e4c-77fa322356c8
What steps can reproduce the bug?
- Configure Git commit instructions in Codex App settings to require multi-line message format with subject + body.
See attached instructions
- Make code changes.
- Leave commit message field blank and let Codex auto-generate it.
- Create commit.
The actual commit message made by Codex App was:
Update metadata summary rows
What is the expected behavior?
This is what Codex thought it was going to generate as a commit message based on the instructions:
fix: summarize large root metadata values in Jobs table Metadata rows were rendering full JSON payloads for root collection values, which caused unnecessary horizontal overflow in the Metadata table. - Add_summarize_root_metadata_valueto render root arrays as<count> items- Render root objects as<count> attributes- Keep scalar root metadata values rendered directly via existing formatting - Update_job_metadata_rowsto use the summary formatter for metadata extras - Add unit tests for collection summarization and scalar passthrough intest_metadata_rows.py
Additional information
Git Commit instructions specified in the Codex App Settings panel:
<img width="1200" height="800" alt="Image" src="https://github.com/user-attachments/assets/8889a9c7-56c3-4b66-b99b-a42e775fa734" />
9 Comments
@etraut-openai how is this an enhancement and not a bug? How is the original feature supposed to work?
Ah, I misunderstood. I thought you meant that you had configured a git commit template in your project.
Changing back to a bug.
Thank you, I wasn't going to argue because I didn't want to risk having the bug further de-prioritized, but I'm happy to see it was a simple misunderstanding.
I would like to add that it would be nice if the commit message was automatically generated and shown in a greyed out text in the commit message field, as soon as you open the commit modal. That way we could preview it before committing. Pressing tab could fill it out and allow you to edit it afterwards.
Hello, I have the same problem, because I want to have semantic rules setup and commit instructions and they never work. I found one workaround that working for me is that just in the terminal to tell the Agent to commit and create PR, then the instructions are working.
Do you mean that the commit configuration message is wired into the chat context, or simply that you paste the configuration message into chat together with asking to commit?
Yes, I think the commit configuration message is wired into the chat context, I have a prompt in the configurations and in the chat window I just tell Codex to "commit" and the commit messages are semantic as I need them.
<img width="708" height="371" alt="Image" src="https://github.com/user-attachments/assets/41b834e1-bc22-4ade-aed9-a312ad886c9f" />
<img width="766" height="301" alt="Image" src="https://github.com/user-attachments/assets/0071d10a-cb23-4360-b8b7-34079df4313c" />
Yep, I can confirm I found the same workaround. Using the actual Codex App commit or PR options disregard the instructions, but telling Codex to do a commit or a PR in the chat context takes the instructions into account. 🤷
is it too much to use a skill https://skills.sh/github/awesome-copilot/conventional-commit just for commit.