Bluesky launched group chats in June 2026, extending its direct messaging system to support multi-person conversations. On the surface it is a catch-up feature – every competing platform has had this for years. Underneath, it is one of the more strategically interesting things Bluesky has shipped.
How They Work
Group chats build on Bluesky's existing DM infrastructure, which is worth understanding because it explains both the capabilities and the limits.
- Multi-person conversations in the Chats tab, alongside your one-to-one DMs.
- You control who can add you through the same settings that govern who can DM you – everyone, people you follow, or nobody.
- Not on the public timeline. Nothing said in a group chat is published as a post record.
- Not end-to-end encrypted. This matters and we cover it below.
If you have used DMs on Bluesky, the mental model transfers directly. Our chat and direct messages guide covers the underlying system, including how it differs architecturally from the rest of the AT Protocol.
The Architectural Wrinkle Worth Knowing
Bluesky's messaging does not work like the rest of the platform. Posts, likes, follows and lists are public records on the AT Protocol, replicated across the network and streamed over the firehose. Messages are not. They run through a separate service with a different data model.
Two consequences:
- Group chats are not federated the way posts are. They do not portably move with your repository in the way your posting history does.
- They are private from other users, not private from the service. Without end-to-end encryption, "private" means "not publicly readable." For most conversations that is entirely fine. For anything genuinely sensitive, use a tool built for that purpose.
This is a reasonable engineering trade – building federated, encrypted group messaging on a public-record protocol is genuinely hard – but it is worth being clear-eyed about what you are getting.
Why This Is a Strategic Shift
Bluesky's 2026 roadmap was almost entirely about engagement rather than acquisition, and group chats fit that squarely.
The platform's core problem is well documented: roughly 45 million registered accounts against a few million daily actives, with daily engagement below its June 2025 peak. Public-timeline products retain users through habit, and habit is fragile. Private group conversation retains users through obligation – you check a group chat because people are waiting for you, not because an algorithm served you something good.
Every major social platform eventually discovered that private messaging is where the durable engagement lives. Bluesky arriving at the same conclusion in 2026 is unsurprising, and probably correct.
The counterargument
Group chats move conversation off the public timeline. A fandom that used to theorize in public replies and now does it in a group chat produces a quieter, less discoverable platform – even as its users become more retained. That is a real tension, and it means the effect on any metric a third party can measure is genuinely ambiguous. It may be that engagement improves while the platform looks less busy.
What Group Chats Are Actually Good For
Fandom and show communities
Already the most visible adoption. Live-watching a show or a game in a group chat is a better experience than the public tag, and it dodges the spoiler problem entirely.
Small professional communities
The tech and academic communities that make up a large share of Bluesky's active base have been running this pattern in other tools for years. Consolidating it here has obvious appeal.
Event coordination
Conference meetups, watch parties, local groups. The kind of thing that previously required a reply thread that everyone lost track of.
Group DMs that were already happening badly
People were faking group chats with mass-mention reply threads. Those were terrible for everyone, including the people who got mentioned. This is strictly better.
Managing the Downside
Group chats are a new harassment surface, and it is worth setting yours up deliberately:
- Check who can add you. Restricting to people you follow eliminates most of the problem before it starts.
- Leaving is always available and does not require an explanation.
- Blocks still apply. Someone you have blocked cannot pull you into a chat.
- Mute noisy chats rather than leaving, if you want to stay reachable without the notifications.
For broader moderation control, our guides to labelers and content filters and moderation lists cover the rest of the toolkit.
For Developers
Because chat runs on separate infrastructure rather than as AT Protocol records, group chats do not appear on the firehose and are not accessible through the standard record endpoints. If you are building tooling, this is a different API surface with different rules – see our chat API guide.
Practically: do not expect to build group chat features against the same patterns you use for firehose or Jetstream consumption. It is a separate system.
Frequently Asked Questions
How many people can be in a Bluesky group chat?
There is a per-chat participant cap. It is sized for small groups rather than broadcast channels – this is a group chat feature, not a Discord replacement.
Are Bluesky group chats encrypted?
Not end-to-end. They are private from other users but not from the service operator. Use a purpose-built encrypted messenger for sensitive conversation.
Can I be added to a group chat without consent?
Only by people your DM settings permit. Restricting to people you follow prevents unwanted additions.
Do group chats appear on the firehose?
No. Messages run on separate infrastructure and are not published as public AT Protocol records.
Can I use group chats in third-party clients?
Support depends on the client and on the chat API surface it implements. Check your client's release notes.
Get More from Bluesky
- Skyscraper for iOS – free Bluesky client with trending hashtags, pinned tags and multi-account support
- Trending Hashtags – see what the public timeline is doing
- Keyword Alerts – monitor topics that matter to you