🔧Claude Code Using the Wrong Model? Check Your PATH

##Problem

Claude Code started producing significantly worse results—regressions on every fix, confusion about basic date logic, requiring constant babysitting. It felt like the tool had regressed months. Running /status showed it was using Claude Sonnet 4 with a date from May, and /model listed Opus 4.1 as an option—both long outdated.

I'd been updating Claude Code regularly, so this didn't make sense.

##Solution

An old version of Claude Code had installed itself in an NVM bin path that had higher priority in my $PATH. Every time I ran claude, I was launching the outdated version instead of the current one.

To fix it:

1. Find all Claude Code executables on your system:

bash
Copy
which -a claude

1. Remove every instance you find—NVM paths, temp folders, old bin directories, everywhere.

2. Reinstall using the latest recommended method.

3. Verify the version:

bash
Copy
claude --version

1. Confirm the models are current with /status and /model inside Claude Code.

After reinstalling, problems that had taken days of frustrating back-and-forth were resolved in minutes. The difference between the old and current models was not subtle.

##Takeaway

If Claude Code (or any AI tool) suddenly starts performing significantly worse, check that you're actually running the version you think you're running. Check your PATH. Check for duplicate installations.