Codecompanion-nvim and blink-cmp

[lifeismeta]

Hiya! Could it be that codecompanion-vim in NVF is hardcoded to use nvim-cmp?

CC ( Codecompanion ) support both nvim-cmp and blink-cmp, but when I enable the latter then CC won't install.

Looking at the CC here on NVF, it seems like nvim-cmp is a dependency? I'm not sure how it plays out, and if that's the reason CC won't install with nvim-cmp.enable = false locally? If, would it be possible to make it it optional? I can try do it myself, just need to learn how first!x)

Thanks in advance!

[gmvar]

I also ran into this issue and can confirm that having both CodeCompanion (CC) and blink-cmp enabled at the same time in nvf stops CC from starting up. The config printed by nvf-print-config looked fine, but I did spot a ["lazy"] = true in there.

Turning off lazy loading did the trick, so as a quick fix, you can set vim.lazy.enable = false; in your config. I’m not really sure why it behaves this way, but it seems like there’s a conflict between the two plugins that stops CC from starting when both are active.