-
Notifications
You must be signed in to change notification settings - Fork 11.2k
/status no longer reports AGENTS.md in 0.120.0 #17776
Copy link
Copy link
Closed
Labels
TUIIssues related to the terminal user interface: text input, menus and dialogs, and terminal displayIssues related to the terminal user interface: text input, menus and dialogs, and terminal displaybugSomething isn't workingSomething isn't workingconfigIssues involving config.toml, config keys, config merging, or config updatesIssues involving config.toml, config keys, config merging, or config updatesregressionBehaviors that worked in previous versions but were broken due to an updateBehaviors that worked in previous versions but were broken due to an update
Metadata
Metadata
Assignees
Labels
TUIIssues related to the terminal user interface: text input, menus and dialogs, and terminal displayIssues related to the terminal user interface: text input, menus and dialogs, and terminal displaybugSomething isn't workingSomething isn't workingconfigIssues involving config.toml, config keys, config merging, or config updatesIssues involving config.toml, config keys, config merging, or config updatesregressionBehaviors that worked in previous versions but were broken due to an updateBehaviors that worked in previous versions but were broken due to an update
Type
Fields
Give feedbackNo fields configured for issues without a type.
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,/statusshows:However, fresh sessions still apply the AGENTS rules correctly.
Backend-scoped task evidence:
Frontend-scoped task evidence:
This shows the AGENTS instructions are loaded, scoped, and used, even though
/statussays otherwise.What steps can reproduce the bug?
AGENTS.md.AGENTS.mdfiles for scoped subdirectories such as backend and frontend areas.0.120.0./status.What is the expected behavior?
/statusshould report the applicableAGENTS.mdfile(s), not<none>.At minimum, it should show the nearest governing
AGENTS.mdfor the current working directory. If multiple AGENTS files are in scope, the status output should reflect that consistently.Additional information
0.118.0works correctly.Using an isolated home/config environment,
/statusin0.118.0correctly showed a relative path to the governingAGENTS.mdin the parent repository hierarchy instead of<none>.Example:
0.120.0appears broken only in/status.0.120.0,debug prompt-inputstill injects AGENTS instructions at session startup./statusdisplay / discovery regression rather than a real AGENTS loading failure.