Skip to content

fix(zen): gate safety identifier by provider config#20141

Closed
Hona wants to merge 1 commit intoanomalyco:devfrom
Hona:fix-kimi-safety-identifier
Closed

fix(zen): gate safety identifier by provider config#20141
Hona wants to merge 1 commit intoanomalyco:devfrom
Hona:fix-kimi-safety-identifier

Conversation

@Hona
Copy link
Copy Markdown
Member

@Hona Hona commented Mar 30, 2026

Summary

  • honor the existing provider-level safetyIdentifier flag when building Zen provider options
  • stop sending safety_identifier to OpenAI-compatible providers like Kimi K2.5 unless that provider explicitly opts in
  • keep the fix minimal by aligning safetyIdentifier with the existing �djustCacheUsage config pattern

Copilot AI review requested due to automatic review settings March 30, 2026 23:02
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Zen route provider option-building logic to only include a safetyIdentifier when the selected provider explicitly opts in via its provider config, preventing unintended propagation to OpenAI-compatible providers.

Changes:

  • Gate safetyIdentifier assignment behind providerProps.safetyIdentifier.
  • Pass undefined for safetyIdentifier when the provider has not opted in, aligning with the existing provider-prop pattern used for adjustCacheUsage.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@Hona Hona closed this Mar 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants