You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Intermittent Bug: After changing the "Follow-up Message Behavior" setting to "Queuing" on the Web interface, messages sent after the model has finished generating its response are temporarily stored in the "Queuing" queue. #18713
I encountered this issue while running opencode serve. Specifically, after changing the "Follow-up Message Behavior" setting to "Queue," I would occasionally trigger a specific bug: the model would have already completed its current task and finished generating its response—and the input box icon would not indicate a paused state—yet if I sent a message, it would automatically be placed into the queue. However, this bug is somewhat difficult to reproduce; I spent most of this morning testing and only encountered it about 2 or 3 times.
Plugins
No plugins were used.
OpenCode version
1.2.27
Steps to reproduce
Used after launching opencode serve.
Set the "Follow-up Message Behavior" to "Queue".
Once the model has finished its current task and completed its response—and provided that the input box is not displaying the "paused" icon—send a message to it.
I encountered this bug before, and the bug keep occur for a specific session (chatroom), but work normally in other newly created session, and other existing session.
Activity
beenotung commentedon Apr 8, 2026
I encountered this bug before, and the bug keep occur for a specific session (chatroom), but work normally in other newly created session, and other existing session.
github-actions commentedon Jul 3, 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.