Repository navigation
X skill: use X Chat's unread state - #578
Closed
santiagomed wants to merge 1 commit into
Closed
santiagomed wants to merge 1 commit into
santiagomed wants to merge 1 commit into
Conversation
This was referenced Oct 12, 2026
Collaborator
Author
|
Combined into #580. |
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.
X Chat now tracks read state, but the X MCP guide never told agents about it. A fresh agent asked what's unread said "X doesn't tell me which chats are unread" and scanned every conversation for messages newer than the read point.
The guide gets a short Unread section before Read / summarize. For "what's unread" it lists
get_chat_conversationswithunread_onlytrue and theunread,last_read_event_id,newest_event_idfields, paging untilmeta.has_moreis false since pages can be short or empty. Unread messages are the events afterlast_read_event_id. Message requests still come from their own list whenmeta.has_message_requestsis true. Read / summarize points there for unread questions, and Don't gets one line against scanning. The plugin goes to 2.6.3.The MCP doesn't expose mark-unread or archive tools yet, so they aren't documented.
This merges cleanly with #566. #563 also takes 2.6.3, so whichever lands second needs to rename its CHANGELOG heading. The skill text doesn't overlap.
Test plan
node scripts/validate-plugins.mjspasses.get_chat_conversationswithunread_onlyand the unread fields, pages untilhas_moreis false, and doesn't scan every thread.Note
Low Risk
Documentation and version bump only; no runtime or API code changes.
Overview
Bumps the X Cursor plugin to 2.6.3 and documents how agents should answer “what’s unread” in X Chat using server read state instead of scanning the whole inbox.
The X MCP guide (
SKILL.md) adds an Unread section: callget_chat_conversationswithunread_onlytrue and fieldsunread,last_read_event_id,newest_event_id, paginate onmeta.has_more(including short/empty pages), then load events afterlast_read_event_idper thread; message requests still come from the separate request flow whenmeta.has_message_requestsis true. Read / summarize now points unread questions at that flow; Don't forbids inferring unread by scanning every conversation’s events.Reviewed by Cursor Bugbot for commit 99979f1. Bugbot is set up for automated code reviews on this repo. Configure here.