Issue Station
Sign In
Tools hereToolbox

codex - ✅(Solved) Fix /status shows Agents.md: <none> even when AGENTS.md exists and appears to be loaded [1 pull requests, 4 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17498•Fetched 2026-04-12 13:27:36
View on GitHub
Comments
4
Participants
2
Timeline
14
Reactions
3
Author
yuebozhangyuebozhang
Participants
ImHangLiImHangLiyuebozhangyuebozhang
Timeline (top)
commented ×4labeled ×4cross-referenced ×2unlabeled ×2

/status shows Agents.md: <none> even when AGENTS.md exists and appears to be loaded.

Root Cause

/status shows Agents.md: <none> even when AGENTS.md exists and appears to be loaded.

Fix Action

Fixed

PR fix notes

PR #17506: Expose instruction sources (AGENTS.md) via app server

Description (problem / solution / changelog)

Addresses #17498

Problem: The TUI derived /status instruction source paths from the local client environment, which could show stale <none> output or incorrect paths when connected to a remote app server.

Solution: Add an app-server v2 instructionSources snapshot to thread start/resume/fork responses, default it to an empty list when older servers omit it, and render TUI /status from that server-provided session data.

Additional context: The app-server field is intentionally named instructionSources rather than AGENTS.md-specific terminology because the loaded instruction sources can include global instructions, project AGENTS.md files, AGENTS.override.md, user-defined instruction files, and future dynamic sources.

Changed files

  • codex-rs/analytics/src/analytics_client_tests.rs (modified, +2/-0)
  • codex-rs/app-server-protocol/schema/json/codex_app_server_protocol.schemas.json (modified, +24/-0)
  • codex-rs/app-server-protocol/schema/json/codex_app_server_protocol.v2.schemas.json (modified, +24/-0)
  • codex-rs/app-server-protocol/schema/json/v2/ThreadForkResponse.json (modified, +8/-0)
  • codex-rs/app-server-protocol/schema/json/v2/ThreadResumeResponse.json (modified, +8/-0)
  • codex-rs/app-server-protocol/schema/json/v2/ThreadStartResponse.json (modified, +8/-0)
  • codex-rs/app-server-protocol/schema/typescript/v2/ThreadForkResponse.ts (modified, +5/-1)
  • codex-rs/app-server-protocol/schema/typescript/v2/ThreadResumeResponse.ts (modified, +5/-1)
  • codex-rs/app-server-protocol/schema/typescript/v2/ThreadStartResponse.ts (modified, +5/-1)
  • codex-rs/app-server-protocol/src/protocol/common.rs (modified, +2/-0)
  • codex-rs/app-server-protocol/src/protocol/v2.rs (modified, +53/-0)
  • codex-rs/app-server/src/codex_message_processor.rs (modified, +33/-0)
  • codex-rs/app-server/src/thread_state.rs (modified, +1/-0)
  • codex-rs/app-server/tests/suite/v2/thread_start.rs (modified, +59/-0)
  • codex-rs/exec/src/lib_tests.rs (modified, +1/-0)
  • codex-rs/tui/src/app.rs (modified, +3/-0)
  • codex-rs/tui/src/app_server_session.rs (modified, +13/-0)
  • codex-rs/tui/src/chatwidget.rs (modified, +7/-15)
  • codex-rs/tui/src/chatwidget/tests/helpers.rs (modified, +1/-0)
  • codex-rs/tui/src/chatwidget/tests/status_command_tests.rs (modified, +23/-0)
  • codex-rs/tui/src/status/card.rs (modified, +2/-15)
  • codex-rs/tui/src/status/helpers.rs (modified, +14/-35)
  • codex-rs/tui/src/status/mod.rs (modified, +1/-1)

Code Example

Agents.md: <none>
RAW_BUFFERClick to expand / collapse

Summary

/status shows Agents.md: <none> even when AGENTS.md exists and appears to be loaded.

Environment

  • Codex CLI v0.120.0
  • macOS Darwin 25.4.0 arm64
  • Model: gpt-5.4
  • Collaboration mode: Default

Description

In my session, /status consistently showed:

Agents.md: <none>

However:

  • The current working directory was a project root containing a root-level AGENTS.md
  • I also added another AGENTS.md at the workspace root to rule out a workspace-root mismatch
  • The assistant still appeared to read and follow the project AGENTS.md

This makes it look like the issue is in the status display logic, or in a mismatch between status path resolution and actual AGENTS loading behavior.

Steps to Reproduce

  1. Open Codex CLI in a project directory that contains a root-level AGENTS.md
  2. Confirm the file exists and is readable
  3. Run /status
  4. Observe that Agents.md is shown as <none>

Observed Behavior

  • /status shows Agents.md: <none>
  • AGENTS.md exists at the active project root
  • Another AGENTS.md also exists at the workspace root
  • The assistant still appears to follow the project instructions

Expected Behavior

  • If AGENTS.md is found and loaded for the active project or workspace, /status should show that file instead of <none>
  • If /status is intentionally checking a different directory than the session cwd, it should clearly indicate which directory it checked

Why This Is Confusing

It is hard to tell whether:

  • AGENTS.md was not discovered
  • AGENTS.md was discovered but not displayed
  • the status panel is stale
  • the status panel is using different path resolution logic than the actual instruction loader

Privacy / Redaction

This report is redacted and does not include:

  • private note contents
  • tokens or credentials
  • identifiable local paths
  • repository names unrelated to reproducing the bug

extent analysis

TL;DR

The issue may be resolved by ensuring consistent file name casing in the project directory and the /status command, as the project contains an AGENTS.md file but the command displays Agents.md: <none>.

Guidance

  • Verify that the AGENTS.md file is correctly loaded by the assistant by checking if the instructions in the file are being followed.
  • Check the documentation of the Codex CLI v0.120.0 to see if there are any known issues with file name casing or path resolution.
  • Try renaming the AGENTS.md file to agents.md to see if the /status command displays the file correctly.
  • Investigate if there are any configuration options in the Codex CLI to specify the directory or file name casing for the AGENTS.md file.

Notes

The issue may be specific to the Codex CLI version v0.120.0 or the macOS environment, and further investigation may be needed to determine the root cause.

Recommendation

Apply workaround: Try renaming the AGENTS.md file to agents.md to see if the /status command displays the file correctly, as this may resolve the issue with inconsistent file name casing.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING