vibing-nvim

---

Table of Contents

• Why vibing.nvim?
• Features
• How It Differs
• Installation
• Usage
• Configuration Examples
• Configuration Reference
• Chat File Format
• Architecture
• FAQ
• Contributing
• License
• Links

💡 Why vibing.nvim?

vibing.nvim takes a fundamentally different approach to AI-assisted coding in Neovim.

CLI Adapter Architecture

Unlike traditional chat-based AI plugins that send static context to an LLM, vibing.nvim gives AI direct access to your Neovim instance through CLI backends and MCP integration.

This means the AI can:

- **Autonomously explore your codebase** - Navigate files, search symbols, and understand
  project structure without manual context setup
- **Access real-time editor state** - Query LSP diagnostics, symbol definitions, and references
  on demand
- **Execute Neovim commands** - Perform editor operations as part of its workflow
- **Maintain conversation continuity** - Resume sessions with full context preserved in
  `.vibing` files

Multi-Backend Support

vibing.nvim supports multiple AI CLI backends with a unified interface:

• Claude CLI (claude -p --stream-json) - Full Claude Code capabilities within Neovim
• Codex CLI (codex exec --json) - OpenAI Codex backend for alternative AI workflows

Switch backends globally via adapter config or per-chat via the agent frontmatter field.

Concurrent Sessions

Work on multiple tasks simultaneously without blocking:

• Multiple chat windows - Open separate conversations, each with its own independent session
• No waiting - Start a new chat while another is still processing

Example workflow:

:VibingChat  " Debug authentication issue in chat 1
:VibingChat  " Design new feature in chat 2

All sessions run independently with proper conflict management.

✨ Features

🤖 Neovim as an Agent Tool

Claude can directly interact with your running Neovim instance via MCP:

• Read and write buffers programmatically
• Execute Ex commands and Lua code
• Query LSP for diagnostics, definitions, references, and symbols
• Navigate the file system within your project

💾 File-Based Session Persistence

Each conversation is saved as a .vibing file with YAML frontmatter:

• Portable - Share conversations with teammates or across machines
• Resumable - Continue exactly where you left off with full SDK session state
• Auditable - All settings (model, mode, permissions) are visible in the file
• Version-controllable - Track AI-assisted changes in Git

🛡️ Granular Permission System

Fine-grained control over what Claude can do:

• Allow/deny specific tools (Read, Edit, Write, Bash, etc.)
• Path-based rules for sensitive files
• Command pattern matching for shell operations
• Interactive Permission Builder UI

📋 Diff Preview with Accept/Reject

Telescope-style diff preview for all code modifications:

• Visual diff for each changed file
• Accept all or reject all with Git-based revert
• Navigate between multiple modified files
• Works in chat mode

🔀 Concurrent Session Support

Run multiple AI tasks simultaneously:

• Independent chat sessions - Each chat window maintains its own conversation and session ID
• Parallel workflows - Debug in one chat while designing features in another

Other Features