warp reporting error message from claude
Pre-submit Checks
- [x] I have searched Warp bugs and there are no duplicates
- [x] I have searched Warp known issues page and my issue is not there
- [x] I have included the logs (optional, but helps expedite the bug fix). Log gathering intructions
Describe the bug
I'm getting this error repeatedly for any complex request.
Internal server error occurred: Anthropic API error: POST "https://api.anthropic.com/v1/messages": 400 Bad Request {"type":"error","error":{"type":"invalid_request_error","message":"messages: text content blocks must be non-empty"}}
To reproduce
please generate separate tests for each header that actually test the functions that each header implements. These should be well thought out tests. You have already done this in the "New_Python directory in Python" I want you to write good tests in C++ for the .h files. You should read each .h file, work out what it is doing and then generate a good test for the functions that it implements. You should then compile the test and make sure it works. You should do this for each of the .h files.
Expected behavior
I expected the model to begin work on the tasks. (as it has in the past)
Screenshots, videos, and logs
No response
Operating system (OS)
Select an OS
Operating system and version
15.2.0
Shell Version
No response
Current Warp version
v0.2025.04.02.08.11.stable_03
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
No
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None
This is block the complex workflows that have been working for the last few weeks. I updates Warp this morning. this is on a macOS etc.
I am having the exact same problem. But different system unfortunately I'm stuck at windows 11 with wsl2.
Does this block you from using Warp daily? Yes a bit
Same problem here on MacOS. It happened after the update to the newest version (v0.2025.06.04.08.11.stable_03) . It works a bit and the gets this error message and is not able to recover from it.
Closing the terminal and restarting over by copying the text of the previous window into the AI worked to a certain degree. I needed to do this twice. So currently it seems to be more stable again.