Majjoha Nvim Context
majjoha-nvim-context is a Claude Code plugin for the Build phase that bridges running Neovim instances so agentic coding tools use live editor context.
by majjoha · github.com/majjoha/nvim-context
Install the nvim-context bridge so Claude Code and other agentic tools read live buffer context from running Neovim instances while you code.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install majjoha-nvim-context@majjoha/nvim-contextBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:majjoha/nvim-context") and the paste-ready config with skillselion.get_install_config("plugin:majjoha/nvim-context").
What it does
majjoha-nvim-context is a Claude Code plugin marketplace entry from majjoha/nvim-context that ships one plugin to bridge live Neovim instances with agentic coding tools. Solo builders who live in Neovim install it when they want Claude Code (or similar agents) to see real editor context—buffers, instances, and coding session state—rather than manually pasting files or relying on partial workspace indexes. The description frames it explicitly as a bridge between running Neovim and agents, which makes it development infrastructure rather than a product feature or launch playbook. It suits indie developers optimizing an Neovim-plus-agent stack during active implementation, not teams standardized on VS Code only. Setup is intermediate: Neovim running locally or remotely, agent host configured, and security awareness because editor bridges can expose sensitive code paths.
Highlights
- Single-plugin marketplace bridging running Neovim instances to agentic coding tools
- Exposes editor context so agents align suggestions with what is actually open and active
- Community-listed integration aimed at nvim-centric solo dev workflows
- Reduces copy-paste context handoffs between terminal editor and Claude Code
- Requires both Neovim and the host agent to be running with compatible bridge setup
Why builders use it
Agentic tools miss what you are actually editing in Neovim, forcing redundant context dumps and wrong-file suggestions.
After you add the plugin, your agent can consume Neovim context from running instances and stay aligned with your live coding session.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 1 stars, 0 votes.
FAQ
Who is majjoha-nvim-context for?
It is for developers who run Neovim alongside Claude Code or other agentic tools and want automated context sync from live editor instances.
When should I use majjoha-nvim-context?
Use it during Build when agent suggestions should reflect open buffers and multi-instance Neovim sessions without manual exports.
How do I add majjoha-nvim-context to my agent?
Register the majjoha/nvim-context marketplace in Claude Code, install the bundled bridge plugin, and configure Neovim plus agent connectivity per upstream docs.
Comments
Share how you use majjoha-nvim-context, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.