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

161–170 of 275 posts

Re: Cursor CLI

#161

Post by LeafItAlone »

gpeal wrote: post #144
LeafItAlone wrote: post #124

Earlier quoted context omitted.

I find the Codex CLI to be the worst of the CLI tools I’ve used (including, but not limited to, Claude Code, Gemini, Aider). There’s something about it that makes it clunky. Haven’t tried Cursor CLI yet though.

We (Codex) shipped a pretty large CLI update today and have many more improvements coming. Give it a try if you haven't. https://x.com/OpenAIDevs/status/1953559797883891735 (0.19 now)

Thanks for the heads up. I’ll check it out!

I don’t visit Twitter links. Why not a link to the GitHub changelog?

Also, as an aside since you are on the team - the organization verification is frustrating in that the docs indicate:

>You must not have recently verified another organization, as each ID can only verify one organization every 90 days.

I champion OpenAI at my work, so naturally I’d be the one to verify there. But I apparently can’t, because I verify for my personal-led org. That gets in the way of me proselytizing gpt-5 based coding tools (such as, possibly, Codex CLI).

Re: Cursor CLI

#162

Post by alwillis »

byronic wrote: 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

For example, Gemini CLI [1] can use native sandboxing on macOS. It's just a matter of time before every major coding agent will run inside of an operating system's native sandbox/container/jail/VM.

[1]: https://github.com/google-gemini/gemini-cli/blob/main/docs/c...

Re: Cursor CLI

#163

Post by alwillis »

zaphirplane wrote: post #6
sblawrie wrote: post #4

Earlier quoted context omitted.

You can spin up the Cursor CLI inside the terminal of your IDE of choice and not be tethered to Claude's models.

Is there a better agent than the anthropic one

You can already use non-Anthropic models with Claude Code with tools like Claude Code Router [1].

[1]: https://github.com/musistudio/claude-code-router

Re: Cursor CLI

#164

Post by kristjansson »

LeafItAlone wrote: post #161
gpeal wrote: post #144

Earlier quoted context omitted.

We (Codex) shipped a pretty large CLI update today and have many more improvements coming. Give it a try if you haven't. https://x.com/OpenAIDevs/status/1953559797883891735 (0.19 now)

Thanks for the heads up. I’ll check it out! I don’t visit Twitter links. Why not a link to the GitHub changelog? Also, as an aside since you are on the team - the organization verification is frustrating in that the docs indicate: >You must not have recently verified another organization, as each ID can only verify one organization every 90 days. I champion OpenAI at my work, so naturally I’d be the one to verify the…

Huge +1 to this. We have two orgs at work (for separate budget/rate limit blast radii) and had to get two people to verify this morning…

Re: Cursor CLI

#165

Post by imp0cat »

tsvetkov wrote: post #31
worldsayshi wrote: post #27

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…

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

Re: Cursor CLI

#166

Post by imp0cat »

ankit219 wrote: post #82

I think CLI is a good idea for now. Next abstraction seems to be Github PRs where someone (likely me) files an issue/feature, then I click a button, and the agent fixes the issue/feature. Github has talked about something similar, but surely it were a pain to figure out if it was GA and I had access to it given so many different variations they have called gh copilot. (PS: it exists, but not as smooth as I described:…

You can already have that with Jules. It's quite impressive.

https://jules.google/

Re: Cursor CLI

#167

Post by ako »

MrGreenTea wrote: post #152
ako wrote: post #147

Earlier quoted context omitted.

I've added these instructions in CLAUDE.md and .windsurfrules, and yes sometimes you have to remind it, but overall it works quite well.

Habe you though about adding a Session start hook that reads this file and adds it to the context?

Not yet, but that sounds like a good suggestion.

Re: Cursor CLI

#168

Post by drdaeman »

zarzavat wrote: post #145
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

Never. It's a marketing strategy. Some percentage of users will check these files into their repos, and some percentage of repo browsers will think "what is this X.md?" Given how much money people are spending on these things the value of having a unique filename must be enormous.

It’s a marketing strategy that works here and now, but “never” is a very long time. What could be seen as pioneers claiming names today could be also seen as retrogressive stubbornness tomorrow and lose its marketing value.

Re: Cursor CLI

#169

Post by stpedgwdgfhgdd »

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

The deeper problem are the custom commands, hooks and subagents. The time has come that you need to make a strategic choice. Once you have heavily invested into CC, it is not easy to turn to an alternative.

Side remark: CC is very expensive when using API billing (compared to e.g. GPT-5). Once a company adopts CC and all developers start to adapt to it at full scale, the bill will go out of the roof.

Re: Cursor CLI

#170

Post by eru »

yunohn wrote: post #160
eru wrote: post #134

Earlier quoted context omitted.

> It would force me to have a useful, up to date document about how to build, run, and edit my projects. Not really: our AI agents are probably smart enough to even make sense of somewhat bad instructions.

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.
Post reply on HN