Having the same issue.
”The JS/TS language service immediately crashed 5 times. The service will not be restarted.”
cmd + click doesn’t work after update
Element inspection using the built-in Browser Tab does not work (Windows atleast). When clicking the “Select Element” it just focus on the chat and nothing happens…
I might be crazy, but is there still the nice gauge graph showing current context used/left in Cursor 2.0? Where did it go?
I only see this now:
I was testing out the new multiple models feature with Sonnet 4.5 thinking, GPT-5 and Composer 1. Composer wrote everything in Chinese! I can’t understand anything! LMAO
1 Like
@PerkyZZ Composer pricing is available at Models | Cursor Docs and more info about Composer is at Composer: Building a fast frontier model with RL · Cursor
@webdo will check with team.
@matgenehr @jgilfoil submitting prompt to x Agents can get to different results, same as when running the same prompt with one agent multiple times may have different outcome. The agents use Worktrees that are independent work areas from each other and at end you can pick which output you prefer.
@zayadur checking with team about generate Cursor rules.
@alagunto please post a full separate Bug Report with more info for Worktrees issues Create Bug Report
I suggest also Feature Request for features you are missing.
@merlin.audio you likely tried the Agent view onboarding , can be switched at top left from Agent to Editor view. @jrista has a good suggestion with /web
@QTom any issues with 2.0? Primary side bar in which view?
@Shayan-Khan likely due to Agent using more features that benefit from multi models than Ask.
@Tomer_ke @wenli could you post a full Bug Report so we can check what goes wrong Create Bug Report
1 Like
just did it :]
1 Like
Looking for this too. The base models are only knowledgable of the old .cursorrules format and so they have no way of understanding the modern format that’s been around for months at this point.
A major release, but still stuck on VSCode 1.99.3 which is over 6 months old? Why?
2 Likes
Great work Team, bold play!
Composer-1 actually cracked an issue I’d been going around with in circles on with GPT5 Codex High/Sonnet 4.5 in one-shot. Definitely a noticeable step-up from my results with Cheetah. That surprised me and I’m keen to see this model continue to develop, especially as the workhorse which coordinates with other models to play on their strengths. As an Ultra user, this is a reason to stay subscribed. It’s unlikely I will break with my Codex/Gemini/Claude plans, so having Cursor act as the coordinator between all three on their IDE/terminal extensions would be great to see also. Though I know that doesn’t exactly match your business model.
Everything is converging in this direction, so I doubt this is a novel idea, but I’d suggest looking at deeper ‘conversations’ during parallel model runs. I’ve run many experiments with asynchronous builds using Claude Code to rapidly prototype complex end-to-end features (i.e. 8 agents building 20k lines of code in parallel with UI, engines, persistence etc). It’s getting very close to viable, but even heavily modularised with tight instructions, each subagent will make errant assumptions about what each other’s components contain.
If there was a ‘conversation’ API between models that are working concurrently on large features with ‘check with this model’ gates which holds the model (or placeholders that portion of the code) until it gets an answer, i.e. ‘wait for model B to give you the actual API points / format before completing this section’, that would be a game changer. Models could send requests with priorities, with each maintaining a queue that it works through. I’m just describing how a team of developers might work 
I do have an even better solution to the left hand not knowing what the right is doing, but I may want to try build it myself
Really pleased to see native voice, I was getting RSI for the first time in my life working full-time with agents and Mac’s Voice Control was shoddy. Early days of testing, but already I can tell your integrated feature is much better. This would be great if we could apply it across the program i.e. in terminal windows and extensions! Also, not sure if this is user-error, but if we could append with voice, that would be helpful. I’ll often pause to copy in directories, files and so forth, and being able to resume the voice prompt would be perfect.
Great product and impressive model, keep at it!
Best
Plight
2 Likes
When using Agent Layout: failed to “Move Primary Side Bar Left.”
My preference is for it to be on the left, especially since I use multiple IDEs simultaneously. If it were on the right, I wouldn’t be able to adapt—and would end up never using Agent Layout at all.
I wanted to use Agent Layout, but the issue with the Primary Side Bar is preventing me from proceeding. This wasn’t the case in version 1.7, though the database had problems in that version.
2 Likes
The new agent-based workflow and layout in Cursor 2.0 has removed many of the unique advantages that Cursor used to have. The agent model makes the user experience much less intuitive and takes away the simplicity and control that were the main strengths of Cursor as a code editor. It feels like the UX is getting in the way rather than helping with productivity.
6 Likes
How do I revert from this? The chat window is refusing to stay sized to what I want - every time a new line prints it dramatically moves from the side bar I put it in to take up all the central space like some kind of “look at me” princess. I don’t care about the chat output, I care about the terminal I have open that I want to stay taking up most of the space.
2 Likes
Version: 2.0.39
VSCode Version: 1.99.3
Commit: 9c66477db9d55302dfb45aacbd0194603a94ed80
Date: 2025-10-30T01:39:26.854Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0
After updating to 2.0, I thought I could still use it under Editor, but the new version ended up looking like this—forcing me to leave Cursor behind.
All extensions are completely unavailable for selection.
I can’t see a way to cycle through individual changes? I have to scroll in review mode? This was the best feature - the alt+J / alt+L allows you to see all changes quickly. Now I what, have to scroll the entire files with changes? I’ll literally just use Claude Code instead?
2 Likes
You don’t live in South East Asia do you? Every time I open the changelog or documentation or some other pages, it defaults to Chinese which I cannot read either. I reported it twice including as a bug report months ago, but still not fixed.
Workbench>Activity Bar: Orientation vertical faild
Version: 2.0.39
VSCode Version: 1.99.3
Commit: 9c66477db9d55302dfb45aacbd0194603a94ed80
Date: 2025-10-30T01:39:26.854Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0
This problem has reappeared, and it’s even more serious now.