Track mcphub.nvim CodeCompanion v19 compatibility workaround

[oyoshot]

Context

Neovim startup hit this error after CodeCompanion moved to v19:

vim.schedule callback: ...mcphub.nvim/lua/mcphub/extensions/codecompanion/variables.lua:20: bad argument #1 to pairs (table expected, got nil)

Cause: CodeCompanion v19 renamed chat variables to editor_context, while current mcphub.nvim still reads config.interactions.chat.variables in its CodeCompanion extension.

Upstream tracking:

• Crash on startup with codecompanion v19 — nil passed to pairs() in variables.lua ravitemer/mcphub.nvim#275: Crash on startup with codecompanion v19
• odecompanion extension: make_vars crashes — config.interactions.chat.variables is nil ravitemer/mcphub.nvim#278: make_vars crashes because config.interactions.chat.variables is nil
• fix(codecompanion): compatibility with v19 ravitemer/mcphub.nvim#276: closed, replaced by #279
• feat(extensions): adapt CodeCompanion extension for v19 compatibility ravitemer/mcphub.nvim#279: open and not merged as of 2026-04-13

Local workaround

Committed on branch nvim-0.12-compat:

• 72f9d47 fix(nvim): disable mcphub vars for codecompanion v19

This sets:

make_vars = false

in dot_config/nvim/lua/plugins/codecompanion.lua.

MCP tools and slash commands remain enabled. Only MCP resources as CodeCompanion # editor context are disabled.

Done when

• feat(extensions): adapt CodeCompanion extension for v19 compatibility ravitemer/mcphub.nvim#279 or an equivalent v19 compatibility fix is merged and released or available in lazy.nvim
• make_vars = true can be restored without the startup Lua error
• Neovim starts cleanly with CodeCompanion and mcphub loaded