CLI activity log shows only basenames for Explored/Read entries

Open 💬 1 comment Opened Apr 18, 2026 by joshka

What version of Codex CLI is running?

codex-cli 0.121.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.4

What platform is your computer?

Darwin 24.6.0 arm64 arm

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

Ghostty

What issue are you seeing?

In the CLI activity log, Explored / Read entries often show only the basename of a file instead of a repo-relative path.

This loses important context in repositories with repeated filenames such as README.md, mod.rs, index.ts, or Cargo.toml. The path is often necessary to understand what the agent is actually inspecting.

What steps can reproduce the bug?

  1. Open a repository with repeated filenames, such as multiple README.md or multiple mod.rs.
  2. Start Codex CLI.
  3. Ask Codex to inspect or explore the codebase.
  4. Watch the Explored / Read activity log.
  5. Observe that entries often show only the basename instead of a repo-relative path.

What is the expected behavior?

Explored / Read activity should show enough path context to disambiguate files, ideally repo-relative paths.

Additional information

This is especially noticeable in Rust workspaces and monorepos, where many files share the same name.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗