fix(tools): tolerate duplicate sessionKey/label in sessions_send#2317
Open
BingqingLyu wants to merge 1 commit into
Open
fix(tools): tolerate duplicate sessionKey/label in sessions_send#2317BingqingLyu wants to merge 1 commit into
BingqingLyu wants to merge 1 commit into
Conversation
LLMs and UI layers (ClawX, Control UI) sometimes mirror the same value into both `sessionKey` and `label` when calling `sessions_send`. This triggers the mutual-exclusion guard even though the intent is unambiguous. Relax the check: only reject when both params are provided AND they differ. When they are equal, treat the call as sessionKey-only (the more specific routing path). Fixes openclaw#64699
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.
Summary
When calling
sessions_send, LLMs and UI layers (ClawX, Control UI) sometimes mirror the same value into bothsessionKeyandlabel. This triggers the mutual-exclusion guard even though the intent is unambiguous.Changes
Relax the check: only reject when both params are provided AND they differ. When they are equal, treat the call as sessionKey-only (the more specific routing path).
Testing
sessionKeyandlabelare the same → uses sessionKey, no errorsessionKeyandlabeldiffer → still rejects with existing errorFixes openclaw#64699