Skip to content

OpenAI provider headers timeout after 10000ms on 1.15.11; increasing headerTimeout fixes it #29548

Closed

Description

@rayborg

Description

After upgrading OpenCode via Homebrew from 1.14.28 to 1.15.11, requests using the OpenAI provider began failing with:

Provider response headers timed out after 10000ms

Increasing the OpenAI provider headerTimeout resolved the issue locally.

This looks like a regression or a default timeout that may be too aggressive for some OpenAI/ChatGPT-provider requests or network environments.

Plugins

No custom plugins involved in the repro.

OpenCode version

1.15.11

Installed via Homebrew.

Steps to reproduce

  1. Upgrade OpenCode from 1.14.28 to 1.15.11 via Homebrew.
  2. Use the OpenAI provider with gpt-5.5-fast / GPT-5.5 Fast.
  3. Run a normal request.
  4. Observe the request fail with:
Provider response headers timed out after 10000ms
  1. Add the following provider options to the global config:
{
  "$schema": "https://opencode.ai/config.json",
  "provider": {
    "openai": {
      "options": {
        "headerTimeout": 60000,
        "timeout": 600000,
        "chunkTimeout": 60000
      }
    }
  }
}
  1. Verify with opencode debug config that the options are loaded.
  2. Run the same request again.
  3. Observe that it succeeds after increasing headerTimeout.

Screenshot and/or share link

N/A. Relevant terminal error is included above.

Operating System

macOS, arm64

Terminal

zsh

Question

Is the 10000ms default intended for OpenAI/ChatGPT-provider requests in 1.15.11? It may be too low for some responses or network/proxy environments.

Activity

  1. github-actions commented on May 27, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

  2. rayborg commented on May 27, 2026

    @rayborg
    Author

    Clarifying the duplicate suggestions:

    This issue is specifically a shorter 10000ms header timeout observed after upgrading to 1.15.11 with the OpenAI provider / ChatGPT-provider path using gpt-5.5-fast.

    The practical difference is the failing threshold and provider path:

    So this may share the broader timeout-config surface, but it seems worth tracking separately unless maintainers consider the 1.15.11 OpenAI 10000ms default intentionally covered by those issues.

  3. rekram1-node commented on May 27, 2026

    @rekram1-node
    Collaborator

    This is intentional, many people are getting no response from openai for extended periods of time almost every other request it seems for certain folks, so we have this header timeout to account for that, as seen in the release notes for the release.

    We may bump it but it's entirely configurable and u can even disable it by setting headerTimeout: false

  4. C485 commented on May 27, 2026

    @C485

    This is intentional, many people are getting no response from openai for extended periods of time almost every other request it seems for certain folks, so we have this header timeout to account for that, as seen in the release notes for the release.

    We may bump it but it's entirely configurable and u can even disable it by setting headerTimeout: false

    i guess we need something that will disable all timeouts in config file, for now
    "timeout": 3000000, "chunkTimeout": 3000000, "headerTimeout": false
    does nothing at all, for local providers we're still getting
    TypeError: terminated at Fetch.onAborted (node:internal/deps/undici/undici:13602:53)
    I would be great to have it as soon as possible

  5. rekram1-node commented on May 27, 2026

    @rekram1-node
    Collaborator

    @C485 this seems like something else entirely none of those timeouts are enabled by default besides header timeout but its only enabled for openai provider and thats it (by default)

  6. Dayclone commented on Jun 3, 2026

    @Dayclone

    I get "Provider response headers timed out after 10000ms" now as well when it never used to happen

  7. rekram1-node commented on Jun 3, 2026

    @rekram1-node
    Collaborator

    @Dayclone u can bump it

  8. Dayclone commented on Jun 3, 2026

    @Dayclone

    @rekram1-node I did
    "provider": { "openai": { "options": { "timeout": 20000 } },

    But probably did that wrong?

  9. rekram1-node commented on Jun 3, 2026

    @rekram1-node
    Collaborator

    Yes u did, read above msgs, it is headerTimeout

  10. Dayclone commented on Jun 3, 2026

    @Dayclone

    Yep that was it thank you! Seems to be working now.

  11. Abdo-Eid commented on Jun 8, 2026

    @Abdo-Eid

    From what I noticed, the problem appears after GPT models read/analyze images and disappears when I compact the conversation or talk in a new chat
    i disabled the headerTimeout as @rekram1-node suggested, it took some time but it eventually responded without compaction
    @rayborg

  12. kossnocorp commented on Jul 11, 2026

    @kossnocorp

    Tried the fix when using GPT-5.6 Sol and it worked! I had to fall back to Codex few times in the past because of this problem, and losing the session history of WIP was very annoying. I hope it gets fixed so OpenCode users don't churn, but the config change works for me for now 👌 Thank you @rayborg

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions