Document granular conversation priority levels in Preview spec#573
Merged
Apexinsideapex merged 1 commit intoJul 2, 2026
Merged
Conversation
The conversation priority field and the priority_changed conversation part now expose granular levels (none, low, medium, high, urgent) in the Preview spec, replacing the binary priority/not_priority values. Example values are normalized to the new enum. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
VedranZoricic
approved these changes
Jul 2, 2026
Apexinsideapex
deleted the
rohitsharma/conversation-priority-levels-preview-docs
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
The conversation
priorityfield is moving from binary values to granularpriority levels in the Preview API version. The OpenAPI spec needs to reflect
the new values so consumers on Preview see the correct contract.
How?
Update the conversation
priorityenum and thepriority_changedconversationpart enum in the Preview spec to
none, low, medium, high, urgent, andnormalize example values to match.
Generated with Claude Code