Repository navigation
Error: spawn /bin/bash ENDENT failure #48
Description
This is all the further I get. Instantly exits.
npm --versions:
{
npm: '11.1.0',
node: '22.14.0',
acorn: '8.14.0',
ada: '2.9.2',
amaro: '0.3.0',
ares: '1.34.4',
brotli: '1.1.0',
cjs_module_lexer: '1.4.1',
cldr: '46.0',
icu: '76.1',
llhttp: '9.2.1',
modules: '127',
napi: '10',
nbytes: '0.1.1',
ncrypto: '0.0.1',
nghttp2: '1.64.0',
nghttp3: '1.6.0',
ngtcp2: '1.10.0',
openssl: '3.0.15+quic',
simdjson: '3.10.1',
simdutf: '6.0.3',
sqlite: '3.47.2',
tz: '2024b',
undici: '6.21.1',
unicode: '16.0',
uv: '1.49.2',
uvwasi: '0.0.21',
v8: '12.4.254.21-node.22',
zlib: '1.3.0.1-motley-82a5fec'
}
Activity
lyramakesmusic commentedon Feb 25, 2025
also getting this, also on windows. Docs say compatible with bash shell and zsh, no cmd mentioned. Seems windows users incl. me are locked out of using it
Wolfieeewolf commentedon Feb 25, 2025
Had the same issue. Install Git for Windows and use the Git Bash and it works just fine
AlexanderMorou commentedon Feb 25, 2025
That helps.
Install git.
Add git's folder to your PATH variable.
Type git-bash
If you're not familiar with bash's command structure, navigate to the folder you want to use (like in their original instructions) before launching git-bash.
Inside git-bash's launched terminal type claude.
The opening screen doesn't say to press a key/enter to continue, thought it legit froze.
The git-bash aspect for windows should probably be somewhere in their getting started guide.
jmc0228 commentedon Feb 25, 2025
I had the same issue, except that I had git bash installed a long time ago and running claude didn't do anything. Turned out I needed to update. I just installed the latest git for windows and the problem was solved.
ia-torlaschi commentedon Feb 25, 2025
Definitely when starting it from git-bash it starts but now the problem is::
" Claude Code is at capacity
Claude Code is currently experiencing high demand. Anthropic has paused sign ups to provide the best possible service to customers. We'll notify you when we have a spot for you! "
github-actions commentedon Aug 9, 2025
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.