warpdotdev
Request failed with 403, "<!doctype error
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 an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID intructions
- [x] I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log intructions
Describe the bug
I had asked the AI agent to analyze performance test shared by customer and it kept returning the same error repeatedly. This has happened in the past as well, so I thought to raise it with relevant team. I'm sorry, I couldn't complete that request.
Request failed with error: ErrorStatus(403, "<!doctype html><meta charset="utf-8"><meta name=viewport content="width=device-width, initial-scale=1">
OS - Windows 11 Enterprise Build Id - 10.0.22631 Build 22631 Debugging Id - {"conversation_id":"e482fa1a-a31f-4477-a45f-9d7ce3056751"}
To reproduce
The issue is intermittent, but the only thing I did was to ask the AI Agent to analyze the performance logs, the contents of the logs folder are jmeter.log - 1627 KB *result-3.txt - 67922 KB *new-.result-3.txt - 109363 KB
Expected behavior
No response
Screenshots, videos, and logs
Operating system (OS)
Windows
Operating system and version
Windows 11 Enterprise Build Id - 10.0.22631 Build 22631
Shell Version
No response
Current Warp version
v0.2025.09.01.20.54.stable_06
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?
Yes, this issue prevents me from using Warp daily.
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
Hey folks, We've been seeing a few reports of this. I've notified the team about it. this is typically due to the Agent Mode request being >50MB. (We're working on improving the error message and changing client behavior so it doesn't send up chunks of data this large.)
We recommend trying to break the files down into smaller ones if possible.
Let us know if it persists and provide the debugging ID. Debugging ID instructions along with the size of the files you're trying to read/edit/upload/work with to the agent.
Getting the same with any model, it seems.
{"conversation_id":"7bd782f5-59f3-49cc-8bb5-467bd1fbb876"}
This happen to me too, and with a new agent it works, so I asked about the problem and this is what said:
"That 403 error you were getting in the other tab sounds like a session or authentication issue that sometimes happens with long-running conversations."
Certainly I was working maybe for weeks with the same agent
Same issue here. I've had an agent open for over a week and I'm now getting 403s.
{"conversation_id":"55a43e78-e6bc-4fa0-bd52-9b603b2f9104"}
same problem: {"conversation_id":"611b6599-8cf7-46ab-95c4-3468f3778863"}
I have experienced this. A cheesy work around seems to be to fork the long task to another convo(tab). Just my 2 cents
