codex - 💡(How to fix) Fix Bug Report: Changed files panel does not show generated `.html` file inside a new untracked directory

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…

Codex generated a new .html file in a new worktree and the file exists on disk. The file can also be opened successfully in the in-app browser via a file:// URL. However, the Codex app’s edited/changed files display does not show the generated .html file.

This looks like a changed-files UI visibility issue, possibly related to new untracked directories or .html file filtering.

Root Cause

Codex generated a new .html file in a new worktree and the file exists on disk. The file can also be opened successfully in the in-app browser via a file:// URL. However, the Codex app’s edited/changed files display does not show the generated .html file.

This looks like a changed-files UI visibility issue, possibly related to new untracked directories or .html file filtering.

Code Example

# Bug Report: Changed files panel does not show generated `.html` file inside a new untracked directory

## Summary

Codex generated a new `.html` file in a new worktree and the file exists on disk. The file can also be opened successfully in the in-app browser via a `file://` URL. However, the Codex app’s edited/changed files display does not show the generated `.html` file.

This looks like a changed-files UI visibility issue, possibly related to new untracked directories or `.html` file filtering.

## Environment

Worktree path:

`/Users/user/code/Agent/chatgpt/work-content`

Branch:

`codex/content`

Current in-app browser URL:

`file:///Users/user/code/Agent/chatgpt/work-content/works/work/content.html`

## Files Generated

Codex generated these files under a new directory:

---

The HTML file exists on disk:

---

Git status shows the parent directory as untracked:

---

## Reproduction Steps

1. Create or switch to a new git worktree.
2. Ask Codex to generate documentation files under a new task directory.
3. Include an `.html` file among the generated files.
4. Open the generated `.html` file in the Codex in-app browser using a `file://` URL.
5. Check the app’s edited/changed files display.

## Expected Behavior

The changed files UI should list all generated files, including:

---

If the parent directory is untracked, the UI should either expand the directory or otherwise show the files inside it.

## Actual Behavior

The generated `.html` file exists on disk and renders in the in-app browser, but it does not appear in the app’s edited/changed files display.

## Impact

This makes it look like Codex did not generate or edit the `.html` file, even though the file exists and is usable. It can confuse users reviewing Codex output, especially when generated artifacts include both Markdown and HTML versions.

## Possible Cause

The changed files panel may not fully enumerate files inside newly created untracked directories, or it may be filtering out `.html` files from the edited-files display.

## Requested Fix

Please make the changed/edited files UI show all newly generated files, including `.html` files inside untracked directories, or clearly indicate that a new directory contains hidden/unexpanded untracked files.

---

works/work/content.html
RAW_BUFFERClick to expand / collapse

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

26.513.20950 (2816)

What subscription do you have?

chatgpt plus

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

# Bug Report: Changed files panel does not show generated `.html` file inside a new untracked directory

## Summary

Codex generated a new `.html` file in a new worktree and the file exists on disk. The file can also be opened successfully in the in-app browser via a `file://` URL. However, the Codex app’s edited/changed files display does not show the generated `.html` file.

This looks like a changed-files UI visibility issue, possibly related to new untracked directories or `.html` file filtering.

## Environment

Worktree path:

`/Users/user/code/Agent/chatgpt/work-content`

Branch:

`codex/content`

Current in-app browser URL:

`file:///Users/user/code/Agent/chatgpt/work-content/works/work/content.html`

## Files Generated

Codex generated these files under a new directory:

```text
works/work/README.md
works/work/content.md
works/work/content.html

The HTML file exists on disk:

-rw-r--r--@ 1 user  wheel  14693 May 15 19:11 works/work/content.html

Git status shows the parent directory as untracked:

## codex/content
?? works/work/

Reproduction Steps

  1. Create or switch to a new git worktree.
  2. Ask Codex to generate documentation files under a new task directory.
  3. Include an .html file among the generated files.
  4. Open the generated .html file in the Codex in-app browser using a file:// URL.
  5. Check the app’s edited/changed files display.

Expected Behavior

The changed files UI should list all generated files, including:

works/work/content.html

If the parent directory is untracked, the UI should either expand the directory or otherwise show the files inside it.

Actual Behavior

The generated .html file exists on disk and renders in the in-app browser, but it does not appear in the app’s edited/changed files display.

Impact

This makes it look like Codex did not generate or edit the .html file, even though the file exists and is usable. It can confuse users reviewing Codex output, especially when generated artifacts include both Markdown and HTML versions.

Possible Cause

The changed files panel may not fully enumerate files inside newly created untracked directories, or it may be filtering out .html files from the edited-files display.

Requested Fix

Please make the changed/edited files UI show all newly generated files, including .html files inside untracked directories, or clearly indicate that a new directory contains hidden/unexpanded untracked files.


### What steps can reproduce the bug?

1. Create or switch to a new git worktree.
2. Ask Codex to generate documentation files under a new task directory.
3. Include an `.html` file among the generated files.
4. Open the generated `.html` file in the Codex in-app browser using a `file://` URL.
5. Check the app’s edited/changed files display.

### What is the expected behavior?


The changed files UI should list all generated files, including:

```text
works/work/content.html

If the parent directory is untracked, the UI should either expand the directory or otherwise show the files inside it.

Actual Behavior

The generated .html file exists on disk and renders in the in-app browser, but it does not appear in the app’s edited/changed files display.

Additional information

feedback id 019e2b2e-670a-7ca0-935e-2f1e66fc8f89

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Bug Report: Changed files panel does not show generated `.html` file inside a new untracked directory