Fix/configure add provider custom headers#7157
Merged
Abhijay007 merged 3 commits intoblock:mainfrom Feb 12, 2026
Merged
Conversation
Previously custom headers were only prompted for openai_compatible providers; now they are offered for every provider type. Signed-off-by: Sahil8383 <sahilbhatt915@gmail.com>
Signed-off-by: Sahil8383 <sahilbhatt915@gmail.com>
Contributor
Author
|
@dianed-square could you take a look at this PR when you have a moment? (Fixes: #7014 ) |
Contributor
|
@Sahil8383 Thanks and looks good to me and goose, but I'll defer approval to the eng team. |
Signed-off-by: Sahil8383 <sahilbhatt915@gmail.com>
Contributor
Author
tlongwell-block
added a commit
that referenced
this pull request
Feb 12, 2026
…provenance * origin/main: (68 commits) Upgraded npm packages for latest security updates (#7183) docs: reasoning effort levels for Codex provider (#6798) Fix speech local (#7181) chore: add .gooseignore to .gitignore (#6826) Improve error message logging from electron (#7130) chore(deps): bump jsonwebtoken from 9.3.1 to 10.3.0 (#6924) docs: standalone mcp apps and apps extension (#6791) workflow: auto-update cli-commands on release (#6755) feat(apps): Integrate AppRenderer from @mcp-ui/client SDK (#7013) fix(MCP): decode resource content (#7155) feat: reasoning_content in API for reasoning models (#6322) Fix/configure add provider custom headers (#7157) fix: handle keyring fallback as success (#7177) Update process-wrap to 9.0.3 (9.0.2 is yanked) (#7176) feat: support extra field in chatcompletion tool_calls for gemini openai compat (#6184) fix: replace panic with proper error handling in get_tokenizer (#7175) Lifei/smoke test for developer (#7174) fix text editor view broken (#7167) docs: White label guide (#6857) Add PATH detection back to developer extension (#7161) ... # Conflicts: # .github/workflows/nightly.yml
jh-block
added a commit
that referenced
this pull request
Feb 13, 2026
* origin/main: (21 commits) nit: show dir in title, and less... jank (#7138) feat(gemini-cli): use stream-json output and re-use session (#7118) chore(deps): bump qs from 6.14.1 to 6.14.2 in /documentation (#7191) Switch jsonwebtoken to use aws-lc-rs (already used by rustls) (#7189) chore(deps): bump qs from 6.14.1 to 6.14.2 in /evals/open-model-gym/mcp-harness (#7184) Add SLSA build provenance attestations to release workflows (#7097) fix save and run recipe not working (#7186) Upgraded npm packages for latest security updates (#7183) docs: reasoning effort levels for Codex provider (#6798) Fix speech local (#7181) chore: add .gooseignore to .gitignore (#6826) Improve error message logging from electron (#7130) chore(deps): bump jsonwebtoken from 9.3.1 to 10.3.0 (#6924) docs: standalone mcp apps and apps extension (#6791) workflow: auto-update cli-commands on release (#6755) feat(apps): Integrate AppRenderer from @mcp-ui/client SDK (#7013) fix(MCP): decode resource content (#7155) feat: reasoning_content in API for reasoning models (#6322) Fix/configure add provider custom headers (#7157) fix: handle keyring fallback as success (#7177) ...
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.
Previously custom headers were only prompted for openai_compatible providers; now they are offered for every provider type.
Summary
The CLI's custom provider configuration only asked for custom headers when adding an OpenAI compatible provider. The backend already supports custom headers for all three provider types (OpenAI, Anthropic, and Ollama compatible). This change updates the configure flow so custom headers are prompted for every provider type.
Type of Change
Testing
Manual testing: ran
goose configure→ Custom Providers → Add A Custom Provider, chose Anthropic Compatible and Ollama Compatible, and confirmed the custom headers prompt appears for both (same as for OpenAI Compatible).Related Issues
Relates to #7014
Screenshots/Demos (for UX changes)
Before:

After:
