codex - 💡(How to fix) Fix Regression: Codex app “For coding” view now hides edited file names and commands behind aggregate summaries [2 comments, 3 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#19891Fetched 2026-04-28 06:35:28
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
4
Timeline (top)
commented ×2labeled ×2cross-referenced ×1

Root Cause

For coding workflows, the minimum useful information is not just “N files edited”; it is which files were edited.

Commands run are also important and should be visible by default because:

  1. Commands can modify repository or system state, even when no file edit is shown directly.
  2. Commands are a key signal of how the agent validated its work, for example by running tests, linters, formatters, type checks, build commands, or ad hoc inspection commands.

Hiding edited files and commands behind extra clicks creates review friction and makes the agent less inspectable. In a coding agent UI, these are not secondary details; they are core audit information.

This is not asking for all command output, diffs, explored files, or search results to be expanded. The request is only that the thread show the edited file paths and command invocations by default.

RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.422.30944 (2080)

What subscription do you have?

Business

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

In the current Codex app UI, using the “For coding” view, the agent’s action log is now collapsed into aggregate summaries such as:

Edited 3 files, explored 2 files, 2 searches

Ran 2 commands

This appears to be a recent regression. Previously, Codex showed the files that were edited by default. Now even the names of edited files are hidden unless I click into the summary.

This makes it harder to supervise the agent live, audit what it changed, and quickly decide whether intervention is needed.

I am not asking for every explored file or every search to be expanded by default. Those can reasonably remain summarized. The main regression is that the UI now hides information that is essential for coding review: which files were edited and which commands were run.

Why this matters

For coding workflows, the minimum useful information is not just “N files edited”; it is which files were edited.

Commands run are also important and should be visible by default because:

  1. Commands can modify repository or system state, even when no file edit is shown directly.
  2. Commands are a key signal of how the agent validated its work, for example by running tests, linters, formatters, type checks, build commands, or ad hoc inspection commands.

Hiding edited files and commands behind extra clicks creates review friction and makes the agent less inspectable. In a coding agent UI, these are not secondary details; they are core audit information.

This is not asking for all command output, diffs, explored files, or search results to be expanded. The request is only that the thread show the edited file paths and command invocations by default.

Expected behavior

In “For coding” mode, Codex should continue to show edited file names and command invocations directly in the thread by default, as it previously did, e.g.:

  • Edited src/foo.ts
  • Edited src/bar.test.ts
  • Ran npm test
  • Ran npm run lint

The aggregate summary can still exist, but it should not hide the edited-file list or the commands run in coding-focused mode.

Actual behavior

The thread now shows only an aggregate summary such as:

Edited 3 files, explored 2 files, 2 searches

To see the actual edited files or commands, I have to click into the summary.

Non-goals

I am not requesting that Codex expand every explored file, every search, full command output, or full diff by default.

Those can remain collapsed or summarized. The specific request is that edited file paths and command invocations remain visible without extra clicks in “For coding” mode.

Related but not exact duplicates

  • #16415 asks for an always-expand-all inspection mode, but this issue is narrower: edited file names and command invocations should be visible by default, even without expanding everything.
  • #19260 is about command/tool output folding. This issue is not primarily about expanding command output; it is about showing the command invocations themselves.
  • #18478 is related to review UX around diff visibility, but not specifically this action-log regression.

What steps can reproduce the bug?

This happens in any Codex session in which the agent modifies code or runs commands.

extent analysis

TL;DR

The Codex App should be modified to display edited file names and command invocations by default in "For coding" mode, without requiring extra clicks.

Guidance

  • Review the current UI implementation for the "For coding" view to identify the change that caused the regression.
  • Update the UI to prioritize displaying edited file paths and command invocations, while keeping other information summarized.
  • Consider adding a configuration option to allow users to customize the level of detail shown in the action log.
  • Verify that the updated UI meets the expected behavior described in the issue, with edited file names and command invocations visible by default.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The issue is specific to the "For coding" mode and does not affect other modes. The requested change is to display edited file names and command invocations by default, without expanding all other information.

Recommendation

Apply a workaround by modifying the UI to display edited file names and command invocations by default in "For coding" mode, as this is a regression that affects the usability of the Codex App for coding workflows.

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…

FAQ

Expected behavior

In “For coding” mode, Codex should continue to show edited file names and command invocations directly in the thread by default, as it previously did, e.g.:

  • Edited src/foo.ts
  • Edited src/bar.test.ts
  • Ran npm test
  • Ran npm run lint

The aggregate summary can still exist, but it should not hide the edited-file list or the commands run in coding-focused mode.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING