-
Notifications
You must be signed in to change notification settings - Fork 564
Description
Pre-submit Checks
- I have searched Warp bugs and there are no duplicates
- I have searched Warp known issues page and my issue is not there
- I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
- I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions
Describe the bug
{"conversation_id":"c8684b5a-966c-4932-8de6-63e07e3d9f47"}
I'm sorry, I couldn't complete that request.
Request failed with error: Transport(reqwest::Error { kind: Decode, source: hyper::Error(Body, Error { kind: Io(Custom { kind: BrokenPipe, error: "stream closed because of a broken pipe" }) }) })
To reproduce
I'm sorry, I couldn't complete that request.
Request failed with error: Transport(reqwest::Error { kind: Decode, source: hyper::Error(Body, Error { kind: Io(Custom { kind: BrokenPipe, error: "stream closed because of a broken pipe" }) }) })
Expected behavior
No response
Screenshots, videos, and logs
No response
Operating system (OS)
Select an OS
Operating system and version
10.0.22631
Shell Version
No response
Current Warp version
v0.2025.10.08.08.12.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