Autotitle conversations whose reply is wrapped in a markdown json fence - #816
Merged
Merged
Conversation
Claude via RubyLLM answers the title prompt with ```json ... ``` despite the JSON-only instruction, so JSON.parse failed and the title stayed blank. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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
AIBackend::RubyLLM) answers the autotitle prompt with a fenced```json ... ```block despite the JSON-only instruction, soJSON.parsefailed, the job logged "Unusable reply", and new conversations stayed untitled in the sidebar.AutotitleConversationJobnow strips a markdown fence before parsing; unfenced and non-string replies are untouched.Verify in dev
Verify in production
🤖 Generated with Claude Code