Threads on X and Bluesky, written once.

Two of these networks chain replies and the rest do not. You write the parts; where they land as a chain is not your problem.

Publishes to all seven

InstagramTikTokLinkedInXBlueskyThreadsFacebook

Instagram and TikTok need an image or video — they have no text-only post. We tell you before you publish, not after.

A long piece has a different shape on every network. On the two that support reply chains it should arrive as a chain, in order, each part inside the ceiling. On the ones that do not, the same piece has to be joined into a single post — and on the network with the most room that is usually the better outcome anyway, because the whole thing fits comfortably.

You write the parts once and say where it goes. Each part is counted against the relevant ceiling before anything is sent, so an overflow is a sentence in your chat rather than a truncated post somebody else reads. Where the parts are going to be joined, the joined length is what gets checked — which is not the same test, and getting that wrong has consequences.

Where a thread stays a thread

The figures in this exchange are read from the same table the publisher enforces — the networks really do disagree with each other this much.

Claude07:15

Set me up — what do you need?

Just the accounts. Connect them in the browser once and I can publish from here after that.

Done, connected

I will tell you before publishing if a network cannot take what you wrote.

Good. Drafting the launch note now

Send it over and I will check it before anything goes out.

Turn the postmortem into a thread and put it out wherever threads actually work

four parts · no media

1S

Different networks do different things with this:

Xchains, up to 25
Blueskychains, up to 25
Threadsjoined into one
LinkedInjoined into one
Facebookjoined into one

Sent. Where it chained it is a real chain; where it joined, the joined length was what I checked.

Message Claude…

What this actually does for you

A chain where one is possible

On the networks that support it the parts arrive in order, each a reply to the last, rather than as separate posts that happen to share a topic.

Measured the way it will be sent

Parts that will chain are checked individually and parts that will be joined are checked as one piece. Those are different tests, and using the wrong one loses text.

One answer, read by both sides

The check and the publisher read a single switch, so they cannot disagree about whether something threads — which is exactly how a post once went out three quarters missing.

Only two of them, honestly

Everywhere else the parts are joined into one post. Where we have enabled chaining without proving it on a live account, that page says so.

How it works

1

Connect once

~2 min

Link the accounts you use in a browser. OAuth, no passwords typed into a chat, no API keys to paste anywhere.

ChatGPT

Claude

Cursor

2

Ask, in your own words

one sentence

Tell your AI chat to publish to every network you picked, now or on a day you name. No dashboard, no tab switch.

3

Read the receipt

per network

One line per network — what landed, what failed and why, and what genuinely could not be determined.

The post that lost three quarters of itself and reported success

There was a version of this where the check and the publisher disagreed about what a thread was. The check validated each part separately, found all of them inside X’s ceiling, and approved the post. The publisher then joined those parts into one long piece and sent it, X truncated it without complaint, and we recorded a success. Somebody’s writing went out with three quarters missing and nothing anywhere said so. There is now a single switch that both the check and the publisher read, so the question “does this thread” has exactly one answer, and that answer is about what happens right now rather than what a network is capable of in principle.

A limitation of this product. Ours to fix. Measured on a live account, 2026-07-26.

When this is the wrong tool

Only two of the networks here produce a real chain, and on one of those we have enabled chaining without yet proving it end to end on a live account. Everywhere else a multi-part post is joined into one. If a genuine reply chain on a specific other network is what you need, this cannot give you one.

Questions people actually ask

Which networks actually chain replies?

Bluesky does, verified by publishing a chain and reading the reply graph back from a public server rather than trusting the tool that made it. X is enabled and has not been proved live yet, and we say so on its page rather than letting you assume.

What happens on a network that cannot chain?

The parts are joined into one post and the joined length is what gets checked against the ceiling. On the roomier networks that is invisible; where it would overflow, you hear about it first.

How many parts can a chain hold?

Enough for any thread a person will actually write in a chat window — the exact ceiling is shown on each network’s own page, read from the same table the publisher enforces.

Something else? Ask us — a person answers.

Read next

Start where you already work.

Connect an account and post your first update in about two minutes. The first 30 deliveries each month are free.

Posts go out through each network’s official API — not scraping.