Not found file in codex app

Resolved 💬 3 comments Opened Feb 11, 2026 by kaojinz Closed Feb 11, 2026
💡 Likely answer: A maintainer (gpeal, contributor) responded on this thread — see the highlighted reply below.

Not found file in codex app

show 'No results' any project

<img width="976" height="712" alt="Image" src="https://github.com/user-attachments/assets/4a410f0d-c6df-4e3b-b9c4-9380cd3eef9f" />

View original on GitHub ↗

3 Comments

gpeal contributor · 6 months ago

Does it work in the CLI or VS Code extension when opened to the same folder?

kaojinz · 6 months ago

Both CLI and VSCode extension not working.
Even after reinstalling everything, it's the same situation.

<img width="1227" height="756" alt="Image" src="https://github.com/user-attachments/assets/3c24d7d7-6e4a-44ac-9be4-5a0d3a388793" />

/status

╭─────────────────────────────────────────────────────────────────────────────────╮
│  >_ OpenAI Codex (v0.98.0)                                                      │
│                                                                                 │
│ Visit https://chatgpt.com/codex/settings/usage for up-to-date                   │
│ information on rate limits and credits                                          │
│                                                                                 │
│  Model:                gpt-5.3-codex (reasoning xhigh, summaries auto)          │
│  Directory:            ~/githubs/test-codex                                     │
│  Approval:             on-request                                               │
│  Sandbox:              workspace-write                                          │
│  Agents.md:            AGENTS.md                                                │
│  Account:              myname1@email.com (Plus)                                 │
│  Collaboration mode:   Default                                                  │
│  Session:              019c4bd1-3376-...
kaojinz · 6 months ago

https://github.com/openai/codex/issues/8616
I resolved the issue by referring to this issue.

It was due to ~/.gitignore .