/status doesn't mention global AGENTS.md

Resolved 💬 23 comments Opened Sep 17, 2025 by nicholaswmin Closed Apr 8, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

Steps

  • launch codex CLI with global ~/.codex/AGENTS.md/$CODEX_HOME/AGENTS.md present
  • run /status

Expected

  • global AGENTS.md listed in AGENTS files row

Actual

  • reports AGENTS files: (none)

View original on GitHub ↗

23 Comments

alexprotonotarios · 10 months ago

it works fine in mine.

nicholaswmin · 10 months ago

@alexprotonotarios what's "mine"? version? OS?

alexprotonotarios · 10 months ago
@alexprotonotarios what's "mine"? version? OS?

macOS
version 0.36

nicholaswmin · 10 months ago

That's really weird bearing in mind the code doesn't exist yet.

The status line’s AGENTS list just iterates the results of discover_project_doc_paths(...), which only walks the repo tree.

This is about showing up in the /status report for a global AGENTS.md,
not any AGENTS.md.

wbdb · 10 months ago

I have the same behavior (Windows 11 Pro / Ubuntu 24.04 WSL2). I had already considered whether it would make sense to change this. But I think that's how it's supposed to be?

nicholaswmin · 10 months ago

No it doesn't make any sense not to print an AGENTS.md that is picked up and composed as context.
Maybe if it was entirely replaced by closer memory files, sure; but that's not the case (the AGENTS.md isn't a protocol but the convention is clear about the closer-one-wins mechanics; its only if there is a conflict, otherwise they compose)

FYI,

  • it's used as context if it exists at $CODEX_HOME/AGENTS.md
  • it consumes context and the UI reflects this
  • It is just not mentioned in /status - only.

to me this looks like a crystal clear oversight, nothing more.

The patch I submitted just ensures that /status mentions it as well;
it's ready if you wanna give it a spin in: https://github.com/openai/codex/pull/3796

wbdb · 10 months ago

I came up with the idea because the top item was called Workspace. But yes, it is taken into account, which I then tested, and I also think it should be displayed.

hi-fox · 10 months ago

A global agents.md file has been added now? How do I use this? I have had an AGENTS.md file in my .codex folder on windows for a while, how do i make sure this is loaded?

wbdb · 10 months ago

~/.codex/AGENTS.md
_“Reply to me with a short joke before every message.”_

It's loading :D

More precisely: Config::load_from_base_config_with_overrides calls Config::load_instructions, which reads codex_home/AGENTS.md (by default ~/.codex/AGENTS.md) and stores the content in config.user_instructions (codex-rs/core/src/config.rs:858 and codex-rs/core/src/config.rs:1060).

bos · 10 months ago

The $HOME/.codex/AGENTS.md file _is_ read, but /status doesn't actually tell the user, which makes a situation ripe for confusion as comments above indicate. I had to actually read the codex code today to convince myself that its content probably is being used.

nicholaswmin · 9 months ago

Well I've issued a PR: https://github.com/openai/codex/pull/3796 but it's in desperate need of a test drive.

also yes @bos is correct, the file is read.

PaulRBerg · 9 months ago

I tried Codex for the first time today, wrote my ~/.codex/AGENTS.md file, ran /status expecting AGENTS.md to be mentioned there, spent 10 mins looking through this repo's issues channel, found a bunch of related issues (that turned out to be misleading after all), proceed to ask Codex why it hasn't loaded AGENTS.md, and it says this:

<img width="1000" src="https://github.com/user-attachments/assets/d144d69f-2ac3-459a-9cc3-43539d609a80" />

---

Ironically, it is in this moment that I realize that Codex has actually read my AGENTS.md file. My prompt contain this no-BS rule:

````markdown
USE BRUTAL HONESTY: Don't try to be polite or agreeable. Be direct, challenge assumptions, and point out flaws

````

But yeah, this was extremely confusing and the /status command should mention ~/.codex/AGENTS.md file.

nicholaswmin · 9 months ago

@seratch this isn't a question; it's a bug

calinfaja · 6 months ago

As of today, I am experiencing this bug also:

Global AGENTS.md and AGENTS.override.md not loading in Codex CLI v0.79.0 (Business account)

Environment

  • Codex CLI: codex-cli 0.79.0
  • OS: Ubuntu 24.04.3 LTS (Linux 6.14.0-37-generic)
  • Shell: bash
  • Account: Codex Business (Team/Unknown shown in /status)

Files present

  • ~/.codex/AGENTS.md exists, 90 lines
  • ~/.codex/AGENTS.override.md exists, 90 lines

Permissions: -rw-rw-r--
(So they are readable and non-empty.)

Reproduction steps

  1. Create ~/.codex/AGENTS.md with non-empty content.
  2. Create ~/.codex/AGENTS.override.md (copy of AGENTS.md).
  3. Start Codex outside any repo (e.g., ~/Project).
  4. Run /status.

Expected result
/status should show the global AGENTS file, ideally the override file path (e.g., ~/.codex/AGENTS.override.md).

Actual result
/status shows Agents.md: <none>.

Example /status snippet (redacted)

Model: gpt-5.2-codex
Directory: ~/Project
Approval: on-request
Sandbox: workspace-write
Agents.md: <none>
Account: *****

Additional observations

  • Project-level AGENTS works.
  • So AGENTS loading works for repo-level, but global appears ignored.
blackirishmec · 5 months ago

@etraut-openai Any vis on getting this handled?

etraut-openai contributor · 5 months ago

We generally prioritize feature development based on upvotes.

calinfaja · 5 months ago

@etraut-openai this is an issue 5 months old...

PaulRBerg · 5 months ago
We generally prioritize feature development based on upvotes.

could you please also prioritize by effort + impact? I'm sure Codex 5.2 GPT can come up with an automated system for sorting issues.

This particular issue is super low-effort + but moderate impact, since AGENTS.md is a super important file.

playhuck · 3 months ago

Has anyone resolved this issue on Ubuntu 24? The .codex/AGNETS.md file still exists and is readable, but when I check the status, it shows <none>. I’d like this uncertainty to be cleared up.

etraut-openai contributor · 3 months ago

If you'd like to see this feature, please upvote it. We generally prioritize feature requests based on upvote counts.

calinfaja · 3 months ago

Hello @etraut-openai . This is not a feature, but a bug fix 8 months old. I really don't understand how you can't plan this fix...

etraut-openai contributor · 3 months ago

This will be addressed in the next release.

PaulRBerg · 3 months ago

Thank you @etraut-openai