I hadn’t seen this. Any news on this? Was it really done or was it done and we didn’t notice?
you are using claude-3-5-sonnet-20241022. You need to change to normal claude3.5-sonnet than agent should work perfect.
Why not allow users to test the version as a beta and gather feedback? I am unable to comprehend the selection process. It is particularly frustrating for individuals who intend to test the version but are not overly concerned about potential disruptions.
3 Likes
0.46 is promising. Looks like the difficulties with current file paths with Monorepo have reduced a lot, even though they have not fully disappeared.
Is there a note on release notes for the new version? There aint any right now.
0.46 has not worked well for me. It sets the PYTHONHOME environment variable, and furthermore sets it to a crazy value in my /tmp/ directory. This makes Python and Cursor unusable because Pylance errors every import.
I don’t know if it is related, but when I downgraded back to 45.11 I am getting “Stopped” for everything in Composer. Right now Cursor is unusable here.
2 Likes
whats the issue?
Cursor install is completely broken for me on Windows 11:
-
App exits on attempt to update it from within Cursor
-
“Windows cannot find Cursor.exe” displayed when I try to launch it or install it
-
During installation, installer shows error that “Cursor process is already running” (it is not - according to Task Manager)
-
I’ve already tried to download, install, uninstall and reinstall version 0.45.14 many times and it’■■■■■ or miss. The only reliable way to get Cursor to work is to uninstall it from WIndows Applications panel, then restart the system. Of course that only kinda works until Cursor is closed.
-
I also noticed that Composer window doesn’t accept any text typed via keyboard.
TL;DR - looks like completely broken beta.
The most important issue for me is fixing the continual oom crashes that happen. I know there’s been a lot of talk about it in the forum but there seems to be no solution. Even the talk of it being an extension but once again there is no mention of what extension it could be. Even when cursor is open for a short time with no activity from me, it’ll just crash.
This can be a great tool and I like using it a lot but very frustrating.
And it just happened again while writing this.
I hope the MCP invocation gets fixed - I’ve been tearing my hair out for days. The IDE spawns a copy of my stdio server 3 times, sends the correct capabilities intro to all of those, then does nothing else but report an error.
please at least add a link someplace to there pointing us at all the doc a developer would need to know to write a server! Including what you’re doing to call it, how to enter windows paths, etc etc. Not everyone uses “node” etc.
Seconding this issue—the environment in Cursor also includes some environment variables that break code that uses gstreamer.
2 Likes
100% agree. Cursor is taking a beating on x lately. The top guys at the other AI IDEs are all online engaging with their communities. Not only is cursor’s devs absent, their official x account is abysmal with the update cadence. There should be a major post with any release.
1 Like
I just updated, Cursor now keeps crashing on my most recent repo. It keeps giving the following error:
I’m using Cursor on Windows 10, and I’m encountering an issue when using the MCP server. When I add a fetch MCP server and enter the following in the settings:
node C:/Users/Administrator/Documents/Cline/MCP/fetch-mcp/dist/index.js
It runs normally but opens an additional Node window. If I close this window, the MCP stops working, and refreshing doesn’t help. I have to close and reopen Cursor to make the Node window appear again.
However, when I configured this MCP server in Cline, I used the following configuration:
{
“fetch”: {
“command”: “node”,
“args”: [
“d:/ai/cursor/mcp/fetch-mcp-main/dist/index.js”
],
“autoApprove”: [
“fetch_html”,
“fetch_markdown”,
“fetch_txt”,
“fetch_json”
]
}
}
This works normally without showing any window.
Has this issue been resolved in Cursor 0.46?
The issue goes away if I revert to version 0.45
I will just say one thing. I’m liking the direction with new release, it’s got it’s points and errors, duh.
But please don’t waste your talents and waste any time on ■■■■■■■ Grok. It’s dogshit, built by a dogshit ■■■■■■■■ artist. It would really ■■■■ to see valuable time wasted on trying to cater to a subpar pile of trash. These little fanboys can’t tell the difference between a function and a second hole in their ■■■, so please, don’t cater.
Keep up the good work. 
Had anyone experience MCP failing to load since new update?
1 Like
same for me, please explain/fix
Nice design!
My only complaint is that it defaults to Agent when you start a new Chat!
My request is to carry over the mode of the previous Chat!
When I use deepseek-r1 or deepseek-v3, I sometimes use Edit mode because Agent is not supported.