Skip to content

Conversation

@cyhhao
Copy link
Contributor

@cyhhao cyhhao commented Jan 12, 2026

Background

Provider options currently support baseURL/apiKey and setCacheKey, but there is no way to set the OpenAI Responses store flag at the provider level. This makes users repeat store=false for every model.

Changes

  • Read provider.options.store in ProviderTransform.options and emit it into request options.
  • Add store to the provider options schema so it is documented and validated.

Verification

  • bun test test/config/config.test.ts

@github-actions
Copy link
Contributor

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

  1. Open an issue describing the bug/feature (if one doesn't exist)
  2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

@github-actions
Copy link
Contributor

The following comment was made by an LLM, it may be inaccurate:

I found a potential duplicate:

Related PR:

This PR appears to be addressing the exact same feature - allowing configuration of the OpenAI store option at the provider level. Both PRs are focused on setting the store flag at the provider level to avoid repetition across models.

@cyhhao
Copy link
Contributor Author

cyhhao commented Jan 14, 2026

@rekram1-node Please pay attention to this issue, many users who use API relay services urgently need it. Thank you.

@rekram1-node rekram1-node merged commit fcf2da9 into anomalyco:dev Jan 15, 2026
5 checks passed
rekram1-node added a commit that referenced this pull request Jan 15, 2026
@rekram1-node
Copy link
Collaborator

Accidentally merged instead of commented, we should have some default model option or something because store is so tied to openai that it doesnt make sense to add that in generic config

hugojosefson pushed a commit to hugojosefson/opencode that referenced this pull request Jan 15, 2026
hugojosefson pushed a commit to hugojosefson/opencode that referenced this pull request Jan 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants