Skip to content

X skill: don't surface per-message encryption status - #543

Merged
vaulpannx merged 2 commits into
cursor:mainfrom
santiagomed:cursor/x-encryption-status-quiet-2f0c
Oct 11, 2026
Merged

vaulpannx merged 2 commits into
cursor:mainfrom
santiagomed:cursor/x-encryption-status-quiet-2f0c

Conversation

@santiagomed

@santiagomed santiagomed commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

Summaries were adding unprompted notes that X Chat messages were unencrypted, which is normal for threads that still have no conversation key and just gets in the way of reading messages. The skill now focuses summaries on the content and uses status when the user asks about encryption or when unverified matters, and bumps the X plugin to 2.6.2.


Note

Low Risk
Documentation and agent skill text only; no runtime or API behavior changes.

Overview
X plugin 2.6.2 tightens how agents present X Chat: summaries should emphasize message content, not unprompted encryption commentary.

The X MCP guide now states that plain DMs are normal when a thread has no conversation key (including recent messages), and agents must not treat unencrypted messages as suspicious. Encryption/status (verified, unencrypted, unverified) is for when the user asks about security or when unverified matters before acting on a message. CHANGELOG.md documents the same behavior change.

Reviewed by Cursor Bugbot for commit 51fd619. Bugbot is set up for automated code reviews on this repo. Configure here.

A thread with no conversation key still carries plain DMs, including
recent ones. status is internal metadata: don't mention encryption
status unless the user asks.
Unprompted encryption commentary gets in the way of reading messages.
Plain DMs are normal when a thread has no conversation key. Answer
encryption questions from status.
@vaulpannx
vaulpannx merged commit 11713c6 into cursor:main Oct 11, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants