explaingit

cachebag/jumpy.nvim

15LuaAudience · developerComplexity · 2/5ActiveLicenseSetup · easy

TLDR

A Neovim plugin that asks an LLM to suggest edits as in-buffer hunks the user accepts or rejects one at a time, keeping the human in charge of every change.

Mindmap

mindmap
  root((jumpy.nvim))
    Inputs
      Selected lines
      Prompt text
      API key env var
    Outputs
      Inline hunks
      Accepted edits
    Use Cases
      Per-hunk AI edits
      Reviewable code changes
      Token-efficient prompts
    Tech Stack
      Lua
      Neovim
      lazy.nvim
    Providers
      Anthropic
      OpenAI
      OpenRouter

Things people build with this

USE CASE 1

Accept or reject AI suggestions hunk-by-hunk inside a Neovim buffer

USE CASE 2

Send only changed lines to a model to keep token use low

USE CASE 3

Swap between Anthropic, OpenAI, and OpenRouter providers without leaving the editor

Tech stack

LuaNeovim

Getting it running

Difficulty · easy Time to first run · 5min

Requires an API key for Anthropic, OpenAI, or OpenRouter set as an environment variable before launching Neovim.

MIT license allows anyone to use, modify, and distribute the plugin with attribution.

In plain English

Jumpy is a plugin for the Neovim text editor that lets a programmer ask an AI to edit code in small, reviewable chunks. The author was inspired by another tool called 99 and built jumpy because they want to keep their hands on the steering wheel even when an AI is writing code on their behalf. The repo has 14 stars and is written in Lua. The idea is to keep the human in charge of every change. Instead of letting an AI rewrite whole files or run as a separate agent, jumpy opens a prompt inside the editor, sends only the relevant lines to the AI, and shows the suggested edits as hunks inside the same buffer. The user can then accept or reject each hunk one at a time, jump to the next or previous hunk, accept everything, reject everything, or ask for a fresh attempt on the hunk under the cursor. In a comparison table, the README contrasts jumpy with other AI coding tools such as avante, sidekick, codecompanion, claude code, and aider. The pitch is that jumpy uses a per-hunk accept and reject model with no context switch out of the buffer, and that it sends only changed lines back to the model, which the author describes as more token efficient than alternatives that pass full files. Installation is done through the lazy.nvim package manager, and the plugin supports Anthropic, OpenAI, and OpenRouter as model providers via environment variables for the API key. Keybindings include leader plus j to open the prompt, bracket h to move between hunks, and leader plus a or x to accept or reject the current hunk. The author is candid that the project is early and rough. They write that they do not really know what they are doing and that the tool does not work very well yet, but they hope it will get better. The license is MIT.

Copy-paste prompts

Prompt 1
Add jumpy.nvim to my lazy.nvim config with OpenRouter as the provider
Prompt 2
Show me a workflow for refactoring a function in Neovim using jumpy's per-hunk accept
Prompt 3
How does jumpy compare to avante.nvim and codecompanion for token cost on a 500-line file
Prompt 4
Customize the leader+j keybinding for jumpy to use a different chord
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.