Skip to main content
An X search result is a lead. Read the original post when you need its full text, author or URL, and use a thread or replies part when the surrounding conversation matters. Profiles, lists, communities, spaces and articles have separate operations; inspect the relevant one instead of treating a post search as a search of all X content.
The post ID here is a dated public-study example, not a stable recommendation. Search supports native operators and a result type such as Latest or Top; web describe x.post.search and scoped --help show current inputs. A search page and an original-post read are separate provider requests. Carry the returned native post ID or resource target into the read. For the current CLI, multiple --post-id values must be separate flag occurrences. A generated backend example shows comma-separated IDs, but the CLI rejects that form. The September 2026 study recovered with repeated flags:
For replies, quotes or a whole thread, inspect x.post.replies.read, x.post.quotes.read or x.post.thread.read before selecting --part. Keep the source post ID and returned conversation IDs distinct from a search cursor. A public post’s text and author are evidence at retrieval time; the search snippet alone does not establish the full original.