Error on first run on Windows

same error message on first run

Error: spawn /bin/bash ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:286:19)
at onErrorNT (node:internal/child_process:484:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -4058,
code: 'ENOENT',
syscall: 'spawn /bin/bash',
path: '/bin/bash',
spawnargs: [ '-l' ]
}
╭────────────────────────────────────────────╮
│ ✻ Welcome to Claude Code research preview! │
╰────────────────────────────────────────────╯

Let's get started.

Choose the text style that looks best with your terminal:
To change this later, run /config

❯ Light text
Dark text
Light text (colorblind-friendly)
Dark text (colorblind-friendly)

Preview
╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ 1 function greet() { │
│ 2 console.log("Hello, World!"); │
│ 2 console.log("Hello, Claude!"); │
│ 3 } │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

What OS and Shell are ya'll using?
Is there a /bin/bash?

nvm I am stupid and apparently can't read, I'm assuming OP made the same mistake as me.

Operating Systems: macOS 10.15+, Ubuntu 20.04+/Debian 10+, or Windows via WSL

I'm on windows 11 and am getting this error using nvm/command prompt

Sorry, we don't support Windows. Are you able to use WSL? https://learn.microsoft.com/en-us/windows/wsl/install

Yes, WSL works. Can you update the readme.md "Get Started" steps?

WSL is not working for me. I have ubuntu WSL setup and running npx claude gives the same errors and the text display and no chance to select and then exits.

You all said it works in WSL.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.