Fix: Preserve user's response language (#7)#100
Open
Subharup-31 wants to merge 1 commit into
Open
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
Problem
Issue #7 reports that Clicky can reply in the wrong language when the user speaks or writes in Russian or another non-English language. The response prompt did not directly instruct the model to preserve the user's current language, so multilingual interactions could drift into unrelated languages.
Fix
Added a focused language-preservation rule to the companion voice response system prompt in
CompanionManager.swift. The rule tells Clicky to respond in the same natural language as the user's latest message, while still allowing explicit translation or language-switch requests.Verification
swiftc -parse leanring-buddy/*.swiftsuccessfully.Closes #7