Threads · from any AI chat
Post to Threads from your AI chat.
Publishing works, analytics come back, and the two things that do not work are our publishing provider’s fault rather than the network’s. Both are listed below.
Threads takes 500 characters and up to 10 attachments, including video — fragmented MP4 with Opus audio published without complaint, which is more than several better-established networks manage. Text posts, images and video all go out through Meta’s own API on a connection you approved in a browser.
This page spends more words than the others on what does not work, for a reason. Threads is where the gap between a network’s capabilities and a publishing provider’s permissions is widest, and telling those apart is the difference between a limitation that will disappear one day and one that never will.
Asking for a Threads 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 Threads post.
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.
Send the announcement to Threads with the cover image
attached draft · 640 characters · 1 image
Before it goes, what Threads will and will not do with it:
Published. If you want it removed later, that will have to be done by hand — I cannot.
What Threads allows
Read from the same table the publisher enforces, so this cannot drift from what actually happens when you press send.
- Caption limit
- 500 characters
- Post with no image or video
- Fine
- Reply chains
- No — the parts are joined into one post
- Images or video per post
- 10
- Image formats
- Anything we accept for upload
What you can do with Threads from a chat
Publishing works properly
Text, pictures and video all go out through Meta’s own API, including video encodings that several better-established networks turned down.
Metrics come back
Views, likes, replies and reposts read back into the conversation. Quote counts arrive in a shape our mapper does not reach yet, so that one is absent rather than zero.
Joined rather than failed
A multi-part post is combined into one and measured against the ceiling as a whole — the outcome that publishes, instead of the one that fails on every attempt.
Two gaps, both attributed
No reply chains and no deletion, and neither is the network’s doing. Both are permissions our publishing provider’s app does not hold, so both can go away.
How it works
Connect once
~2 minLink the accounts you use in a browser. OAuth, no passwords typed into a chat, no API keys to paste anywhere.
ChatGPT
Claude
Cursor
Ask, in your own words
one sentenceTell your AI chat to publish to Threads, now or on a day you name. No dashboard, no tab switch.
Read the receipt
per networkOne line per network — what landed, what failed and why, and what genuinely could not be determined.
Threads can thread. We cannot thread on it.
The network obviously supports reply chains — it is in the name. The app our publishing provider uses to post on your behalf does not have permission to create one: it holds exactly three permissions, and none of them covers posting a reply, so every multi-part post aimed here failed with the same refusal and was then retried three more times for good measure. Isolating it took two publishes, after a first guess wrongly blamed the video. So a multi-part post is joined into one instead, which publishes, with the 500-character ceiling checked against the joined text before it is sent. The day that permission is granted, this paragraph gets rewritten — and there is a test whose job is to fail on that day so nobody forgets.
A limitation of our publishing provider, not of Threads — it goes away if we move. Measured on a live account, 2026-07-27.
When this is the wrong tool
A published Threads post cannot be removed by us either — the delete permission is missing in the same way the reply permission is, and the request comes back as a server error every time. We say the post is still live rather than deleting our own copy and calling it done. If removing posts programmatically matters to you, Threads is the wrong network to rely on here.
Questions people actually ask
Why does my multi-part post arrive as one Threads post?
Because the app publishing for you is not permitted to create replies. Joining is the outcome that actually publishes; the alternative is failing every time. It is a limitation of our publishing provider rather than of Threads, and it is expected to go away.
Does Threads accept PNG images?
Yes. PNG and JPEG both publish. When a Threads image is refused it is almost always the proportions rather than the format — a wide banner comes back as an invalid aspect ratio while a square PNG of the same picture goes through.
What Threads metrics can I read back?
Views, likes, replies and reposts. Quote counts are present in the raw response but arrive nested in a way our mapper does not reach yet, so that one number is simply absent rather than shown as zero.
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.