fix(client): default SSE Accept headers - #48779

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

The issue already exists as #48771, and the PR description already contains Closes #48771.

This appears to be a non-default-branch edge case: this PR correctly targets v2, while the repository default is dev. GitHub documents that closing keywords do not create links for non-default branches. The standards workflow checks closingIssuesReferences, which is consequently empty, rather than the reference in the body.

I tried the supported addCloseIssueReferences mutation, but GitHub denied it because my account lacks permission to link issues in this repository. Could a maintainer manually link #48771 through the Development sidebar so the check can recognize it? The v2 base and code changes will remain unchanged.

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

• The PR was created more than 1 month ago
• The PR had fewer than 2 positive reactions
• Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.

Could a maintainer please reconsider reopening this PR?

I'm experiencing the same issue on Windows with Kaspersky Endpoint Security and OpenCode 2.1.4.

Both the CLI and Desktop repeatedly lose their SSE connections:

• CLI: Timed out connecting to server approximately every 2 seconds.
• Desktop: continuous event stream disconnected and starting v2 background service messages.
• The server itself responds correctly to HTTP API requests, including /api/model.
• /api/event streams events and heartbeats correctly when tested with curl.
• Clean reinstallations and fresh databases did not resolve the issue.

This makes OpenCode 2.x practically unusable on my machine.

The proposed Accept: text/event-stream fix appears highly relevant, especially given the author's successful Kaspersky tests.

This PR was closed by automated cleanup rather than a failed technical review. Could it please be reopened and considered for the current v2 release?

There also appears to be an issue-linking problem with #48771, as documented by the PR author.

Thank you!

I'd like to confirm that this fix works in practice on Windows with Kaspersky Endpoint Security enabled.

We encountered persistent SSE connection failures after upgrading OpenCode from 2.0.6 to 2.1.4.

Symptoms:

• CLI/TUI repeatedly showed Connection lost and Restarting service....
• SSE requests timed out after approximately 2001 ms.
• Desktop continuously logged event stream disconnected.
• Desktop displayed "No models found", despite the backend correctly returning 10 models through /api/model.
• Reinstalling OpenCode and resetting its databases did not resolve the issue.

We applied the fix from this PR to OpenCode 2.1.4 and rebuilt both the Windows CLI and Desktop.

Results:

• First SSE event received in 33 ms, compared with the previous 2001 ms timeout.
• SSE connection remained stable for 65 seconds, including heartbeats.
• 140 tests passed, along with type checks and client regeneration.
• Three consecutive TUI launches completed without connection failures.
• Desktop successfully loaded all 10 models, including our custom alor-ai / MiniMax M2.7 provider.
• We subsequently restored our shared user profile and credentials, and both patched applications are now working.

All of this was achieved without disabling Kaspersky or adding antivirus exclusions.

This confirms that the missing Accept: text/event-stream header can make both OpenCode CLI and Desktop unusable in a real Windows environment, and that the proposed fix resolves the issue.

Could a maintainer please reopen this PR, review it, and consider merging or porting the fix into the current release?

The PR was closed by automated cleanup, not because the patch failed review. Given that this affects both CLI and Desktop, I believe it deserves another look.

Thanks to @DEAN-Cherry for identifying the root cause and providing the fix!