A development stage from October 12 to 16, 2026. There is no 0.6.9 package: these changes shipped in
0.7.0.
Sign-in with a code
Where the channel link does not carry the transaction to the bot, the sign-in has a second path: the page shows a short code, and the user sends it to the bot. For Instagram and Messenger the code is offered automatically; under hop mode it is on the phone’s launch page and disappears as soon as the bot answers.BotName sets the bot’s name. The HTTP channel supports a start by a code for
registrations with no owner — see
Start by a code.
The sign-in page and hop mode
- The hop pages and the sign-in page show where the question is waiting.
- Canceling on the sign-in page sends a “declined” receipt to the channel.
- A third QR code mode,
QrMode: UnifiedWithChannels: the shared QR code and the buttons of every channel on the first tab, followed by a tab per channel with its own QR code. - When the sign-in page asks the question (
OnWebPage), the chat gets one message saying the sign-in has started and must be confirmed on the page. - Fixes: the countdown and the live status of the
OnWebPagequestion page, the “Choose another way” button.
The standalone server
The standalone server image includes the Redis stores, event publishing to RabbitMQ and MaxMind GeoIP — switched on by configuration keys, with no build of your own; see Quickstart self-hosted.Samples and documentation
- Google and Apple pseudo-channels —
samples/dotnet/pseudo-channels. - A Claude Code mod with a QR code panel —
samples/claude-code; see Claude Code mod. - The Helio and Nova Stream showcases.
- A new page, You already have a bot.
What to check when you upgrade
Email withLoginConfirmation.Mode = OnWebPage: the sign-in email no longer completes the
sign-in; it only links the mailbox, and the sign-in page decides. “No” there gives
declined_by_user.
The full list is in
What to check when you upgrade from 0.6.1.