Skip to content

chore: sync with cursor/plugins — Merge pull request #1186 from santiagomed/cursor/x-guide-chat-lookup-f5dd - #75

Merged
SmailG merged 7 commits into
mainfrom
sync/merge-pull-request-1186-from-santiagomed-cursor-x-guide-chat-6-commits
Nov 7, 2026
Merged

SmailG merged 7 commits into
mainfrom
sync/merge-pull-request-1186-from-santiagomed-cursor-x-guide-chat-6-commits

Conversation

@SmailG

@SmailG SmailG commented Nov 7, 2026

Copy link
Copy Markdown
Owner

Upstream changes

6b03002 Merge pull request cursor#1186 from santiagomed/cursor/x-guide-chat-lookup-f5dd
e336b83 X plugin 2.11.1: changelog for the contact playbook and the X DM send rule
fb77aaa X MCP guide: step-by-step playbook to find or message a contact
fb4bf31 X MCP guide: find a contact's thread with participant_query
8ecfb19 Merge pull request cursor#1185 from cursor/add-fitmetrics-plugin
2101076 feat(third_party): add FitMetrics plugin


Automated sync via sync-upstream workflow

rshah2020 and others added 7 commits November 6, 2026 13:09
Co-authored-by: Cursor <cursoragent@cursor.com>
Add FitMetrics plugin (third_party/fitmetrics)
To find or message someone the owner already chats with, the guide now
starts with get_chat_conversations participant_query (their @handle or
name, type direct, expansions participant_ids) instead of resolving their
handle to an id and matching participants across the inbox.

Send or reply also says X DMs go out only through send_chat_message, never
an email or Slack draft tool, and that when a host holds the call for
approval, the send repeats it with exactly the same arguments rather than
re-encrypting.
Turns the participant_query section into numbered steps: search with
participant_query (their @username, or a word of their name) with type
direct and expansions participant_ids, confirm the person from the expanded
participant, keep paging while has_more is true, retry with the @username,
then check message requests, and send through Send or reply with the
match's id.
…ookup-f5dd

Cursor/x guide chat lookup f5dd
…uest-1186-from-santiagomed-cursor-x-guide-chat-6-commits

# Conflicts:
#	README.md
@SmailG SmailG added the sync Automated upstream sync label Nov 7, 2026
@SmailG
SmailG merged commit 5b7c17d into main Nov 7, 2026
2 checks passed
@SmailG
SmailG deleted the sync/merge-pull-request-1186-from-santiagomed-cursor-x-guide-chat-6-commits branch November 7, 2026 12:26
@coderabbitai

coderabbitai Bot commented Nov 7, 2026 •

Copy link
Copy Markdown

Explain Change →

Caution

Review failed

The pull request is closed.

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Tip

🎯 Customize your risk assessments

Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.

✅ Automatic approvals, with your rules

Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

sync Automated upstream sync

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants