Missing x-opencode-session header in Node.js fetch calls

[PCServices2]

Description

I received a notification from the model provider ("OpenCode Go") that some requests are missing the required x-opencode-session header. The affected user agent is Node fetch.

Details from provider
“Some of your requests to OpenCode Go are missing an x-opencode-session header. If we don't have this we cannot properly optimize our service. Starting 09/06 requests missing this header may error.”

Impact
“Starting September 6th, 2026, requests without this header may begin failing, potentially causing errors or degraded service.”

Plugins

No response

OpenCode version

Current version: 2.5.3

Steps to reproduce

1. Use Opencode
2. Wait a few days for the email to arrive
3. Investigate what the email is talking about
4. Submit a report, as the issue appears to be related to an error or omission on the part of a developer on GitHub

Screenshot and/or share link

No response

Operating System

Running as Home Assistant add-on (f5588468_ha_opencode)

Terminal

Unknown

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• Steps to reproduce are listed as "Unknown" — a bug report needs at minimum some context about how the issue was observed or triggered
• The description appears to relay a provider notification verbatim rather than describing a user-observed behavior; please describe what you actually experienced (e.g., error messages, failing requests, logs)
• Version "2.5.3" does not match any known opencode release — please verify and correct the version

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

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

Thank you for updating the issue. Unfortunately it still needs a few more changes before it meets our contributing guidelines.

What still needs to be fixed:

1. AI-generated description: The description contains text that was generated by OpenCode when you asked it to interpret the provider email. We don't accept AI-generated content as issue descriptions — please describe in your own words what you observed (e.g., "I received an email from my model provider saying requests are missing a header, and I'm not sure if this is something OpenCode should handle").

2. Steps to reproduce: "Use Opencode." is not sufficient. Please describe what you were doing when you received this notification, or what behavior you observed that led you to report this. Even a brief description like "I received a provider notification email while using OpenCode normally" is more useful than the current text.

We understand you're not a programmer — a simple description of what happened in your own words is exactly what we need. You don't need technical detail; just tell us what you experienced.

Please edit the issue to address the above. Thanks!

[PCServices2]

The OpenCode version is taken straight from the OpenCode plugin, within Home Assistant.

The steps to reproduce the issue are not relevant, as the email I received from the developer was through simply using OpenCode and having it look at a few issues. I can only assume that this generated some server side error logs and that the developer was responding to them.

[github-actions]

Thank you for responding and for the additional context in your comment — that's actually exactly the kind of information we need.

However, the issue description itself still contains text that was generated by OpenCode when you asked it to interpret the provider email. We can't accept AI-generated content as the issue body.

What still needs to be fixed:

The description should be written in your own words. Based on your comment, something like this would be perfectly acceptable:

I received an email from my model provider saying that some requests from OpenCode are missing a required header. I'm not a programmer and I'm not sure if this is something OpenCode should handle, but I wanted to report it in case it's relevant.

That's genuinely all we need. You don't need to include the AI-generated technical analysis — just a plain description of what you experienced and why you're reporting it.

Please edit the issue body to remove the AI-generated text and replace it with a brief description in your own words. Thanks for your patience!

[github-actions]

Thank you for updating your issue! It now follows the contributing guidelines and issue template. We appreciate you taking the time to provide the details.

[pengzh1]

Taking a look at this — planning to thread the session header through the remaining request path.