Repository navigation
Web sessions can loop indefinitely when user message IDs are generated on the client #17012
Closed as not planned
Description
Summary
Web sessions can enter an infinite assistant loop after a finished response.
Reproduction
- Run the opencode server on one machine
- Open the web UI from another machine
- Submit a prompt
- Observe that an assistant message finishes with
stop - Observe that the session immediately returns to
busyand creates another assistant message for the same user prompt
Root cause
The web app generates the user messageID in the browser, while assistant message IDs are generated on the server.
SessionPrompt.loop() uses message ID ordering to decide whether the latest finished assistant message belongs to the latest user message:
lastUser.id < lastAssistant.idThat ordering is not reliable across machines. The correct relationship is lastAssistant.parentID === lastUser.id.
Impact
- repeated assistant messages for the same user prompt
- hidden context growth
- increasingly strange follow-up outputs
- sessions appearing stuck in
busy
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Mar 11, 2026
This issue might be a duplicate of existing issues. Please check:
lastUser.id < lastAssistant.idloop exit condition, causing infinite assistant response generation. That issue also identifies theparentIDrelationship as the correct fix.Please review #11863 in particular, as it describes the identical root cause and symptoms.
fix: prevent web ui session loop by removing client-side message id g…
github-actions commentedon Jul 4, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.