"Edit invalid arguments" persistent error

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Composer fails to write to files during content generation, causing loss of generated content and wasted credits. The issue is not marked as errored in the billing section.
All the time I have “Edit invalid arguments”

Steps to Reproduce

Use Composer to generate content.
Observe that some content is not written to files.
(Check billing section – errors are not reflected there.)

Expected Behavior

All generated content should be saved to files correctly, and any failed write attempts should be marked as errors in the billing section.

Screenshots / Screen Recordings

Operating System

Windows 10/11
MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.50 (user setup)
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Composer 1

For AI issues: add Request ID with privacy disabled

ba212916-0ffa-41fa-954e-c6bb20b9e907

Additional Information

I think I’ve lost already at least 20% of my monthly credits because of this issue as the content is always generated but not written into the file due to this persistent issue.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hi Giles,

I looked into your request ID (ba212916-0ffa-41fa-954e-c6bb20b9e907) and it appears to have originated from a Nightly build of Cursor (2.2.0-pre.23.patch.0). Nightly builds can be unstable.

Could you confirm whether this issue persists on either the latest nightly build, or the current stable version (2.1.50)?

Hello,

Do you mean nightly build of Composer or Cursor IDE? If it’s Cursor, I am not participating in any “Nightly build” or “Early Access” program so this cannot be the case, right?

I still have the issue unfortunately.

I’m facing probably the same issue today. I searched the Internet and found this thread.

My case is it only failed when I’m using a multi-root workspace with multiple projects. More specifically, I also created a git worktree for one of the repos and added to the workspace, not sure if it’s relevant. And in this case, all models (Opus 4.5, Sonnet 4.5, GPT 5.1 Codex Max, GPT 5.2, Composer, Auto, etc.) failed to edit showing “invalid argument" (the same as the screenshot provided by Gilles). Some models might raise an error like “relative path is expected”, which seems like Cursor (or the model with prompts) is providing a wrong path to the edit tool that it couldn’t handle.

Request IDs:

  • 95e53ddc-1e5a-4262-a1aa-5dc6ab5e7b31
  • 57a6e6d1-6f43-44c5-a3ce-a3eaa1448984
  • 2eb9ee77-8b92-4fca-8f03-e48a881ffa8d
  • 534e2e77-edd7-4b29-8401-4825aa2594d7
  • f19e2f6a-85af-4502-bc44-222268df3ef6

Current Cursor Version

Version: 2.2.17 (user setup)
VSCode Version: 1.105.1
Commit: cf858ca030e9c9a99ea444ec6efcbcfc40bfda70
Date: 2025-12-11T18:30:06.649Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.22631

Note that this is a stable version. I’m not participating in Nightly build or Early Access program either. If I’m indeed participating from your perspective, that means the release channel is wrong and releases incorrect version to me.

This is stopping me from using Cursor because it literally does not work, failed to do any edits. It still worked yesterday before I upgraded Cursor to the latest version.

1 Like

It seems that upgrading to the latest version just released fixes it for me.

Current Cursor Version

Version: 2.2.20 (user setup)
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.22631

1 Like

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.