9/4/2026
Open Source Report · developer-tools

Grep beats LSP? Why coding agents ignore your fancier tools

Filed by Patch Reyes
Grep beats LSP? Why coding agents ignore your fancier tools
Another day, another dev tooling hot take: your fancy Language Server Protocol might be dead weight when an agent just needs to find a damn string. This piece from AgentConnect argues that grep—yes, plain old grep—often beats the LSP-equipped harnesses we’ve spent years worshipping. The reason? Speed, simplicity, and the fact that coding agents don’t need your whole project’s semantic graph to patch a bug. If you’ve ever watched an agent stall while waiting on a language server to index 400,000 files, you get it. The article makes a compelling case that sometimes the dumbest tool is the smartest choice. Read it before you add another heavyweight tool to your agent’s stack. Source: https://www.agentconnect.md/blog/grep-beat-lsp-harness/
P
Patch Reyes
Magazine AI commentary
Let’s be honest: the tech world has a fetish for complexity. We built LSPs to give editors superpowers, then bolted them onto AI agents like a rocket engine on a bicycle. But agents don’t think like human developers—they don’t need hover docs or go-to-definition to form a mental model. They need answers, fast, and grep gives them that without the ceremony. The AgentConnect piece isn’t saying LSPs are useless; it’s saying we’ve been optimizing for the wrong user. For an agent, a pattern match is often enough to make a change, and the milliseconds saved add up when you’re looping through a thousand edits. There’s a deeper lesson here about tool selection in the age of AI. We keep porting human-friendly workflows into agent runtimes, but agents don't have our cognitive bottlenecks. They don't get tired, they don't need autocomplete, and they don't care about type signatures unless the task demands it. The best agent tooling isn't the one with the richest features—it's the one with the lowest latency and the least noise. Grep wins because it’s deterministic, composable, and doesn't require a language server that crashes on monorepos. That’s a feature, not a bug. What’s really interesting is the pushback in the HN thread—49 comments, 75 points, and the usual chorus of “but LSPs are better for refactoring!” Sure, for semantic operations like rename-across-files, an LSP is invaluable. But most agent tasks are not semantic refactors; they’re “find the hardcoded config and tweak it” or “locate the function that throws this error.” For those, grep is not just adequate—it’s superior. The article’s real argument is about matching the tool to the task, and that’s a lesson that extends beyond coding agents to every AI pipeline we build. So before you strap another MCP server or LSP harness onto your agent, ask yourself: is this adding intelligence or just adding latency? The article makes a strong bet that grep will outlive half the agent frameworks we’re hyping today. I’m inclined to agree. The terminal’s oldest trick is still the one that ships code. Source: https://www.agentconnect.md/blog/grep-beat-lsp-harness/
📌 Read the real article ↗via Hacker News · Hacker News

💬 Discussion

Sign in to join the discussion.
Be the first to comment on this story.
Loading

Grep beats LSP? Why coding agents ignore your fancier tools — Open Source Report