Bug: /event replay semantics are implicit and conflict with SSE backpressure handling #19584

Activity

1. github-actions

   assigned

   thdxr

   on Mar 29, 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 29, 2026
3. github-actions commented on Mar 29, 2026

   

   github-actionsBot

   on Mar 29, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn't fully meet our contributing guidelines.

   What needs to be fixed:

   • The issue does not use one of the three required issue templates (Bug Report, Feature Request, or Question). Please resubmit using the appropriate template.
   • The description reads as AI-generated: it is highly structured with proposed implementation details, specific internal event names, and design recommendations that go well beyond describing a bug. AI-generated walls of text are not acceptable per our guidelines.
   • Bug reports should describe observed behavior with actual reproduction steps — this issue describes hypothetical/expected behavior rather than a confirmed bug.
   • The environment section lists v1.3.4 baseline which does not appear to be a real version; please include your actual OpenCode version.

   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:

   • [FEATURE]: Durable event export / replay surface for external integrations #19567: Durable event export / replay surface — covers cursor-based replay semantics and SSE replay for external integrations
   • SSE event streams leak memory on client disconnect #15645: SSE event streams leak memory on client disconnect — related SSE stream lifecycle issues
   • [FEATURE]:Support sessionID Filter for SSE Event Subscription #9650: Support sessionID filter for SSE event subscription — touches the same /event route and SSE stream architecture

   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.

   and removed

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

   on Mar 29, 2026
5. github-actions commented on Mar 29, 2026

   

   github-actionsBot

   on Mar 29, 2026 – with GitHub Actions

   Contributor

   More actions

   Thank you for updating the issue! It now follows the contributing guidelines and includes all the necessary information. We appreciate the clear description, reproduction steps, and system details.
6. thdxr

   assigned

   jlongster

   and unassigned

   thdxr

   on Apr 26, 2026
7. thdxr

   removed

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

   on May 3, 2026
8. github-actions commented on Jul 3, 2026

   

   github-actionsBot

   on Jul 3, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
9. github-actions

   closed this as not plannedon Jul 3, 2026