问HN：为什么开发者开始转向基于命令行的编码助手？
在过去几个月里，我认识的大多数工程师都从Cursor转向了基于命令行界面的代理（主要是Claude Code）。我个人非常喜欢任何基于命令行的工具，但我惊讶地发现，几乎从不打开终端的开发者们，如今却在一夜之间成为了Claude Code和终端的重度用户。
从技术上讲，代理在终端运行并不是绝对必要的——在Cursor聊天中运行的代理可以将终端作为工具使用，并且可以说其用户界面更为友好。通常从命令行工具中获得的价值（如输入输出的管道、可组合性）并不适用于这些代理的使用方式。
我的理论有两个方面。首先，使用像Claude Code这样的命令行代理可以获得更好的价值，因为你不需要向像Cursor这样的集成开发环境支付“过路费”。其次，Claude Code中有一些强大的功能，比如“计划模式”，如果没有控制用户体验，Anthropic是无法实现这些功能的。但我很想听听其他人的看法，以及基于命令行的代理是否会长期存在。
查看原文
In the last few months, most of the engineers I know have switched from Cursor to CLI-based agents (mostly Claude Code). I personally love anything CLI-based, but I've been surprised to see developers who almost never open a terminal now becoming Claude Code and terminal power users overnight.<p>Technically, there isn't a real need for agents to run in the terminal - an agent running in Cursor chat can use the shell as a tool and arguably has a nicer UI. The value you'd normally get from CLI tools (piping I/O, composability) doesn't really apply to how these agents are being used.<p>My theory is twofold. First, you get better value using CLI agents like Claude Code because you don't need to pay a "toll" to an IDE like Cursor. Second, there are some killer features in Claude Code like "plan mode" that wouldn't have been possible for Anthropic to build without controlling the experience. But curious to hear what others think, and whether CLI-based agents are here to stay?