Skip to content

[pull] main from Alishahryar1:main - #241

Merged
pull[bot] merged 1 commit into
Co-Contribute-OpenSource:mainfrom
Alishahryar1:main
Sep 24, 2026
Merged

pull[bot] merged 1 commit into
Co-Contribute-OpenSource:mainfrom
Alishahryar1:main

Conversation

@pull

@pull pull Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

## Why
OpenAI can reject `temperature` or `top_p` for a model's current
reasoning mode, preventing otherwise valid FCC requests from completing.
FCC needs to handle those explicit incompatibility errors without
maintaining model-name rules or discarding settings that OpenAI accepts.

## How
Send the original sampling settings, then use an OpenAI API-specific
correction callback in the shared Responses transport to remove only the
field explicitly rejected upstream. Recognize structured
`unsupported_parameter` errors and the narrow default-only
`unsupported_value` form. Both Messages and native Responses use the
existing recovery path, including reasoning/history corrections, stream
commitment safeguards, and the shared five-attempt limit.

Corrections apply only to the current request: there is no model table
or capability cache. Each subsequent request starts with its original
settings, so incompatible requests can incur extra round trips.
Ambiguous and unrelated validation errors keep their normal failure
behavior. Bump the package version to 6.2.60.


<!-- greptile_comment -->

<!-- greptile_summary -->

<h2><a
href="https://app.greptile.com/api/retrigger?id=68632430"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://greptile-static-assets.s3.amazonaws.com/badges/RetriggerDark.svg?v=2"><source
media="(prefers-color-scheme: light)"
srcset="https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2"><img
alt="Retrigger"
src="https://greptile-static-assets.s3.amazonaws.com/badges/Retrigger.svg?v=2"
align="right"></picture></a>Confidence Score: 5/5</h2>

No outstanding findings block merging.

<details open><summary>Summary</summary>

The OpenAI API provider now preserves requested sampling settings until
OpenAI explicitly rejects one, then retries without the rejected
setting. Both previously reported issues are fixed.
</details>

<!-- greptile_confidence_score:5 -->

<sub>Reviews (3) · Last reviewed commit: ["Correct OpenAI sampling only
after
expli..."](https://github.com/alishahryar1/free-claude-code/commit/c397b03337473e4625dce5e40988a456985e5473)</sub>

<!-- /greptile_comment -->
@pull pull Bot locked and limited conversation to collaborators Sep 24, 2026
@pull pull Bot added the ⤵️ pull label Sep 24, 2026
@pull
pull Bot merged commit 82408c5 into Co-Contribute-OpenSource:main Sep 24, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant