Message ordering breaks with clock-skewed IDs #17255

Activity

1. github-actions

   assigned

   rekram1-node

   on Mar 12, 2026
2. github-actions

   added

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   on Mar 12, 2026
3. github-actions commented on Mar 12, 2026

   

   github-actionsBot

   on Mar 12, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn't fully meet our contributing guidelines.

   What needs to be fixed:

   • No issue template was used. Please use one of the three required templates (Bug Report, Feature Request, or Question). For a bug report, this means including fields like Description, Steps to Reproduce, OpenCode version, and Operating System.

   Please edit this issue to address the above within 2 hours, or it will be automatically closed.

   ---

   This issue might be a duplicate of existing issues. Please check:

   • Web UI: client-generated message IDs cause infinite processing loop when client/server clocks diverge #11863: Web UI: client-generated message IDs cause infinite processing loop when client/server clocks diverge — describes the exact same root cause (clock-skewed IDs, shouldExitLoop condition failing, infinite prompt loop)
   • Clock skew between client and server breaks prompt loop and message rendering #14236: Clock skew between client and server breaks prompt loop and message rendering — same issue with prompt loop and message rendering broken by ID timestamp skew
   • Bug: Message ordering broken when client clock is out of sync with server #15657: Bug: Message ordering broken when client clock is out of sync with server — same message ordering breakage due to clock differences

   If you believe this was flagged incorrectly, please let a maintainer know.
4. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Mar 12, 2026
5. sjawhar commented on Mar 12, 2026

   

   sjawhar

   on Mar 12, 2026

   Author

   More actions

   Duplicate of #11863. PR #17256 addresses this.
6. sjawhar

   closed this as not plannedon Mar 12, 2026