---
title: "Comment by Adam Lewis on \"AGENTS.md Not Working? 8 Fixes for Codex and Other Agents\" | Hashnode"
description: "Case mismatches in fix 3 catch people out, because a repo can carry AGENTS.md and agents.md side by side and the wrong one stays invisible until you ask the age"
url: "https://hashnode.com/posts/agents-md-not-working/6ae8ed6a30b593952bfb84e4/comment/6aea55dee84edb54a17cbc2f"
---

[Discussion](https://hashnode.com/posts/agents-md-not-working/6ae8ed6a30b593952bfb84e4)

Comment [AGENTS.md Not Working? 8 Fixes for Codex and Other Agents](https://hashnode.com/posts/agents-md-not-working/6ae8ed6a30b593952bfb84e4)

[Adam Lewis](https://hashnode.com/@nark3d)

[Nov 3](https://hashnode.com/posts/agents-md-not-working/6ae8ed6a30b593952bfb84e4/comment/6aea55dee84edb54a17cbc2f)

Case mismatches in fix 3 catch people out, because a repo can carry AGENTS.md and agents.md side by side and the wrong one stays invisible until you ask the agent to summarise its instructions. It runs into the same trouble as an override file someone wrote and forgot: the chain loads something and nothing looks broken. I keep the docs and checklists at a set standard before any code so the agent updates them as it goes, and each phase starts from the file. Before you spend another hour on the wording, open the file your editor is showing you and check it's the same one the agent is reading.

[AgentKit Co](https://hashnode.com/@agentkitco)

[Nov 4](https://hashnode.com/posts/agents-md-not-working/6ae8ed6a30b593952bfb84e4/comment/6aea55dee84edb54a17cbc2f#reply-6aeb62c95a839c983304242f)

Thanks Adam, good catch. Having both side by side is a nasty case, especially on case-sensitive filesystems where both really exist. Asking the agent to summarise its instructions is the fastest check. I'll add a line to fix 3 about deleting the stray lowercase copy with `git rm --cached agents.md`.
