Neovim sweetspot between trad coding and AI coding
The article discusses a new coding tool called Jumpy, designed to provide users with control over AI-assisted coding. Unlike other tools, Jumpy allows for inline prompts and per-hunk acceptance or rejection of changes, ensuring that users can review modifications in real-time. The author expresses a desire for a balance between traditional coding and AI assistance, emphasizing the importance of maintaining control over the coding process.
- ▪Jumpy is designed to allow users to maintain control while using AI to edit code.
- ▪The tool features inline prompts and per-hunk acceptance or rejection of changes.
- ▪The author prefers to handwrite code while utilizing AI, wanting to review changes immediately.
Opening excerpt (first ~120 words) tap to expand
jumpy Inspired by 99: I, like Prime, wanted a tool to allow for me to still be in the driver seat if I am going to spawn an AI to edit my code. The main difference between jumpy and other tools, like 99, are: feature jumpy avante / sidekick codecompanion inline claude code / aider Interaction model Inline prompt → hunks in buffer Sidebar chat → apply Inline edit → accept/reject CLI agent → full file writes Review granularity Per-hunk accept/reject Per-file or per-suggestion Per-change Post-hoc (git diff) Context switch None: you stay in buffer Sidebar opens Minimal Leave editor or split terminal LLM output format Search/replace blocks Full file / patch Full file Full file via temp Token efficiency High (only changed lines sent back) Lower (full context) Lower Lower Scope Single targeted…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.