codex - 💡(How to fix) Fix Codex can not see currently open file in VSCode anymore [1 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#18163Fetched 2026-04-17 08:31:54
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

What version of the IDE extension are you using?

26.415.20818

What subscription do you have?

Pro

Which IDE are you using?

VS Code

What platform is your computer?

Windows + WSL

What issue are you seeing?

Codex is not able to read the currently open file anymore. This worked yesterday still. It now has to guess which file, do workspace search by keyword etc instead of being able to refer to the currently open file as it could before.

I gotta say im getting majorly pissed off with these constant regressions and clunky changes.

What steps can reproduce the bug?

STart a chat with a file open and see it wont know which file you are talking about when you reference the open file.

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The issue may be resolved by checking for updates to the IDE extension or resetting its configuration to ensure it can access the currently open file.

Guidance

  • Verify that the issue persists after restarting VS Code to ensure it's not a transient problem.
  • Check the extension's settings to see if there are any configuration options related to file access or context awareness that may have been changed or reset.
  • Try disabling and re-enabling the Codex extension to see if it resolves the issue.
  • If the problem started recently, consider checking the extension's changelog or release notes for any updates that may have introduced this regression.

Notes

The exact cause of the issue is unclear, and without more information about the extension's configuration or recent updates, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Try resetting the extension's configuration or disabling and re-enabling it to see if it resolves the issue, as this may be a temporary fix until an update is released to address the regression.

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