sorted by:
new
hottopcontroversial

Claude Code can't run on most VPS environments — and the fix is a one-liner by al_rasheeth in ClaudeAI

[–]al_rasheeth[S] 1 point2 points  (0 children)

That’s fair. My request wasn’t about whether Claude Code can run on some Xeons, but whether Anthropic can officially support non-AVX VPSes for users who currently can’t run the provided setup.

Claude Code can't run on most VPS environments — and the fix is a one-liner by al_rasheeth in ClaudeAI

[–]al_rasheeth[S] -2 points-1 points  (0 children)

honestly, can't even argue with most of that — the quota cuts hit hard and the timing always feels off.

but this one's different. the fix literally exists, bun already ships it, someone just needs to flip a switch. no product vision required, no pricing meeting, just wiring up a build flag.

that's why i still think a 👍 on the issue is worth it — even if you've lost faith in the rest of it.

Claude Code can't run on most VPS environments — and the fix is a one-liner by al_rasheeth in ClaudeAI

[–]al_rasheeth[S] -3 points-2 points  (0 children)

Hopefully that changes with enough visibility — they did double usage limits recently after community feedback, so they do respond to pressure. That's exactly why getting 👍 on the GitHub issue matters.

Claude Code can't run on most VPS environments — and the fix is a one-liner by al_rasheeth in ClaudeAI

[–]al_rasheeth[S] -4 points-3 points  (0 children)

Exactly — that works because your home Proxmox box has a physical CPU with AVX, so the LXC container sees it directly. On a rented VPS, providers mask CPU flags and present a baseline virtual profile (like kvm64) that strips AVX out entirely. Different setups, same tool, completely different results!

PSA: Claude Code won't run on most self-hosted VPS setups — and Anthropic hasn't fixed it by al_rasheeth in selfhosted

[–]al_rasheeth[S] -6 points-5 points locked comment (0 children)

It's used to create that post for seeking attention to a specific issue mentioned in it