Release detail
Thread composer
The release added a composer for drafting multiple connected posts.
Bluesky Thread Reader
Read returned ancestors and nested replies as a source-linked conversation you can copy or export.
Paste a post URL
Use any public bsky.app post URL or at:// post URI.
Paste a supported public link.
The returned result appears here.
Follow returned parents and reply branches without flattening them.
A post viewer answers what one record says. A thread reader also keeps the returned parent chain and reply branches, so the conversation can be read, checked, and exported without losing who said what.
Thread example
Open the source thread on Bluesky
Bluesky 1.93 release thread
Bluesky
@bsky.app
Selected post in a public release thread
This example starts at post 1 of Bluesky's 1.93 release and follows its details into connected posts and replies.
- Selected record
- Post 1 of the release thread
- Published
- November 8, 2024
- Record key
- 3lahjxmqajk2p
- Context
- Selected post + available reply branches
Release detail
Content-warning controls
The update made self-labeling tools easier to understand and added a Graphic Media label.
Release detail
Interface and playback fixes
The release graphic also notes link-card, image, and video playback improvements.
Ancestor context
See the public parent chain returned above the selected post, in order, so a reply does not lose the conversation that led to it.
Nested reply tree
Follow self-thread continuations and cross-author reply branches with visible depth, authors, dates, media, metrics, and original post links.
Thread export
Copy or download Markdown that keeps the returned posts in reading order with authors, dates, depth labels, and source URLs.
A thread is useful only when its branches stay legible.
CarryFeed keeps the returned public fields and original source close. Missing or unavailable fields stay missing.
- 01
Post URL
Read from a shared Bluesky link. The selected post, returned ancestor context, and nested public replies below that record.
- 02
Reply URL
Start in the middle of a conversation. The returned parents above the reply plus the reply subtree below it.
- 03
AT URI
Resolve the protocol record directly. The same public thread lookup with the selected record's URI, CID, DID, and rkey preserved.
Official field guides: Viewing threads ยท AT URI scheme.
Use it when a Bluesky conversation needs to leave the feed.
Read a long self-thread
Follow an author's continuation posts in sequence without mixing them into an unrelated profile feed.
Review a conversation
Keep cross-author branches and their original URLs visible when preparing research, support notes, or a handoff.
Give the thread to an AI tool
Export readable Markdown with source attribution instead of asking an agent to infer the conversation from a screenshot.
Bluesky Thread Reader questions.
What can I paste into the Bluesky Thread Reader?
Paste a public bsky.app post or reply URL, or an at:// URI for an app.bsky.feed.post record. Handles and profile URLs belong in the Bluesky Viewer tab.
Can I start from a reply in the middle of a thread?
Yes. CarryFeed shows the public ancestor chain returned above that reply and the nested public replies returned below it.
Does it read nested replies or only the first level?
It renders multiple returned reply levels as branches. The request and page are deliberately bounded, so a very deep or large tree can show a truncation boundary.
Can it unroll a Bluesky self-thread?
Yes. Continuation posts by the selected post's author are labeled inside the same returned tree, while replies by other authors remain separate branches.
Is this the complete historical thread?
No tool should promise that. It is the public parent and reply context returned by Bluesky at lookup time, within the reader's depth and node limits.
What happens to blocked, deleted, or unavailable replies?
CarryFeed shows the returned blocked, not-found, or unavailable state as a stop in that branch. It does not reconstruct missing text.