New request
#2734: automatic compression strangely triggered
We'll provision a sandbox, run an agent against the issue, and open a draft PR. You can pull the branch and iterate from there.
Issue
bugneedinfostreaming
i did the compression manually，then continue the chat，the automatic compression suddenly showed up，but the chat continues，the automatic compression ends after the next agent reply。and my last message was copied to the end
<img width="856" height="773" alt="Image" src="https://github.com/user-attachments/assets/f22ce4cc-52c8-4c2b-9631-a7a87927f1e0" /> <img width="811" height="432" alt="Image" src="https://github.com/user-attachments/assets/56cfba4a-d683-4a31-a9d3-98f3947e952c" /> <img width="799" height="393" alt="Image" src="https://github.com/user-attachments/assets/15ec0b52-5212-4d0a-ba96-a0ceaf227088" />Assessmentadvisory
bug●● medium75% confidence
Unexpected auto-compression timing and duplicated message rendering point to a streaming-state bug around the compression boundary in both frontend and backend.
Likely files
- static/streaming.js
- static/chat.js
- api/compression.py
- api/session.py
- api/routes.py
Create the request