anomalyco / anomalyco/opencode

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

Open
#47,438 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Node.js fetch call sites that construct requests to model providers and check how request headers are assembled. Confirm which requests need x-opencode-session, then add coverage showing the header is present on those requests and that the affected provider calls no longer omit it.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.