Summary

The upstream lexicon now ships a full chat.bsky.group.* namespace (group lifecycle, membership, join links, join requests) plus a chat.bsky.embed.joinLink embed object. None of these are reflected in ATProtoKit, so group conversation management is unreachable through the typed pipeline.

Pain points

The entire group surface (lifecycle, membership, join links, join requests, and the messageInput.embed join-link) has to be hand-built on raw XRPC, re-implementing the api.bsky.chat routing and auth plumbing that ATProtoBlueskyChat already handles for every other chat call.

Considered Alternatives

Raw XRPC for the entire group surface — loses typed pipeline, isRelatedToBskyChat host routing, and forces every consumer to repeat the same auth plumbing.

Is this a breaking change?

No

Library Examples

N/A

Additional Context

Missing lexicons

Wrappers follow the existing ATProtoBlueskyChat convention (method name mirrors the lexicon's final segment, no artificial Group prefix — matching getConversation, listConversations). All sit on api.bsky.chat and require isRelatedToBskyChat: true routing, and the group namespace maps to ChatBskyLexicon.Group.

Cross-reference

• The convo-side discriminator (convoView.kind → #groupConvo) and the 4 convo-level endpoints (getConvoMembers, listConvoRequests, lockConvo, unlockConvo) are tracked in a separate feature request [Feature Request]: Add chat.bsky.convo reply and group conversation support #320.

References

• Lexicon root: https://github.com/bluesky-social/atproto/tree/main/lexicons/chat/bsky/group
• chat.bsky.embed.joinLink: https://github.com/bluesky-social/atproto/blob/main/lexicons/chat/bsky/embed/joinLink.json
• Affected directories: Sources/ATProtoKit/Models/Lexicons/chat.bsky/Group/ (new), Sources/ATProtoKit/APIReference/ChatBskyAPI/ (new method files)