Repository navigation
x: treat add_conversation_keys UNAUTHORIZED_REQUESTING_USER as final (2.8.1) - #728
Open
santiagomed wants to merge 1 commit into
Open
santiagomed wants to merge 1 commit into
santiagomed wants to merge 1 commit into
Conversation
…the X MCP guide The code means the other person can't receive encrypted chats from the owner, almost always because they don't follow the owner, and it lasts until they follow. The guide blamed the peer not being on X Chat, so agents kept re-posting the same saved request body. Bump the X plugin to 2.8.1.
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.
Why
add_conversation_keysreturnsUNAUTHORIZED_REQUESTING_USERwhen the other person can't receive encrypted chats from the caller, almost always because they don't follow the caller. It lasts until they follow. The guide said the peer was likely not on XChat, so agents kept re-posting the same saved request body and the 400s kept climbing.What
UNAUTHORIZED_REQUESTING_USERis final for that conversation for the session. Don't re-post, re-prepare keys, or send. Tell the owner the other person has to follow them first, and both accounts need X Chat keys.add_conversation_keysbody is single-use and must never be saved and re-posted.plugin.jsonversion and CHANGELOG entry. 2.8.1 is the next patch after 2.8.0 on main, and no open PR claims it.Testing
node scripts/validate-plugins.mjs: all plugins validated.node scripts/generate-pstack-harness-trees.mjs --check: up to date.Note
Low Risk
Documentation and plugin version only; no runtime or API behavior changes.
Reviewed by Cursor Bugbot for commit 6bd1975. Bugbot is set up for automated code reviews on this repo. Configure here.