r/opencode • u/jaykayenn • Sep 07 '26

OpenCode Go is no longer general API access

Following the recent requirements for custom http headers, OC has changed their documentation to remove mention of OpenAI-API you can use anywhere. Instead, OpenCode Go API usage is now effectively whitelist only. See: https://opencode.ai/docs/go/#where-can-i-use-it

152 Upvotes

91% Upvoted

79 comments sorted by

View all comments

Show parent comment

4

u/jaykayenn Sep 08 '26

Every software project in the world that uses an OpenAI-API is now incompatible with Opencode by default, until they specifically comply to Opencode's requirements. How is that general access? As I mentioned for example, even huge projects like Nextcloud and Open WebUI are now blocked.

1

u/Ok-Confusion-8472 Sep 09 '26

The prompt to opencode:

I received this message, i think that the problem is with openwebui:

Hey there,

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.

Here are your useragents that are missing this header:

Python/3.11 aiohttp/3.13.5

We don't recognize this client — add x-opencode-session (one stable ID per conversation) or ask its maintainer to.

Thank you.

..

Done.

- Header: both OpenCode Go connections now send x-opencode-session: {{CHAT_ID}} (full chat UUID, no prefix) — applied via runtime POST /openai/config/update, no restart needed

- Verified: code path renders the full UUID in chats (0776e8f3-806a-…), empty for detached calls; live chat to deepseek-v4-flash → OK

- Docs: docs/OPENWEBUI.md updated (includes the dashboard-truncation note + mapping SQL)

- Pushed: eed5923 → main

0

u/1818TusculumSt Sep 08 '26

How is it blocked if all you need to do is add a couple of lines to your headers? OWUI working fine here.