Connect Bluesky with an app password

Any account created at bsky.app works — a default handle like yourbrand.bsky.socialor a custom-domain handle you’ve verified. Accounts hosted on a third-party server (a self-hosted PDS) aren’t supported yet; if that’s you, the connect step will say so rather than fail silently.

On bsky.app/settings/app-passwords (Settings → Privacy and security → App passwords) click Add App Password, name it something you’ll recognise later (“Rebbel” is fine) and leave Allow access to your direct messagesunticked — Rebbel never reads or sends DMs. Bluesky shows the code once, in the shape xxxx-xxxx-xxxx-xxxx. Copy it now; if you lose it, just delete it and make another.

In Rebbel open your brand → Connections→ the Bluesky section. Enter your handle (or the email on the account) and paste the app password, then Connect Bluesky. The row turns Healthy the moment Bluesky accepts the sign-in. Rebbel keeps the session token, not the app password itself, and refreshes it quietly in the background.

Text posts, with up to four images attached. Bluesky caps a post at 300 characters, so Rebbel drafts Bluesky copy to fit and shows the count while you edit. Video isn’t supported on Bluesky yet — a video-only post can’t be sent there, and Rebbel tells you so before it tries. Every post still goes through the same approval step as every other channel: nothing publishes until you say yes.

Delete the app password on the same Bluesky settings page. Rebbel’s next check marks the connection “Needs reauth”, holds any scheduled Bluesky posts rather than failing them, and releases them once you connect again. Disconnecting from Rebbel’s side works too — the Disconnect button on the row — but deleting the app password is the one that cuts access at the source.