Going further

You can now build described, typed, role-gated commands that hot-reload as you edit. Here is the rest of Raito, and where to read about it.

Interactive features

• Keyboards — build inline and reply keyboards declaratively or with a builder. See the keyboards guide.

• Pagination — page through text and media with inline buttons, with no server-side state. See the pagination guide.

• Scenes — multi-step dialogs where every step is an ordinary handler, so request-scoped dependencies (like a database session) are released between messages. See the scenes guide.

• Conversations — pause a handler and wait for the user’s next message. See the conversations guide.

Operational features

• Throttling — rate-limit globally or per-command.

• Albums — receive grouped media as a single list.

• Lifespan — startup/shutdown logic in one async generator.

• Storages — optional JSON and SQL persistence.

Understand the internals

If you prefer to know why things work the way they do, the 💡 Explanation section covers the architecture, the hot-reload mechanism, request-scoped scenes, stateless pagination and the role model.

Look things up

The 📖 Reference has the generated API, every configuration option and the full list of in-chat .rt commands.