-
The command “ask” UX flow seems fixed. Thank you! For a few versions it would steal focus and I would send a command while typing by accident. Now I can once again click in the prompt box and type and interrupt the shell question by sending without taking my hands from the keyboard.
-
Can not repro shell tool read-only: I can still edit the content of the shell tool still, though sometimes the agent uses a bash tool instead of the shell tool (not a new thing)
2 Likes
The DoneBell seems to work consistently since 1.5.11 Thanks, pretty important on parallel agents.
(Notifications work. Event counter badge stays at 1, some popups, no audio (may interfer with main Bell?).)
2 Likes
Note, oslook is a few versions behind - it currently shows 1.6.6, but the latest update is 1.6.11:
2 Likes
Read only shell is intentional. It leads to much higher reliability with terminal in agent.
Is the constant freezing on windows fixed? Otherwise its unusable and we’re stuck on some ancient version.
What freezing have you been seeing? Are you using the new Agent Window?
Okay so I am having the worst day of my life using Cursor. the agent assumes the open file is the context when I start a new chat and is making horrific decisions based on said fact. for tiny fixes I used to just start a new chat and return to what I was previously doing but now that’s impossible. It just made like 200 edits to the wrong file even after screenshot, and proper textual context was provided. This is a massive issue that is significantly hindering to the workflow, and it is costing me money everytime I do not notice it is happening. anyone else??
Hey - no changes here on the latest update. Cursor gives the current tab as context. You can remove it and also disable this behavior.
Could you try again on 1.6.14? We think it’s resolved
1 Like
I am also noticing freezing/hanging of all Cursor windows when navigating to the Cursor settings page as well as when opening the new Agent Window.
1 Like
Thank you! We have been dealing with remote SSH performance issues for a long time with Cursor while working in JS/TS projects, especially noticeable in large monorepos.
1 Like
I am noticing major freezing/stuttering while using the editor like normal, during these freezes/stutters the cursor process CPU usage climbs quite high, and after a few seconds returns to normal and I can edit again. This happens every few seconds while editing, scrolling around, clicking on things, nearly every action causes this behavior.
Version: 1.6.14
VSCode Version: 1.99.3
Commit: 64b72c9cd7e38203078327f881d5fe74930b2600
Date: 2025-09-11T21:42:07.958Z
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.12.46-1-lts
1 Like
We’ve been seeing some bad performance degradations with Agent Windows - is it possible that is related? We’re actively working on it, but note that Agent Window is still in an early beta (see settings → beta)
current tab was not added as context in the chat where it occurred, where do I disable this behavior?
1 Like
The copilot-instructions.md generated by GitHub Copilot Generate Instructions is far superior in quality to Cursor /Generate Cursor Rules — hope Cursor can implement optimizations to match.
1 Like
Could you share more info on what was high or low quality?
GitHub Copilot Generate Instructions : more like specification
Cursor /Generate Cursor Rules : Overly focused on details (getting stuck in frequent content changes)
1 Like
Thank you
Cursor v1.6.6 stopped automatically before finishing the todos, gpt-5-high-fast