I rolled back to version 2.2.4, which works fine and allows me to edit files. But now version 2.2.4 forces an update and won’t let me use it anymore.Versions 2.3, 2.4, and 2.5 have an issue in SSH mode: the first session works normally, but all subsequent sessions crash.The latest version 2.6 can’t edit files at all and can’t find skills!I can’t use it at all now!
When you say “crash,” does Cursor fully close, or do you get an error popup? If there’s a message, what does it say?
If you’re able to reproduce this, next time it happens, could you grab the logs for us? Open Cursor, hit Ctrl+Shift+P → Developer: Open Logs Folder, then go up one directory, you’ll see folders for each session. Grab the logs from the session that crashed and share them with us. Those would help us a ton. I can also open a private message for you to share those logs!
Could you tell us a bit more about what you’re seeing? Is it that you’re typing in the editor and nothing happens? Is the file opening as read-only? Or is it the AI/Composer that can’t make edits? And is this happening on local files, or only over SSH?
In version 2.6, when editing files with Cursor, it prompts that there are problems with the read and write tools, and files can only be edited using PowerShell commands. Version 2.2.44 works normally.
Both Write and StrReplace tools consistently return Error: Invalid arguments regardless of input parameters. This prevents normal file editing workflow and disables the accept/reject UI for users.
Test Cases
Tool
Path Format
Content Type
Result
Write
D:/Pytest/test_write.txt
Pure ASCII
Error: Invalid arguments
StrReplace
D:\Pytest\...\flash.py
Pure ASCII
Error: Invalid arguments
StrReplace
D:/Pytest/.../flash.py
Pure ASCII
Error: Invalid arguments
StrReplace
English path
Chinese content
Error: Invalid arguments
Working Tools (for comparison)
Shell - Works correctly
Glob - Works correctly
Grep - Works correctly
Read - Returns URI error, but Shell type command works
Environment
OS: Windows 10 (Build 10.0.19044)
Shell: PowerShell
Workspace: D:/Pytest
Path characteristics: Contains mixed separators, deep nesting, Chinese folder names in some paths
Impact
Cannot edit files through standard Cursor tools
No diff generation for user review
Accept/Reject buttons not displayed
Forced to use Shell commands to write files directly, bypassing Cursor’s change tracking system
Workaround Used
Created Python scripts via PowerShell here-strings, then used copy command to overwrite target files. This bypasses Cursor’s file tracking entirely.
Recommendation
Investigate the argument parsing logic in Write and StrReplace tools. The error occurs even with the simplest possible inputs (ASCII-only path and content), suggesting a fundamental issue rather than encoding or path format problems.
I am also having this issue. Connecting with ssh and cursor is really struggling to edit files. Cursor makes a plan in .cursor/plans but then can’t edit it cause it’s not in the workspace??
I tested Remote SSH from Windows to a Linux box and was able to create new files and edit existing ones without issues on the latest version. From your description, I’m not sure if you’re also SSHing into a Linux machine or into a Windows one — could you clarify? Windows SSH targets are less common but could behave differently.
Your initial report mentions crashing after the first SSH session, and your follow-up mentions an “invalid arguments” error — are these the same issue, or two separate problems?
Any additional details that would help me reproduce this? For example:
What OS is the remote machine you’re SSHing into?
Are you using key-based or password auth?
Does the crash happen when reconnecting to the same host, or any new SSH session?
Hello, I’m using Cursor on Windows to SSH remotely into another Windows machine.
I have two separate issues:
In versions 2.3, 2.4, and 2.5, the app crashes after the first SSH session. This is a known bug related to context collection in Cursor’s SSH mode, so I cannot use these three versions.
In the latest version (2.6), I cannot edit files over SSH at all — it shows an “invalid arguments” error.
The problem now is that Cursor forces an update, which prevents me from using version 2.2.44.
As a result:
If I upgrade to 2.3 / 2.4 / 2.5, I get the crash after the first SSH session.
If I upgrade to the latest version, I get the “invalid arguments” error and cannot edit files over SSH.
I am completely unable to use Cursor right now.
Could you please disable forced updates for my account? Thank you!!!
Hello, I’m using Cursor on Windows to SSH remotely into another Windows machine.
I have two separate issues:
In versions 2.3, 2.4, and 2.5, the app crashes after the first SSH session. This is a known bug related to context collection in Cursor’s SSH mode, so I cannot use these three versions.
In the latest version (2.6), I cannot edit files over SSH at all — it shows an “invalid arguments” error.
The problem now is that Cursor forces an update, which prevents me from using version 2.2.44.
As a result:
If I upgrade to 2.3 / 2.4 / 2.5, I get the crash after the first SSH session.
If I upgrade to the latest version, I get the “invalid arguments” error and cannot edit files over SSH.
I am completely unable to use Cursor right now.
Could you please disable forced updates for my account? Thank you!!!~~~