Model not respecting agents instructions
What version of the Codex App are you using (From “About Codex” dialog)?
v0.142.0
What subscription do you have?
PLUS and PRO
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
I am aware this is not strictly a harness bug, it is probably a model or base instructions bug, but, as you have no other means to report things, here we go
Since a while, maybe 3 weeks, codex (model 5.5 high non-fast) constantly and apologetically (meaning it KNOWS about it and later says "I am sorry" when challenged) ignores a specific instruction from my project-level AGENST.md file. Below, the instruction with the pre- and after instructions (which both get followed perfectly) included:
## Testing and Validation
Before every commit:
1. Run PHPCS.
2. Run PHPUnit, including the WordPress Unit Test suite.
3. Fix all reported issues.
4. Repeat until the full test and standards suite passes.
Do not commit code that fails checks.
## Git Workflow
- Create atomic git commits for completed work.
- Do not commit unrelated changes.
- If GPG signing blocks a commit, do not create an unsigned commit. Report the error to the operator.
- Do not bypass `.gitignore` with force-adds.
- If a requested file is ignored, keep it local unless the operator explicitly asks to track it.
## Documentation
Keep `/docs` updated with relevant architectural, structural, and developer-facing changes.
- `/docs/README.md` is a compact index for scoped documentation files.
- Use `/docs` to understand the codebase structure and locate relevant files.
- `/docs` is for agents and developers.
- End-user documentation belongs in the main `README.md`.
Always keep the WordPress "Contextual Help Tab" up to date with the current screens.
Note that this does not just happen in this project, it happens in ALL projects, which ALL include the GIT workflow (sometimes even with more aggressive wording) and are sometimes even totally different languages, frameworks etc
When I challenge it it always goes "yes you are right I should have", and _from that point on does_ follow the orders.
This has been working PERFECTLY before a certain point in time after which suddenly it started ignoring the specific GIT workflow commands and simply does not do the commit anymore, not even attempts to.
Yet it happily follows all other commands, and even uses git (diff etc), but not the commit
What steps can reproduce the bug?
.
What is the expected behavior?
The agent respects the agents file commands.
Additional information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗