Skip to content

fix(kiro): map GPT reasoning effort fields#2701

Closed
SemonCat wants to merge 1 commit into
decolua:masterfrom
SemonCat:fix/kiro-gpt-reasoning-effort
Closed

fix(kiro): map GPT reasoning effort fields#2701
SemonCat wants to merge 1 commit into
decolua:masterfrom
SemonCat:fix/kiro-gpt-reasoning-effort

Conversation

@SemonCat

@SemonCat SemonCat commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

Summary

  • map GPT-5.6 effort to additionalModelRequestFields.reasoning.effort
  • preserve Claude adaptive-effort mapping through output_config.effort
  • keep the existing prompt tags for backward compatibility

Why

Kiro CLI selects the effort field path from each model schema. GPT models use reasoning.effort, while Claude models use output_config.effort. 9Router previously only emitted the Claude-shaped request fields, so GPT-5.6 did not receive the same structured thinking level as Kiro CLI.

Verification

  • production Docker build (npm run build) passes on Node 22
  • targeted mapping smoke confirms GPT reasoning.effort and existing Claude output_config.effort
  • live Kiro GPT-5.6 request with reasoning_effort: high returned HTTP 200
  • added OpenAI- and Claude-format translator coverage for GPT-5.6 effort mapping and invalid values

@SemonCat

Copy link
Copy Markdown
Contributor Author

Superseded by #2707, which also preserves Responses API reasoning.effort through the OpenAI bridge and covers the actual Hermes codex_responses path.

@SemonCat SemonCat closed this Jul 19, 2026
@decolua

decolua commented Jul 19, 2026

Copy link
Copy Markdown
Owner

Thanks @SemonCat for the contribution! Reviewed and merged into master. 🙏

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