Skip to content

Accept replayed reasoning aliases without rejecting messages - #52

Open
strin wants to merge 1 commit into
recursive-oss:mainfrom
strin:codex/f004-reasoning-aliases
Open

strin wants to merge 1 commit into
recursive-oss:mainfrom
strin:codex/f004-reasoning-aliases

Conversation

@strin

@strin strin commented Nov 5, 2026

Copy link
Copy Markdown

Assistant messages carrying both reasoning and reasoning_content currently return HTTP 400. Normalize them once, giving the public reasoning field precedence by presence, including empty/null values. This avoids concatenating duplicate thoughts when clients replay responses.

Fixes #46.

Validation: 38 focused Python tests passed across serving, Anthropic translation and chat; Ruff and whitespace checks passed. Coverage includes equal/different aliases, either field alone, empty/null precedence, and streaming/nonstreaming responses. No real model inference or Hermes session was run.

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.

Messages carrying both reasoning and reasoning_content are rejected with 400

1 participant