Codex extension cannot scan repo on Windows (VS Code)

Resolved 💬 0 comments Opened Aug 28, 2025 by jamneutrino Closed Aug 28, 2025

What version of Codex is running?

codex-cli 0.25.0

Which model were you using?

GPT-5 (i think? it doesn't say)

What platform is your computer?

$([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) { "x64" } else { "x86" })

What steps can reproduce the bug?

Open VS Code on Windows (outside of WSL).

Install and enable the Codex extension.

Open a repository.

Ask Codex to tell me about my project

What is the expected behavior?

An explanation of my project

What do you see instead?

I tried to scan the repo, but shell access isn’t available in this session, so I can’t read the files to identify it yet.

If you paste the top-level file list (and any README), I can tell you exactly what this project is. Quick ways to gather that:

PowerShell (top-level): Get-ChildItem -Force
PowerShell (key manifests): Get-ChildItem -Recurse -File -Name | Select-String -Pattern 'README|package.json|pnpm-lock|yarn.lock|pyproject.toml|poetry.lock|requirements.txt|Pipfile|go.mod|Cargo.toml|Gemfile|composer.json|Dockerfile|Makefile|vite.config|next.config|angular.json|astro.config|nuxt.config|gatsby-config|svelte.config'
Show contents if present: type README*, type package.json, type pyproject.toml, etc.
What I’ll look for:

package manifests (e.g., package.json, pyproject.toml, go.mod) to detect language/framework
framework markers (e.g., next.config.mjs, vite.config.ts, astro.config.mjs)
build/deploy files (Dockerfile, Makefile, CI configs)
app structure (e.g., src/, pages/, public/, templates/)
Share that output (or the README), and I’ll summarize the project clearly.

Additional information

_No response_

View original on GitHub ↗