Reference console claude binary avx2 constraint

---

name: Console VM: claude binary requires ~/.local/bin/claude, not nvm path description: Console CPU is x86-64-v2-AES (no AVX2); npm-bundled claude binary SIGILLs — use ~/.local/bin/claude instead type: reference

---

Console VM (CT 103) CPU is pinned to x86-64-v2-AES, which lacks AVX/AVX2. The @anthropic-ai/claude-code npm package (2.1.123+) ships a Bun-bundled binary that requires AVX2 — every claude -p subprocess crashes with rc=-4 (SIGILL) on Console.

Current workaround (applied 2026-04-30): ~/.nvm/versions/node/v20.20.0/bin/claude symlink re-pointed to ~/.local/bin/claude, which is a different installer path that does not require AVX2. This fixed all 4 Telegram bots and 14 forge scripts immediately.

Fragility: If npm install -g @anthropic-ai/claude-code ever runs again it overwrites the symlink and breaks everything again.

Recommended permanent fixes (not yet done as of 2026-04-30): 1. Change Console VM CPU from x86-64-v2-AES to host in Proxmox (Finn VM 103 conf) — exposes full AVX2, makes npm binary work again. 2. Repoint all 14 forge CLAUDE_BIN constants from ~/.nvm/.../claude to ~/.local/bin/claude directly, bypassing nvm entirely.

Affected scripts: brain, morning report, heartbeat, training reco, wellness summary, evening winddown, dispatcher critic, eval harness, food lookup, fitness retro, habits alias backfill, capture/coordinator brain, remote bridge, auto-memory, auto-dream.

[Claude Code] 2026-04-30

[auto-memory session e5162cae-5d60-4ef4-9892-fa6f91ddafa9, confidence 0.88, mode direct]