Title: Persistent Update Notification Blocking Claude 4 Access This issue title captures the core problem of: - Continuous update notifications - Inability to access Claude 4 despite paying for service - Potential update system malfunction The title is t
Bug Description
fy.toml)…
⎿ Read 151 lines (ctrl+r to expand)
● Read(README.md)…
⎿ Error: File does not exist.
⎿ Interrupted by user
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ > Try "edit api.ts to..." │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
? for shortcuts ✓ Update installed · Restart to apply
it always tells me to restart and i have restartd the pc and used the /doctor instructions to cd into the local ~/.claude install directory and run the commands to update and it says there are no new packages updated so why does it keep saying it is autoupdating? i stil HAVE NOT GOTTEN THE NEW CLAUDE 4 AND I AM PAYING $200 A MONTH FOR THIS!
Environment Info
- Platform: linux
- Terminal: vte-based
- Version: 0.2.126
- Feedback ID: d4db72df-7ded-460e-8af4-0a2097e54236
Errors
[{"error":"Error: spawn ENOTDIR\n at ChildProcess.spawn (node:internal/child_process:420:11)\n at spawn (node:child_process:753:9)\n at execFile (node:child_process:346:17)\n at file:///home/jman/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:644:3137\n at new Promise (<anonymous>)\n at PX (file:///home/jman/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:644:3115)\n at p0 (file:///home/jman/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:644:3041)\n at $v (file:///home/jman/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:644:4240)\n at Object.<anonymous> (file:///home/jman/.claude/local/node_modules/@anthropic-ai/claude-code/cli.js:644:4455)\n a
Note: Error logs were truncated.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗