Pre-submit Checks
Describe the bug
I don't know what the bug is.
I was in a conversation on restyling a simple component, and I attached a JPEG for visual guidance. Warp was 'warping' the request and then got the bad request response. Now, EVERY prompt I enter cannot be processed as they all result in Bad Request
To reproduce
Not sure how I got into that state, and now:
- Type ANY prompt
- Warp fails regardless of whether an image is attached or not
Here's the latest conversation ID: {"conversation_id":"4f914d91-abfd-4a12-b952-f3b7c29aa0af"}
Expected behavior
I expected Warp to begin working through tasks designed to restyle code underlying a simple hero component.
Screenshots, videos, and logs
Operating system (OS)
macOS
Operating system and version
15.6.1
Shell Version
zsh 5.9 (arm-apple-darwin23.0.0)
Current Warp version
v0.2025.09.17.08.11.stable_02
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
25-Sep-2025 10:30 am EST
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
Pre-submit Checks
Describe the bug
I don't know what the bug is.
I was in a conversation on restyling a simple component, and I attached a JPEG for visual guidance. Warp was 'warping' the request and then got the bad request response. Now, EVERY prompt I enter cannot be processed as they all result in
Bad RequestTo reproduce
Not sure how I got into that state, and now:
Here's the latest conversation ID: {"conversation_id":"4f914d91-abfd-4a12-b952-f3b7c29aa0af"}
Expected behavior
I expected Warp to begin working through tasks designed to restyle code underlying a simple hero component.
Screenshots, videos, and logs
Operating system (OS)
macOS
Operating system and version
15.6.1
Shell Version
zsh 5.9 (arm-apple-darwin23.0.0)
Current Warp version
v0.2025.09.17.08.11.stable_02
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
25-Sep-2025 10:30 am EST
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