Slash commands not responding on <CR> in the chat window

[Bastes]

Hi,

I've just configured codecompanion on my neovim and trying it out ai noticed the slash commands are not working as intended. The auto-complete suggests them alright, but once they're typed and I type Enter, I don't see the appropriate reaction, instead it just types a newline and nothing happens.

To diagnose I removed all the non-codecompanion plugins (including those who had bindings to <CR>) to no avail, the same problem persists.

Here's my current config:

return {
  "olimorris/codecompanion.nvim",
  dependencies = {
    "nvim-lua/plenary.nvim",
    "ravitemer/mcphub.nvim",
  },
  opts = {
    strategies = {
      chat = {
        adapter = "qwen"
      },
      inline = {
        adapter = "qwen"
      },
      cmd = {
        adapter = "qwen"
      },
    },
    adapters = {
      http = {
        qwen = function()
          return require("codecompanion.adapters").extend("ollama", {
            name = "qwen",
            schema = {
              model = {
                default = "qwen2.5-coder:7b",
              },
              num_ctx = {
                default = 16384,
              },
              think = {
                default = false,
              },
              keep_alive = {
                default = "5m",
              },
            },
          })
        end,
      },
    },
    extensions = {
      mcphub = {
        callback = "mcphub.extensions.codecompanion",
        opts = {
          make_vars = true,
          make_slash_commands = true,
          show_result_in_chat = true
        }
      }
    },
    opts = {
      log_level = "DEBUG",
    },
  }
}

Do note I'm not seeing any error message, typing Enter just creates a newline and that's it.

As far as I can tell, the rest of the plugin seems to work alright, I get answers from my local qwen2.5-coder:7b model and it seems to read files and all, but the lack of slash commands puts a serious dent in the usability.

So far I've tried on an Ubuntu Linux (home) and MacOSX machine (work) and both exhibit the same behaviour.

If it helps, my whole config is on github:
https://github.com/Bastes/nvim-config

(and sorry if it isn't the right channel where to post this request for help, but I don't seem to get much traction posting it on more general neovim channels)

[olimorris]

You need to complete as per your completion provider, or if you don't have one, as per the keymap outlined in the docs

[Bastes]

Hi, thank you for replying :) (so fast, too :) )

I'm using fzf_lua through vim-cmp, and as far as I can tell this is what codecompanion uses to suggest the command ; usually I complete by typing "space", and in this case typing "space" completes the word but does not trigger the plugin either. I'll be looking into the documentation for vim-cmp and coming back after trying something more explicit adding a shortcut for that.

[Bastes]

Ok, got it! It was vim-cmp that had no explicit <CR> mapping to validate an input. Thank you for your help diagnosing.