codex - 💡(How to fix) Fix /status no longer reports AGENTS.md in 0.120.0 [1 comments, 2 participants]

What version of Codex CLI is running?

0.120.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.4

What platform is your computer?

Linux 6.6.87.2-microsoft-standard-WSL2 x86_64 x86_64

What terminal emulator and version are you using (if applicable)?

Windows Terminal WSL

What issue are you seeing?

In 0.120.0, /status shows:

Directory:            <workspace>
Permissions:          Custom (workspace-write, never)
Agents.md:            <none>

However, fresh sessions still apply the AGENTS rules correctly.

Backend-scoped task evidence:

Considered rule documents:

- root AGENTS.md
- backend-scoped AGENTS.md
- general repository-level rule documents
- backend-specific rule documents
- frontend-only rule documents marked as not applicable

Frontend-scoped task evidence:

Considered rule documents:

- root AGENTS.md
- frontend-scoped AGENTS.md
- general repository-level rule documents
- frontend-specific rule documents
- UI-specific rule documents when the task is a UI task

This shows the AGENTS instructions are loaded, scoped, and used, even though /status says otherwise.

What steps can reproduce the bug?

1. Prepare a repository with a root AGENTS.md.
2. Add nested AGENTS.md files for scoped subdirectories such as backend and frontend areas.
3. In those files, require Codex to print the considered rule documents at the beginning of its response.
4. Start Codex in the repository with 0.120.0.
5. Run /status.
6. In fresh sessions, run one task in a backend-scoped directory and one task in a frontend-scoped directory.

What is the expected behavior?

/status should report the applicable AGENTS.md file(s), not <none>.

At minimum, it should show the nearest governing AGENTS.md for the current working directory. If multiple AGENTS files are in scope, the status output should reflect that consistently.

Additional information

0.118.0 works correctly.

Using an isolated home/config environment, /status in 0.118.0 correctly showed a relative path to the governing AGENTS.md in the parent repository hierarchy instead of <none>.

Example:

Agents.md:            ../../AGENTS.md

0.120.0 appears broken only in /status.

• In 0.120.0, debug prompt-input still injects AGENTS instructions at session startup.
• Fresh backend/frontend sessions still obey the AGENTS rules and output the required document list.
• This strongly suggests a /status display / discovery regression rather than a real AGENTS loading failure.