Live data from Hacker News

Cursor CLI

cursor.com

231–240 of 275 posts

Re: Cursor CLI

#231

I wonder when all of them will adopt AGENT.md and stop using gemini.md/claude.md/crush.md/summary.md/qwen.md https://agent.md [redirect -> https://ampcode.com/AGENT.md ] https://agent-rules.org

That sounds nice and I have the same pain, but not sure AGENT.md is the right abstraction either. After all, these models are indeed different and will respond differently even given the same prompting. Not to mention that different wrappers around those models have different capabilities. e.g. maybe for CURSOR.md you just want to provide context and best practices without any tool-calling context (because you've fou…

Then lets do:

  AGENT.md
  AGENT.CLAUDE.md
They get applied AGENT first, then AGENT.CLAUDE. You are able to specify agent specific instructions in the AGENT.md:

  @agent-disable CLAUDE
  These instructions are not parsed by claude
  @agent-enable CLAUDE

Re: Cursor CLI

#233

Earlier quoted context omitted.

> 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.

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 a…

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

Re: Cursor CLI

#234
post #226

Earlier quoted context omitted.

My company has a huge codebase, for me cursor would freeze up / not find relevant files. Claude code seems able to find the right files by itself. I seem to always have better outcomes with Claude code.

How does Claude Code handle editing multiple files? My understanding is that it's CLI based, so it edits a bunch of files on it's own, so how do you accept/reject and rollback changes?

I use git and when necessary, git worktrees to keep parallel Claudes from bothering/actively-undoing each other’s edits (esp when an edit requires multiple files of changes, so the tree is temporarily broken).

Re: Cursor CLI

#235
Excited to see competition. The UX is not as polished as Claude Code though. For instance, missing a command to fire shell commands (in CC done via `! {commmand}`. And has less commands overall. But will catch up I hope.

Re: Cursor CLI

#236
post #226

Earlier quoted context omitted.

My company has a huge codebase, for me cursor would freeze up / not find relevant files. Claude code seems able to find the right files by itself. I seem to always have better outcomes with Claude code.

How does Claude Code handle editing multiple files? My understanding is that it's CLI based, so it edits a bunch of files on it's own, so how do you accept/reject and rollback changes?

> how do you accept/reject and rollback changes?

Git

Re: Cursor CLI

#237

I wonder when all of them will adopt AGENT.md and stop using gemini.md/claude.md/crush.md/summary.md/qwen.md https://agent.md [redirect -> https://ampcode.com/AGENT.md ] https://agent-rules.org

(I work at Cursor) The CLI supports AGENT.md as well as CLAUDE.md and Cursor Rules.

Re: Cursor CLI

#238
post #85

I'm having trouble finding a use for this outside of virtualized unused environments. Why not instead give me a virtual machine that runs this in a confined storage space? I would _never_ give an LLM access to any disk I own or control if it had anything more than read permissions

(I work at Cursor) We also support running the agent in a VM at cursor.com/agents

Re: Cursor CLI

#239
post #216

Earlier quoted context omitted.

Because you can script terminal app (ideally, at least you can do that with opencode.ai) and that opens some amazing opportunities.

How and why would one script things like this? I thought the process was basically just talking to the agent and telling it what you want to do and reviewing the changes before they are committed.

Well. Agents use context and context window has limit. If you add too much to context you will get poor result. You can split your task in smaller ones and in result you might get much better result. E.g. migration of tests to new version of library.

Re: Cursor CLI

#240
post #98

I went from years of vscode to "Cursor is the future" to never using Cursor at all. Claude Code, even with new limits, is just too good. If I were to switch to gpt-5, why wouldn't I just use Codex? I'm struggling to understand the value of what they're presenting.

I find it really difficult to take this stuff seriously when the proponents of these tools are constantly flitting from tool to tool. There's tools and paradigms I've used for years at a time. Some things like vim have been used for decades.

This all just feels profoundly immature. You tell us one thing then two months later you're on to the next thing. There's no sense of mastery here.

Post reply on HN