X thread
Your X thread
Paste your X thread. Nothing to upload.
←X thread
Make a mind map
Turn an X thread into a mind map
A thread is a straight line. The thinking underneath it almost never is.
Free to try, no card. Your X thread opens in Ancher.
Posts in orderAttached imagesAuthor and profile
Kept in parts
Every one of these stays separately addressable instead of collapsing into one block of text.
CentreBranchesCross-linksGaps
Mind map
The structure of an argument, laid out so the shape is visible at a glance.
The format forces a linear order on an argument that has none: a thread cannot fork, so an author flattens a branching idea into a sequence and drops whatever will not fit the line. Ancher puts the claim the thread is really defending at the centre, branches the supporting arguments off it, draws the cross-links where a later post depends on an earlier one, and marks the branches the author opened and abandoned.
The honest version
The format cannot fork, so the author flattened something that branched
When an argument has three parallel strands, a thread has to pick an order and pretend one leads to the next. That transition is written to look like reasoning and frequently is not. The map recovers what was parallel and what actually depended on what, which is the shape the author was working from before the character limit got involved.
One post in one thread, at post 10/15, read two ways.Illustrative. The figure is invented; the gap it falls into is not.
10/ I'll come back to the second point, but first
In the attached diagram — not readThe specific never reaches the draft
Mind map
In the attached diagram
Three-stage loop, stage 2 unresolved
from post 10/15
Lands in the draft, with its timecode
- The centre is the claim the thread keeps returning to, not the one in post one.
- Cross-links are drawn wherever a later post depends on an earlier one, which is what makes it a map rather than a list.
- Threads that end with "more on this later" leave an open branch, and it stays on the map as a gap.
What comes out
Mind map, section by section
The structure of an argument, laid out so the shape is visible at a glance.
Centre
The claim the thread keeps returning to, which is rarely the one it opens on.
Branches
Supporting arguments as branches, restoring the ones the thread had to serialise.
Cross-links
Cross-links wherever a later post depends on an earlier one, drawn rather than described.
Gaps
Branches opened and never closed, including every promise to come back to something.
Legend
What a line means here, plus the author and the thread, so the map travels on its own.
Thread-to-mind-map prompt
The link on its own gets a summary. This is the instruction that produces the 5 sections above, in that order, with the rules that keep them honest. Paste it with your X thread — in Ancher, or in whatever assistant you already use.
Map this thread. (1) Put the claim it keeps returning to at the centre, not the opening post. (2) Branch the supporting arguments, restoring anything the format forced into a sequence that was actually parallel. (3) Draw a cross-link wherever a later post depends on an earlier one and say what the dependency is. (4) Mark every branch opened and never closed as a gap, including promises to return to a point. (5) Include a legend with the author. Keep it under thirty nodes.
The detail, if you want it
How each part of an X thread becomes a section
| From the X thread | Into | Why |
|---|---|---|
| Posts in order | Cross-links | Back-references — as I said in post four, this connects to — are literal text, and each one is an edge on the map. |
| Posts in order | Centre | How many posts a claim occupies is a better centre than the opening hook, which was written to stop a scroll. |
| Attached images | Branches | Authors often attach their own diagram, and a structure someone drew to explain their own argument beats any structure inferred from words. |
| Posts in order | Gaps | Promises to return to a point are easy to find and almost never kept, which is exactly what makes them worth marking. |
| Author and profile | Legend | The legend carries the author and the thread, so a map shared on its own still says whose argument it is. |
Everything Ancher keeps from an X thread
Posts in order
A thread is a sequential argument; read out of order it stops meaning anything.
Attached images
On X the chart usually carries the claim while the text carries the opinion, so the image is the part worth keeping.
Author and profile
Whether the author builds the thing or sells against it changes how the claim should be weighted.
Outbound links
Threads cite primary sources more often than they get credit for, and those links are the way past the hot take.
Likes, replies, reposts
Reach separates a thread the field actually argued about from one nobody read.
The four steps
- Add the X thread. Paste the post URL. Ancher reads the thread in order and keeps the attached images, the author, the outbound links, and the engagement counts together as one source.
- Nothing gets flattened. Posts in order, attached images, author and profile, outbound links, likes, replies, reposts stay separately addressable instead of collapsing into one block of text.
- Ask for a mind map. Ancher fills centre, branches, cross-links, gaps, legend using the mapping above, not a generic summary pass.
- Check it before you use it. Every specific keeps a link back to where it came from in the X thread, so a claim can be verified without reopening the source.
Where this goes wrong
- A map with no cross-links is the thread drawn sideways. If nothing connects across branches, only the sequence was captured and not the structure.
- Threads are written to persuade, so the transitions are smoother than the logic. A gap on the map is often a real gap in the argument, not an extraction error.
- Long threads make wide maps. Past thirty nodes it stops being one screen and becomes a diagram you have to navigate, which defeats the point.
Questions people ask
How is this different from just listing the posts?
A list can only show order. A map can show that post nine depends on post three, which is usually the actual insight in a threaded argument and the thing the linear format was never able to express.
What if the author attached a diagram?
Then that becomes the skeleton. A diagram someone drew to explain their own thinking is a better structure than anything inferred from the words around it, and it is kept with the post it came from.
Does it show where the argument is weak?
It shows where branches were opened and never closed, which is frequently the same thing. It does not judge the reasoning — it makes the shape visible so you can judge it yourself.
Bring your own X threads
Everything you save lives in one workspace, so the mind map is built from your sources — not from a model's memory of the internet.
Open Ancher →Not an X thread? The same mind map also comes from YouTube video, LinkedIn post, Instagram post.