Repository navigation
[Bug] Long conversations get stuck indefinitely / no response. #1202
Description
What's wrong? Maybe some steps to reproduce.
Everything was working pretty well initially, but once conversations become longer, I can no longer continue chatting reliably.
At some point:
- the response keeps spinning forever, or
- the generation stops without returning any response.
What I tried
- Reinstalled OpenChamber
- Downgraded OpenChamber to older versions
The issue still persists.
Expected behavior
The conversation should continue generating responses normally even with longer chat histories.
Actual behavior
Long conversations eventually become unusable:
- infinite loading/spinning
- no response returned
- generation silently stops
- can continue chatting to the session using opencode TUI
Environment
- OpenChamber
- OpenCode
- Issue appears after conversations grow in length/history
OpenCode version
1.14.44
Steps to reproduce
- Start a normal conversation using OpenChamber with OpenCode
- Continue chatting until the conversation history becomes relatively long
- Send another message
- Observe the behavior:
- the loader keeps spinning forever, or
- the request stops without any response being generated
Notes
- The issue does not seem to happen on short conversations
- Reinstalling OpenChamber did not fix the issue
- Downgrading OpenChamber versions also did not fix the issue
Operating System
AlmaLinux 8
Where does it happen?
Not sure
Version (if known)
No response
Screenshots / recordings (optional)
No response
Logs (optional)
Reacted by Rana Ahmed
Activity
Silvenga commentedon May 10, 2026
Also saw this, getting a 400 on the message endpoint after < 30ms, no logs.
The fetching the messages immediately fails, and the UI stays in a loading state. This only happens with long conversations.
Silvenga commentedon May 10, 2026
I've read the code now 😆
The session/{session}/message endpoint is handled by OpenCode - OpenCode has had a few changes to that endpoint in the past couple days - didn't see anything that was explicitly a bug fix, but upgrading to latest appears to resolve this issue.
So tldr @procodingtools - try at least version v1.14.46 of OpenCode.
procodingtools commentedon May 10, 2026
@Silvenga Thanks i'll try that
sudokar commentedon May 11, 2026
Thanks @Silvenga . I am on
1.14.48and the issue reported by @procodingtools is still happeningrekram1-node commentedon May 13, 2026
can someone send a session they encounter the error on?
run
opencode export > session.jsonsudokar commentedon May 17, 2026
Hey @rekram1-node , As the opencode process is namaged by openchamber to start/stop, Is running
opencode exportis fine to get the export you are looking for? If yes, then I am happy to get that.blain3white commentedon Jun 9, 2026
I'm the maintainer of Clean My Agent. It focuses on local AI coding-agent session scanning, backup, cleanup, and export, so it may be a useful reference for this thread: https://github.com/blain3white/clean-my-agent
yulia-ivashko commentedon Sep 15, 2026
The thread traces the failure to OpenCode's session-message endpoint returning HTTP 400 for long histories. That endpoint and its stored-session handling belong to OpenCode; a related investigation is anomalyco/opencode#27319. Closing as not planned here without claiming the upstream defect is fixed. Thanks for narrowing the failure to the request and comparing OpenCode versions.