feat: add GOOSE_PROVIDER_TIMEOUT config for provider API timeouts - #9145
Closed
Raptors65 wants to merge 1 commit into
Closed
feat: add GOOSE_PROVIDER_TIMEOUT config for provider API timeouts#9145Raptors65 wants to merge 1 commit into
Raptors65 wants to merge 1 commit into
Conversation
Raptors65
force-pushed
the
lucas/feat/goose-provider-timeout
branch
2 times, most recently
from
May 12, 2026 14:34
6bb11d7 to
4e3b520
Compare
Raptors65
force-pushed
the
lucas/feat/goose-provider-timeout
branch
from
May 15, 2026 15:38
4e3b520 to
269e82a
Compare
Contributor
|
This pull request has been automatically marked as stale because it has not had recent activity for 23 days. What happens next?
Thank you for your contribution! 🚀 |
Contributor
|
This pull request has been automatically closed due to inactivity. Why was this closed?
Want to reopen?
Thank you for your contribution! We appreciate your effort. 🙏 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
While working on #9138, I noticed Goose has a 600s timeout for all providers, which is from the initial request to the stream ending. When Goose hits this timeout, it gives the following error:
This is configurable for some providers (specifically, OpenAI, Ollama, and LiteLLM) but not others. It seems to make sense to have a more general
GOOSE_PROVIDER_TIMEOUTthat we fall back to whenever a provider-specific value isn't provided; we might also want to add provider-specific configs for the other providers in a follow up.This PR adds a
GOOSE_PROVIDER_TIMEOUTthat we fall back to whenever a provider-specific value isn't provided.Testing
unit tests
Related Issues
N/A
Screenshots/Demos (for UX changes)
N/A (no UX changes)