ravitemer pushed a fix to main that enhances workspace file handling by using fs_lstat to detect symlinks, adding a symlink_target field, and formatting links as “symlink → target.” They also improved path handling to respect a specified directory instead of cwd and added cross-platform support via git -C and vim.fs.joinpath (fixes #268).

ravitemer pushed a fix to the main branch that updates lua/mcphub/hub.lua by adding a self:fire_servers_updated() call right after native.setup so chats see new servers as soon as possible, resolving issue #260.

This change removes the forced assignment of vim.o.winborder in the confirmation window setup, leaving win_opts.border nil so Neovim will automatically apply either the user’s custom border or its default. It restores support for custom border characters that was broken by a previous PR and keeps the project’s UI consistent with user settings. However, documentation wasn’t updated to reflect this change, formatting checks were skipped, and there may still be edge cases on older Neovim versions or empty-border scenarios.

This change adds explicit buffer deletion whenever confirmation or input windows close in mcphub.nvim, cleaning up unused hidden buffers and plugging a minor memory leak. It streamlines the hidden-buffer list without altering any user-facing behavior, and all existing tests pass. One potential concern is that forcibly deleting buffers—even with validity checks—might race with other scheduled operations or remove buffers still expected by other plugins or callbacks.

This change adds additionalProperties = false to the tool_input schema for the use_mcp function to satisfy strict JSON schema requirements and resolve invalid schema errors when using GPT-5.x on GitHub Copilot. It enforces tighter validation for nested objects, prevents unexpected properties, and ensures tests and tooling pass cleanly. However, the stricter schema may break existing calls that relied on passing extra or dynamic fields in tool_input and could necessitate updates to client code or documentation.

This update extends mcphub.nvim to support CodeCompanion v18.0.0 by renaming the chat API from strategies to interactions, updating documentation (including VS Code JSON5 support and slash-command guides), and adding a CopilotChat extension. It enhances integration and feature discoverability but changes core configuration keys and adds a large volume of docs and code changes that could break existing setups. Since tests weren’t run and such widespread renames may introduce regressions or backward-compatibility issues, users should review and validate their configs before upgrading.

This adds a check in create_function_name to truncate any generated function name to 64 characters, preventing the “string too long” errors when registering CopilotChat tools. By ensuring names never exceed the limit, it avoids registration failures, but blunt truncation could lead to name collisions or loss of distinguishing information.

This change simply inserts a missing newline in the configuration.md documentation to improve formatting, with no impact on the codebase or functionality. It’s a low-risk tweak that doesn’t introduce breaking changes, and there are no significant concerns beyond its trivial nature.

It inserts a default set of box-drawing characters for window borders when vim.o.winborder is empty so that the confirmation dialog’s header and buttons are no longer invisible. This change improves UI consistency out of the box by ensuring dialogs are always framed. However, hardcoding a specific border style may conflict with custom themes, environments without proper glyph support, and offers no fallback or configuration options for alternative borders.

By including server.capabilities.prompts in the renderer’s capability count, this change makes prompt-only native servers show up correctly in the mcphub UI. It improves visibility for servers that define only prompts, but the PR skips documentation updates and may introduce UI inconsistencies or edge-case behavior where prompts weren’t previously considered.