Vibing-Nvim

Prerequisites

- Neovim 0.10+ (uses vim.system()) - Node.js 18+ (for the MCP server) - At least one AI CLI backend: - Claude CLI (claude) — npm install -g @anthropic-ai/claude-code - Codex CLI (codex) — npm install -g @openai/codex (0.140+; see note below) - GitHub Copilot CLI (copilot) — npm install -g @github/copilot (needs Node.js 22+, higher than the 18+ the MCP server itself requires) - Grok Build CLI (grok) — see xAI's install docs

Codex version note. vibing.nvim runs the Codex backend's lightweight calls (chat title generation, /summarize, daily summary) with --ignore-user-config --strict-config, which keeps those calls out of your MCP servers and makes them fail loudly rather than silently unfenced if Codex renames a config key. Both flags were verified present in 0.140.0 and 0.147.0, on codex exec and codex exec resume alike. Older releases were not tested; if they lack the flags, ordinary chat is unaffected but lightweight calls fail with an unknown-argument error. Upgrade Codex if you see that. --ignore-user-config also drops model_provider, so if your config.toml points Codex at a custom or local provider, those lightweight calls go to the default OpenAI endpoint instead. Ordinary chat still uses your provider. vibing.nvim warns once per Neovim session when this applies to you, asking Codex itself (codex doctor --json) which provider is configured; it says nothing if Codex cannot answer. Set agent.codex_provider_notice.enabled = false to turn the warning and its probe off.

Why does it require Node.js?

Node.js is required for the MCP server, which provides AI with direct access to your running Neovim instance (buffer reads/writes, LSP queries, command execution). The AI CLI binaries themselves (claude, codex, copilot) are separate installs.

📦 Installation

🚀 Quick Start

:VibingChat        " Open a new chat

Type your message under the ## User header and press <CR> in normal mode to send. The AI responds in the same buffer; <C-c> cancels a running request. Chats remain ordinary Markdown files that you can save, search, and edit normally. In Neovim, the small vibing Tree-sitter parser isolates chat headers and tool output, then injects the standard Markdown parser into each message body. Existing Markdown highlighting, including fenced code languages, is preserved.

🚀 Usage

Also available offline as :help vibing-commands, which carries per-command help tags.

⚙️ Configuration

require("vibing").setup() works out of the box. Commonly tweaked options:

require("vibing").setup({
  adapter = "claude",              -- "claude" | "codex" | "copilot"
  chat = {
    window = {
      position = "current",        -- "current" | "right" | "left" | "top" | "bottom" | "back" | "float"
      width = 0.4,                 -- screen-width ratio (0-1)
    },
    save_location_type = "project", -- "project" | "user" | "custom"
  },
  agent = {
    default_model = "sonnet",      -- backend model id, e.g. "sonnet" or "gpt-5.6-terra"
    scheduled_requests = {
      enabled = true,              -- during a usage limit, <CR> schedules instead of sending
    },
  },
  permissions = {
    mode = "acceptEdits",          -- "default" | "acceptEdits" | "plan" | "auto" | "dontAsk" | "bypassPermissions"
    allow = { "Read", "Edit", "Write", "Glob", "Grep", "Skill", "StructuredOutput" },
    deny = { "Bash" },
    codex_profile_file = ".vibing/codex-permissions.toml", -- false disables loading the generated profile
    codex_allow_tracked_profile = false, -- true explicitly trusts a Git-tracked profile
  },
  language = nil,                  -- e.g. "ja", or { default = "ja", chat = "ja" }
})

The default permissions shown above are used as a template when creating new chat files; each chat file's frontmatter carries its own permissions, which are what's enforced at runtime.

For the Codex backend, vibing.nvim creates .vibing/codex-permissions.toml when it initializes a project. Its default profile permits workspace and Git metadata writes without using full bypass mode; edit the file to narrow or extend the OS sandbox. Existing files are never overwritten. Git-tracked profiles are rejected unless codex_allow_tracked_profile = true explicitly trusts the reviewed file; locally generated, untracked profiles continue to load automatically. See Project-local Codex permission profiles.

Full reference: every option (window details, UI/gradient/tool markers, diff backends, granular permission rules, MCP, Node.js executable, daily summary, ...) is documented in handbook/configuration.md.

language: ja # Optional: default language for AI responses

Claude Code Plugin (MCP + Skills + Agents)

vibing.nvim ships a Claude Code plugin that bundles the vibing-nvim MCP server together with Neovim-aware skills and a read-only navigation subagent.

Nothing to install. The plugin is not registered into Claude Code's global state at all — vibing.nvim hands the CLI its own claude-plugin/ directory per session with --plugin-dir, so whichever checkout is running is the one that serves you. build.sh builds the MCP server and the small Tree-sitter parser used for chat boundaries (and, once, cleans up an install from an older version of vibing.nvim). If no C compiler is available, the parser build is skipped and chat buffers fall back to the previous whole-buffer Markdown parser.

That gives you mcp__plugin_vibing-nvim_vibing-nvim__* tools (buffer/window/cursor access, Ex commands, and LSP queries against the running Neovim instance), the bundled skills (nvim-context, nvim-lsp-navigation, vibing-chat-recall, vibing-chat-search, and the vibing-worktree-{list,create,attach,run,finish} worktree workflow), and the nvim-navigator subagent (read-only code navigation via @vibing-nvim:nvim-navigator).

You still need Neovim running with mcp = { enabled = true } (the default) for the MCP tools to have anything to connect to. The one trade-off is that a plain claude session started outside Neovim no longer sees these tools; that was never a supported way to use them.

The Codex backend gets the same plugins without a --plugin-dir of its own: the MCP server is registered per run as -c mcp_servers.vibing-nvim.* (tools named mcp__vibing-nvim__*) and the skills are listed for the model in developer_instructions. Subagents do not carry over.

Your own project plugins. Anything you drop into .vibing/plugins/<name>/ (with a .claude-plugin/plugin.json) is loaded the same way, for chats in that project only. Run :VibingReloadCommands after adding one, or :VibingCreatePlugin <name> to write a working skeleton in the first place. Note that a plugin may declare mcpServers, so a plugin in a repository you cloned can start a process on your machine — set agent.plugins.project_dir = false for repositories you do not trust. See handbook/configuration.md for agent.plugins.

Upgrading from an older vibing.nvim: build.sh removes the user-scope install and its marketplace entry for you. To do it by hand:

/plugin uninstall vibing-nvim@vibing
/plugin marketplace remove vibing

Can I use vibing.nvim alongside other AI plugins?

Yes. vibing.nvim doesn't conflict with completion plugins (Copilot, Codeium) or other chat plugins. Use vibing.nvim for deep Claude interactions and other tools for quick completions or different providers.

Consider alternatives if you

• Need local/offline models (Ollama, etc.)
• Prefer minimal dependencies (vibing.nvim requires Node.js for the MCP server)
• Want a battle-tested plugin with a large community (we're still growing!)

vibing.nvim doesn't conflict with completion plugins (Copilot, Codeium) or other chat plugins — they compose well.

How does it compare to Claude Code CLI?

vibing.nvim provides similar capabilities to Claude Code CLI but integrated into Neovim:

• Same claude CLI underneath
• MCP for editor control (CLI controls terminal, vibing controls Neovim)
• Additional Codex and GitHub Copilot backend options for non-Anthropic workflows

Think of it as "Claude Code (or Codex, or Copilot) for Neovim users."

❓ FAQ