Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cursor CLI

cursor.com

Post reply on HN
Print view View original

211–220 of 275 posts

Re: Cursor CLI

#211

Post by computerfriend »

sneak wrote: post #53
thehamkercat wrote: post #21

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

When they stop getting desperate for differentiation by spamming their brand advertising in your repo against your will. Claude Code likes to add "attribution" in commit messages, which is just pure spam.

I've experimented a little with LLM agents (only Claude Code). I definitely don't want the agent to write the commit messages (they should be written by a human as they're for human consumption) so I manually added the co-author trailer. It's morally correct to provide attribution.

Re: Cursor CLI

#212

Post by yunohn »

eru wrote: post #170
yunohn wrote: post #160

Earlier quoted context omitted.

They’re definitely not, Claude and all other agents frequently forget the build and test commands present in CLAUDE/etc.md for my various repos (even though most of them were were initialized by the AI).

Whether Claude and co understand is probably not a great proxy for whether your docs are good for humans.

Hmmm, in my experience if something like documentation confuses the current SOTA LLMs, then it will confuse the average developer for sure.

Re: Cursor CLI

#214

Post by __MatrixMan__ »

bikeshaving wrote: post #91
thehamkercat wrote: post #21

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

Every time I’ve ever read a {CLAUDE|GEMINI|QWEN}.md I’ve thought all this information could just be in CONTRIBUTING.md instead.

If I'm writing for a human contributor, I'm gonna have a pretty high bar for the quality of that writing.

An agent on the other hand, one who is in that sweet spot where they're no longer ignorant, and not yet confused... It's nice to have them dump their understanding to agent_primers/subsystem_foo.md for consumption by the next agent that touches that subsystem. I don't usually even read these until I suspect a problem in one. They're just nuggets of context transfer.

Re: Cursor CLI

#215

Post by Jenk »

ascorbic wrote: post #202
ako wrote: post #137

Earlier quoted context omitted.

I asked claude code for a guidelines file so it would collaborate with windsurf. This is what it proposed: --- This project uses shared planning documents for collaboration with Claude Code. Please: 1. First read and understand these files: - PLAN.md - current project roadmap and objectives - ARCHITECTURE.md - technical decisions and system design - TODO.md - current tasks and their status - DECISIONS.md - decision h…

You could create a CLAUDE.md that just contains: @AGENTS.md Still messy, but at least it means it's using the same content

What about

    ln -s AGENTS.md CLAUDE.md # repeat for all

?

Re: Cursor CLI

#216

Post by ksynwa »

daliusd wrote: post #209
ksynwa wrote: post #207

Why are all these coding agents being created as terminal applications? Feels like the kind of thing that the tech industry would publish as an electron app.

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.

Re: Cursor CLI

#218

Post by easeout »

ksynwa wrote: post #207

Why are all these coding agents being created as terminal applications? Feels like the kind of thing that the tech industry would publish as an electron app.

Shell commands and files on disk are the classic narrow waist, and this type of tool, exemplified by Claude Code, locates a coding agent down in that ecosystem.

Why shouldn't you be able to use the abilities of this tool as a batch command, connected with all your other basic tools, in addition to interactive sessions?

Cursor's chat being locked in an IDE sidebar has felt like driving with a trailer attached. For some tasks the editor is secondary or unnecessary, and as a papered-over VS Code fork, Cursor has a lot of warts that you just had to accept. Now you can just use your favorite editor.

Companies make apps but want to be platforms, so they try to put everything in one app and help you forget about everything else. VS Code and Figma, for example, make their own extension ecosystems rather than connecting outward, because it makes them platforms-as-apps and harder to leave. But a desktop task workflow spans many apps and windows. You compose it yourself to your needs. We are computer users more than app users.

To me as a computer user, a tool that's compact and has compatible outward extension points feels good.

Re: Cursor CLI

#219

Post by jona777than »

amclennon wrote: post #8

At this point, there are more AI coding agents announced every week than Javascript frameworks, but to be honest, I'm here for it.

This made me chuckle. Excellent comparison. I share your sentiment; it’s more exciting than distracting.

Re: Cursor CLI

#220

Post by SwiftyBug »

kridsdale3 wrote: post #67
consumer451 wrote: post #30

Earlier quoted context omitted.

In one of their Claude Code talks they said it didn’t seem worth it, given their expectation that all IDEs will become obsolete by next year.

Xcode pretty much hung up their hat this year, and threw in with Claude.

What do you mean? I've been patiently waiting for the death of Xcode for a long time. Do you think it's near?
Post reply on HN