Hacker News Reader

> why an IDE is required for an agent that codes for you

Because the agents aren't yet good enough for a hands off experience. You have to continuously monitor what it does if you want a passable code base.

View on HN

Sure, but monitoring, reviewing and steering does not really require modern IDEs in their current form. Also, I'm sure agents can benefit from parts of IDE functionality (navigation, static analysis, integration with build tools, codebase indexing, ...), but they sure don't need the UI. And without UI those parts can become simpler, more composable and more portable (being compatible with multiple agent tools). IMO another way to think about CLI agentic coding tools as of new form of IDEs.

As was already mentioned elsewhere, Emacs + Magit to monitor incoming changes is a great combo.

yes i am rejigging my whole vim setup

Following are now stars of my workflow

* Git plugins - Diffview, gitsigns, fugitive

* Claude Code plugin / Terminals with claude code

* Neovim sessions

* Git worktrees

Editing focused workflows have taken an backseat

* LSP

* Vim motion and editing efficiency

* File navigation

* Layouts

why even use vim at this point? the LLM ecosystem there is decent, but definitely less polished than using a modern IDE

Vim motions are nice.

Reply on news.ycombinator.com