[BUG] claudecode.nvim does not seem to use the local version of claude code

[jim-at-jibba]

Bug Description

Claude code has the idea of a local installation of their tool. I assume this is to get around the issue of people having multiple versions of node on their machines. This plugin does not seem to find the local installation and will only work work with one globally.

This means that you have to install and maintain multiple versions of Claude Code if you have different versions of node installed.

/doctor will warn you about it and recommends using the local version and removing the global version.

To Reproduce

Steps to reproduce the behavior:

1. /doctor
2. read warnings
3. See error

Expected Behavior

Use local version of package

Environment

• Neovim version: [e.g. 0.11.1]
• Claude Code CLI version: [e.g. 1.0.44]
• OS: [e.g. macOS 15.5]
• Plugin version: latest

Error Messages

Paste any error messages here

Additional Context

Add any other context about the problem here.

[gshpychka]

Do you have the local installation on your PATH?

[jim-at-jibba]

Not local to the project. They refer to local as ~/.claude/local and this seems to be the recommended approach, the is a migrate command that removes the global package and adds an alias, and I wonder if the spawned shell has all the aliases available to it

[gshpychka]

Not local to the project. They refer to local as ~/.claude/local and this seems to be the recommended approach, the is a migrate command that removes the global package and adds an alias, and I wonder if the spawned shell has all the aliases available to it

Huh - why an alias and not add it to PATH?

[jim-at-jibba]

Thats fair enough. Because that is what Claude code does for the user that runs migrate-installer, I would be more than happy to add it to my PATH but that cant be said for all users of Claude Code.

[gshpychka]

I would be more than happy to add it to my PATH but that cant be said for all users of Claude Code.

but it probably can be said for all users of this plugin, though.

Anyway, this may be of interest: #76

[jim-at-jibba]

Yeah maybe. The PR seems like it would solve this issue.

Thanks

[carlosarraes]

Yeah maybe. The PR seems like it would solve this issue.

Thanks

It does. I've created it because i had to use the migrate-installer too.