We’ve been testing it and it will be released soon; no Cursor update will be required.
7 Likes
Now that v1.6 is available on the main/official release channel, when can we expect a changelog including all of the changes released? This changelog really should be posted before, or at the very least concurrently to, new releases on the main non-early-access channel.
1 Like
Completely agree and understand - we release the changelog when it becomes GA; 1.6 is rolling out but not available to all users yet (expecting this EOD)
1 Like
Could you please unf*ck the stupid release process, and also make auto-update bearable?
Cursor should get mature.
3 Likes
What are your biggest issues with the release process? Also, you’ll see way more frequent updates if you’re on nightly. If your personality is not suited to daily updates, I’d recommend staying on the stable track from settings → beta.
2 Likes
This has been said many many times but I think the main complaint is the lack of changelog for pre-release versions making it very hard for us to know what we are supposed to test. Changelogs should be provided when pre-release hits and evolve with it as patches go. I’m not saying we need changelog for every little patch, just a general idea of what to look for would be nice, it would allow us to test what actually matters instead of just posting reports about unrelated bugs in threads like this.
9 Likes
I agree with that! We’re going to move to this system
4 Likes
MCP suggestion is annoying, appears too often (on every Sentry-related URL paste, when URLs are different) and blocks whole window from interaction.
Not even mentioning I have Sentry installed, just behind the MCP proxy.
Example of URLs:
1. https://example-org.sentry.io/issues/ABC123DEF456/?project=7890123&query=is%3Aunresolved&referrer=issue-stream
2. https://example-org.sentry.io/issues/ABC123DEF456/?project=7890124&query=is%3Aunresolved&referrer=issue-stream
1 Like
Got it - will share this! Curious if the Sentry MCP would be useful if you are pasting sentry URLS?
Of course it useful, it can extract everything i need to fetch actual issue details into the chat context.
But the problem is I already have it installed behind the MCP proxy, so I don’t need it to be installed directly (and I am unable to prevent this pop-up from appearing & blocking the editor behind additional click)
MCP proxy allows me to have everything in one place, preserving tools limit. Also single MCP entrypoint for multiple IDEs is more convenient IMO (personally I use mcpproxy.app, but i saw the other proxy solutions exist too)
Also in the notification “New update is available” should be “New update 1.6.23 is available”, so the user knows if its a patch or a major update. I always click Help - About after an update to know the exact version I’m updated on.
3 Likes
Did you remove “ask” mode altogether? I only have agent and background in chat after updating…
Version: 1.6.23 (user setup)
VSCode Version: 1.99.3
Commit: 9b5f3f4f2368631e3455d37672ca61b6dce85430
Date: 2025-09-15T21:49:07.231Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100
I tried adding ask mode in some capacity back, and it just ignored disabled edits and edited the file anyway 
2 Likes
Bug Report
Problem
Chat cannot run in terminal my custom aliases, commands, etc., because they are defined in ~/.bashrc and the Chat runs non-interactive shell (probably) which loads just the ~/.profile. It used to work around version 1.6.21, but now it doesn’t.
Also the cmds the AI runs in chat are in / (the root dir of the filesystem), not in my project root as it used to be.
I Tried
I tried source ~/.bashrc with no success, because if it’s non-interactive shell, then the instructions in .bashrc are ignored as written in the default code of .bashrc itself.
I made the agent run “whoami” and it properly returned my username.
Version
Version: 1.6.23
VSCode Version: 1.99.3
Commit: 9b5f3f4f2368631e3455d37672ca61b6dce85430
Date: 2025-09-15T21:49:07.231Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Linux x64 6.1.0-39-amd64
Why Is It Important
I have in .bashrc:
export PATH="${ASDF_DATA_DIR:-$HOME/.asdf}/shims:$HOME/.local/bin:$PATH"
. <(asdf completion bash)
eval "$(~/.rbenv/bin/rbenv init - --no-rehash bash)"
Without that I cannot run any dev related comands like compile, test, run server, etc.
1 Like
Anyone having issue with Ask mode, this should be soon resolved.
@theio make sure you have not added it on your own.
1 Like
No release notes in time.
Most stuff undocumented for months.
Update UX in cursor is bad, and most of the time not working (Windsurf does that well).
Stable is good for me, since I want to work.
Thanks @andrewh !
1 Like
1.6 Release is out with a changelog. Please continue there as its now the featured post.
I will close this thread so all communication is in the same new thread.
For issues please post a full Bug Reports with detailed info Create Bug Report
4 Likes