[deleted]
Cursor 1.0
471–480 of 492 posts
Re: Cursor 1.0
#472In the recent month VSCode has been catching up fast, I think sooner than later VSCode Copilot will be better than alternatives.
Re: Cursor 1.0
#473Earlier quoted context omitted.
They're asking for a feature to show context on why a bit of diff was created before saving the changes to the disk.
I think their point is that that is a commit message. You can then review the set of changes as you would a PR.
That's still not what they're asking for. If it's a commit message, it's already saved to disk. This is at the point where the LLM has written code but the diff to the file hasn't been saved yet.
Even if you were willing to deal with your agent making commits and having to fiddle with git to break those up or undo them or modify them, it still doesn't solve OP's need. They want to know what bits of diff apply to which thinking tokens. The prompt and the output are necessary, but there's no mapping between the final diff and the stream of tokens that came out of the LLM (especially in a commit). But that information is known by the tooling already! When generating the diff, the LLM had to output code changes. So you can map those changes to where they originated from. It's not just "what did I tell the LLM to get this change" it's "what was the thought process that the LLM went through after getting my prompt to end up with this line change"
Re: Cursor 1.0
#474Have they managed to fix the bug where applying changes to a file moves the file to the first in your list of open files? And even pinning it if you have other files pinned? Overall, while I've liked using Cursor, it has many bugs like this that I haven't experienced in other VSCode forks and makes me wonder what they consider to be 1.0 quality.
Been using Cursor on Linux and Windows for 2 months and I've never seen this bug
Re: Cursor 1.0
#475Earlier quoted context omitted.
Note: the text of that article itself is AI generated. > Automate Content: Like this very post. I use Wispr Flow to talk with Claude, explain the topic and tell it to read my past blog posts to write in my style.
Now I have the mental image of the owner of that blog tearing his hair out trying to get back into his computer, while the AI that locked him out is happily posting on his blog trying to convince other gullible humans to hand over control of their computers.
[deleted]
Re: Cursor 1.0
#476I've only tried Cursor superficially for 10 minutes. I admit I've kept my head in the sand during this AI boom for the most part. I'm curious from people in this thread:
* Are you using Cursor as your main editor?
* For more senior engineers -- is it really that much of a productivity boost?
* Is the primary use of an AI editor like Cursor to handle more tedious tasks? Ex: generate an array with all the months, write some unit tests for me for some simple component, write some boilerplate code for me, etc.
Re: Cursor 1.0
#477Earlier quoted context omitted.
I believe Copilot Agent isn't yet generally available outside of GitHub (the website)? Also, Copilot's paid version is free for developers of popular FOSS projects.
I use gh copilot at work, so the enterprise version I guess, and it has agent mode in vs code with various models to select from.
You're right. Agent mode with select models (no o3 or Opus unfortunately) is available to Copilot Pro users (also provided for free to eligible FOSS developers) on latest VSCode (I hadn't updated it in over 5 months). Per docs, the newly announced Coding Agent (available on the website only) however isn't. And this was the source of my confusion.
https://docs.github.com/en/copilot/about-github-copilot/plan... / https://archive.vn/HxHzc
Re: Cursor 1.0
#478Earlier quoted context omitted.
I just run two IDEs. Cursor is essentially only the wrapper for running agents. I still do my heavy lifting in Jetbrains products. It actually works out well because I can let Cursor iterate on a task while I review/tweak code.
Same here, everyday coding in Webstorm, Oh I have a task I can offload to copilot, I open VSCode and let a Github CoPilot Agent do that. Knowing what tools are better for what really helps.
have you tried the CoPilot agent tab in Github copilot chat in Webstorm? I wonder if/why you find using it through VSCode better in any way then using it directly in WebStorm.
Re: Cursor 1.0
#479Earlier quoted context omitted.
Have you tried the Jetbrains agent, I think it’s called Jennie? I am trying it right now and it seems decent enough but I haven’t tried Cursor as I don’t really like vs code.
I tried previous iterations of JetBrain's AI without much love, but need to look at Junie. Using Windsurf plugins in JB ides has been working for me, albeit not as powerful yet as the Windsurf VS Code fork.
have you compared Windsurf (previously codeium, had to look it up) to Github Copilot agent or ChatGPT? I'm mostly still using ChatGPT's App integration. It can see my currently open files in webstorm and can directly suggest and apply changes from the app. And I find the suggestions better then JetBrain's AI integrations. But curious about Windsurf / CoPilot Agent
Re: Cursor 1.0
#480Earlier quoted context omitted.
The other day, I was repairing a raidz2 cluster. Power instability during a heavy / long term write operation caused problems resembling defective drives and corrupted metadata all over the drives. I came up with a strategy to repair it but I needed some code which was pretty straightforward. Rust is easier for me than shell scripting so I started writing what I needed and remembered Zed added agent mode. I decided t…
Yeah, I’m impressed with it too. Sure there are things that can still be improved, especially the tab completion, but I’m very happy with how well agent mode works over all! As an aside: $11 for an hour of Claude 4 seems expensive? I’ve been using Claude 4 (through a Zed Pro subscription, not with my own keys) and I haven’t hit the subscription limits yet. Were you using burn mode, or?
The cost came from the context size and repeated queries without changing context. It adds up fast.
Using my own API tokens is effectively equivalent to "burn mode" when using Zed's subscription model.
At the current pricing, I value my time more than these costs and maintaining context can save a lot of time as opposed to maximizing context vs cost.