No response on Windows 11 powershell

[Kurren123]

Environment: Windows 11 powershell
Python version: 3.10.1

My powershell administrator session:

PS C:\dev\Codex-CLI> .\scripts\powershell_setup.ps1 -OpenAIOrganizationId '*****' -OpenAIEngineId 'code-davinci-002'

cmdlet powershell_setup.ps1 at command pipeline position 1
Supply values for the following parameters:
OpenAIApiKey: ***************************************************
Checking OpenAI access...
Removed previous setup script from C:\Users\Kurren\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1.
Added plugin setup to C:\Users\Kurren\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1.
Updated OpenAI configuration file with secrets.
Codex CLI PowerShell (v5) setup completed. Please open a new PowerShell session, type in # followed by your natural language command and hit Ctrl+G!

I open a new powershell and do # what is my pc name? hit Ctrl + G, no response.

Any help would be much appreciated

[john-yzaguirre]

same issue bump

[Loky13]

Same issue here

[windwang]

Same issue here
+1

[scsa20]

Same issue
+1

[camillanapoles]

another one

[KDLGates]

Obviously I can't 'guarantee' no user error, but followed the installation carefully twice and got the success confirmation both times. New PowerShell terminal, put in my # Natural Language Prompt, pressed Ctrl+G, no response.

Despite the topic title I am on the Windows 10 PowerShell (v 7.3.1), not Windows 11.

[jtschuster]

Ran into this issue until I realized I hadn't installed the pip dependencies. If you haven't yet, make sure python is installed and run python -m pip install -r requirements.txt at the root of the repo. That fixed it for me.

[KDLGates]

THANK YOU! 🙂 This was the issue for me, I too was missing the dependencies such as the OpenAI package. Learned to watch for a requirements.txt in cloned projects for a PIP run. and if this was in the installation instructions I missed them. Suspect that might be the case for others here.

[Kurren123]

@jtschuster This did the trick! It wasn't in the installation instructions unfortunately.