"broken pipe" transport errors during operations

[jacksonkasi1]

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 included the logs (optional, but helps expedite the bug fix). Log gathering intructions

Describe the bug

Warp's AI Agent Mode frequently fails with transport layer errors showing "stream closed because of a broken pipe". This occurs across various operations including Git workflows, code generation, and general AI assistance. The error appears intermittently - sometimes happening frequently, other times working normally. The full error message is:

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" }) }) })

This affects the overall reliability of AI Agent Mode functionality.

To reproduce

Steps to reproduce:

1. Open Warp terminal and navigate to any project directory
2. Run git status or any command that shows changes
3. Use AI Agent Mode by typing a natural language request (e.g., "add proper git commit msg & push it")
4. Wait for AI Agent to process the request
5. Error occurs intermittently - sometimes immediately, sometimes after partial processing

The issue is not consistently reproducible but occurs frequently enough to impact daily workflow.

Expected behavior

AI Agent Mode should successfully process requests and complete operations without transport layer failures. The connection to Warp's AI service should remain stable throughout the interaction, providing consistent and reliable AI assistance.

Screenshots, videos, and logs

warp-logs.zip

Operating system (OS)

Select an OS

Operating system and version

10.0.26100

Shell Version

GNU bash, version 5.2.15(1)-release (x86_64-pc-linux-gnu)

Current Warp version

v0.2025.06.25.08.12.stable_02

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

This is a widespread issue affecting AI Agent Mode reliability across different types of operations:

• Git workflow assistance
• Code generation and refactoring
• General terminal command assistance
• File operations

The intermittent nature ("sometimes often, sometimes normal") suggests network connectivity or server-side resource management issues. The error occurs at the transport layer, indicating connection drops between the client and Warp's AI service infrastructure.

This impacts productivity as users cannot rely on AI Agent Mode for consistent assistance and must frequently retry operations or fall back to manual commands.

Does this block you from using Warp daily?

Yes

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

[petercrabtree]

I have the same issue, on both Windows and MacOS over the last couple of days.

[yosheng]

I'm also experiencing the same issue. I'm on Windows, but my friend using macOS encounters the same error. I have to keep telling the AI to continue, though it still works (with manual intervention).

[dworl]

I see this issue as well. It is intermittent but happens often enough to be disruptive.

[caijunxian-core]

i want to know how to fix, and the issue is open in long time. the problem is effect me work

[aherreDev]

i want to know how to fix, and the issue is open in long time. the problem is effect me work

Me too, it basically stops us from using the conversations or the agent mode (One of the main features I subscribed for)

[lucainkwell]

me too

[RasberryKai]

Same here

[sunp8741]

Until today on September 1st, the same problem still arises

[david0723]

Happened to me numerous times today

[rbugajewski]

Every time you try to scaffold a project or create a slightly more sophisticated plan, there’s a very high chance you’ll run into this. Sometimes you can recover by manually intervening, but often the prompt just gets stuck.

[gpboyer1]

Yes, I have the same problem.
I also found that others have similar problems:

• BrokenPipe -> Stream Closed #7352