Agent issue <no message> and “Model provided invalid arguments to read file tool"

Today I encountered issue multiple times while the agent was executing tasks, even after reverting to re-execute. This led me no clue on what the agents are doing, which made it hard to trace back activities. Additionally, there were several messages, such as “Model provided invalid arguments to read file tool." While I’m not sure if this is a direct consequence of the error, the result provided from the agent seemed not as good.

Please add the following info to help us diagnose your issue:

:white_check_mark: Saw this has been posted before but didn’t see an update on solution
:lady_beetle: The agent just printed and “Model provided invalid arguments to read file tool." while executing the work
:counterclockwise_arrows_button: Input prompt, choose Claude Sonnet 3.7 thinking, hit Enter
:camera: Attached are screenshots.



:laptop: OS sonoma 14.1 and your Cursor version 0.49.6
:prohibited: Probably…

3 Likes

Absolutely I’ve been working on the same project for about 2 weeks now, I would say about 30% of my day look at the other screen is what you showed on your screenshots.

I’m thinking it might be due to lag or the maximum amount of files, I tried restarting Cursor and starting new chats, but its very anecdotal evidence here I’m really not sure.

Furthermore, I don’t know if it does it to you, but after the 25 messages, more often than not, the “resume” button won’t work, gives you a timeout error. I don’t know if its related, but usually happens all around the same time.

Please share request IDs of conversations where this happens!

This one is a good example of degradation.

1bc72754-a0e4-48d1-b000-c3bae540e771

I will share more real soon when it start giving the one (if OP doesnt share it first.)

2 Likes

request ID: 5870bd93-ea0a-4fe9-9681-43f980dc0d46

so happy I can finally commented haha

@NiwatiX how’d you fix the issue? start new convo???

for more context: it seems the issue only happened to Claude 3.7 both with & without thinking. however it didn’t happen with other models, ie: Claude 3.5 or Gemini 2.5, whose result isn’t as good compared to Claude 3.7 when it properly functions.

Also in case you’re not aware, seems my post has been mistakenly marked as spam :sweat_smile: @dcastl

You both might be in privacy mode so I’m not able to look at the requests! Could you disable, reproduce the issue, and then send the new request IDs?

@dcastl this might be a silly question to ask, but how do i know if i’m in privacy mode? and how to disable it?

In Cursor Settings, on the very first screen, there should be more info!

@dcastl now cursor just hid all the messages related to changes instead of showing < no message > - This is still challenging for me to understand what it’s changed. regarding “Model provided invalid arguments to read file tool error”, same as before. The result generated didn’t seem to follow through my prompt - perhaps you can look into it & give some suggestions?

Request ID: 298d346c-ac08-4543-9003-67f37b8ab4fd

Images attached



yello? test test @dcastl are you still following thru?

Seeing some issues with our read tool prompt in your example, looking into it!

As for “cursor just hid all the messages related to changes”, in general we never expect to see < no message > when the model decides not to talk, we should just not see anything! So the “no message” behavior is actually pretty strange and would be great to get a repro.

@castl trying to reproduce the < no message > bug…

do remind me to ask for a refund of the requests thrown to cursor :slight_smile:

yo @dcastl encountered < no message > error today, ID: 3d413a6b-ecd6-4b4c-b9a7-e4fc72774c91

what I did: input prompt, chose agent/ Claude 3.7 thinking

same issue here, chat ID: 2ee58b94-726c-4034-b9bf-c2711f06796f

1 Like

understand that the team are very packed but would highly appreciate a solution here since the issue still persists on my end, Dylan @dcastl!

attached screenshot & ID request today: Request ID: e4b1471c-d254-4f28-a6f9-63165f699c4c (there were 2 other issues happened in this request- 1) cursor got stuck in terminal command for hours and 2) cursor stopped running the request after I skipped terminal command)