Bluesky · from any AI chat

Post to Bluesky from your AI chat.

The least troublesome network here, and the only one where we can check a post really landed instead of believing a provider.

Bluesky takes 300 characters per post and chains multi-part writing into a genuine reply thread of up to 25 posts — not a fan of separate comments hanging off one root, but root to reply to reply, the way a reader expects it. Ask your agent for a thread and that is what appears.

It is also the one network in this set that can be read without logging in, through the public AppView. That sounds like a detail and is not: everywhere else, "your post published" is ultimately something a provider told us. Here we can go and look.

Asking for a Bluesky post

The ceilings in this exchange are read from the same table the publisher enforces, so what the agent says here is what would really happen to your Bluesky post.

Claude07:48

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.

Break the changelog into a thread and put it on Bluesky

attached draft · 640 characters · 1 image

1S

Bluesky chains properly, so this goes out in order:

Bluesky caption3003-part thread
Image or videooptional here
Reply chainsup to 25 parts
Attachments allowed4per post

Published. I read the reply graph back from the public server — it is a real chain.

Message Claude…

What Bluesky allows

Read from the same table the publisher enforces, so this cannot drift from what actually happens when you press send.

Caption limit
300 characters
Post with no image or video
Fine
Reply chains
Yes — up to 25 parts
Images or video per post
4
Image formats
Anything we accept for upload

What you can do with Bluesky from a chat

Threads that are really threads

Root to reply to reply, the way a reader expects — not a fan of separate comments hanging off one post, which is what the documentation predicted.

The one we can verify

Posts here are readable without an account, so a delivery can be confirmed against the network itself rather than against whoever claimed to have made it.

Engagement, minus impressions

Likes, reposts and replies come back into the chat. Bluesky reports no impressions at all, so that column stays empty rather than showing an invented zero.

The mention bug, named

A post containing an @ mention currently fails outright — the handle is sent where an account identifier belongs. Ours to fix, and not hidden while it is open.

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 Bluesky, 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.

We predicted the chain would break, and went and checked

Our publishing provider’s documentation describes multi-part posts as replies to a single root — a flat fan of comments rather than a chain — and their response field is even named after comments. On that reading we wrote into the migration commit that Bluesky chaining would come out wrong. Then a probe published three parts to a live account and read the reply graph back from the public AppView, which no provider controls: root has one reply, and that reply has one reply of its own. A real chain. The documentation was wrong and so was our prediction, and the only reason we know either way is that this network can be independently read.

A limitation of Bluesky itself — it stays true whoever publishes for us. Measured on a live account, 2026-07-27.

When this is the wrong tool

Two rough edges, both ours to own. A post that mentions somebody with an @ currently fails outright, because the handle is being sent where Bluesky expects an account identifier and it rejects the whole record. And deleting a thread removes the root while its replies stay up — we tell you how many parts were left behind rather than reporting a clean delete.

Questions people actually ask

Do Bluesky threads actually chain, or is it separate posts?

They chain. It was verified by publishing three parts and reading the reply graph back from the public AppView rather than from the provider that created them, which is the only way to answer this question without taking somebody’s word for it.

Why did my Bluesky video fail to upload?

Almost certainly an unverified email on the Bluesky account. Video goes through a separate service that checks it, while text and images take another path entirely — so the account looks perfectly healthy and only video fails. We recognise that refusal now and explain it in words instead of passing on a 401.

What analytics come back from Bluesky?

Likes, reposts and replies. Bluesky does not report impressions at all, so there are none to show — an empty column rather than a zero we made up.

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.