Skip to content

Fix fin_reply_chunk status in 2.14 and 2.15 specs#477

Merged
rahulgdsouza merged 1 commit intomainfrom
rgd/fix-fin-reply-chunk-status
Apr 24, 2026
Merged

Fix fin_reply_chunk status in 2.14 and 2.15 specs#477
rahulgdsouza merged 1 commit intomainfrom
rgd/fix-fin-reply-chunk-status

Conversation

@rahulgdsouza
Copy link
Copy Markdown
Contributor

Why?

The SSE streamer has always hardcoded "status": "replying" in every fin_reply_chunk event, but the 2.14 and 2.15 OpenAPI specs incorrectly documented the status as awaiting_user_reply. The Preview spec (version 0) was already correct, so the older specs were out of sync with both actual behavior and the latest docs.

How?

Updated the fin_agent_reply_chunk_event schema's status field in 2.14 and 2.15 specs — changed the enum, description, and example from awaiting_user_reply to replying to match what the streamer actually sends.

Generated with Claude Code

The SSE streamer has always sent "status": "replying" in every
fin_reply_chunk event across all API versions. Update 2.14 and 2.15
specs to match the actual behavior and the Preview spec.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@rahulgdsouza rahulgdsouza self-assigned this Apr 24, 2026
@rahulgdsouza rahulgdsouza merged commit 5b40e3c into main Apr 24, 2026
3 checks passed
@rahulgdsouza rahulgdsouza deleted the rgd/fix-fin-reply-chunk-status branch April 24, 2026 11:05
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