Add reasoning effort control and selectable messages - #32
Merged
Conversation
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
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.
Summary
supportedReasoningEffortsRoot cause
Message content did not override the non-selectable behavior inherited from Obsidian's application-style view shell. The model catalog integration also discarded
supportedReasoningEffortsanddefaultReasoningEffort, even thoughmodel/listalready returned both fields, leaving the composer with model names only.User impact
Users can select and copy rendered responses. They can also choose the reasoning level supported by the active Codex model; leaving the control on Default uses that model's advertised default.
Validation
npm run typechecknpm test(70 tests passed)npm run buildmodel/listand verified model-specific effort catalogsScreenshots
Not attached because the message-selection fix has no static visual delta and the effort menu is rendered by Obsidian's native
Menu; the control was validated in the local development Vault.