raito 1.1.0

REPL, hot-reload, keyboards, pagination, and internal dev tools — all in one. That's Raito.

🔦 Raito

REPL, hot-reload, keyboards, pagination, and internal dev tools — all in one. That's Raito.

---

Highlights

• 🔥 Hot Reload — automatic router loading and file watching for instant development cycles
• 🎭 Role System — @raito.roles with pre-configured roles (admin, mod, support, etc) and selector UI
• 📚 Pagination — easy pagination over text and media using inline buttons
• 💬 FSM Toolkit — interactive confirmations, questionnaires, and mockable message flow
• 🚀 CLI Generator — $ raito init creates a ready-to-use bot template in seconds
• 🛠️ Command Registration — automatic setup of bot commands with descriptions for each
• 🛡️ Rate Limiting — apply global or per-command throttling via decorators or middleware
• 💾 Database Storages — optional SQL support
• 🧪 REPL — execute async Python in context (_msg, _user, _raito)
• 🔍 Params Parser — extracts and validates command arguments
• 📊 Metrics — inspect memory usage, uptime, and caching stats
• 📃 Logging — view and filter runtime logs without leaving Telegram
• 🧰 Debug Utils — run shell commands, monitor jobs, inspect command states, and more

Installation

pip install -U raito

Quick Start

import asyncio

from aiogram import Bot, Dispatcher
from raito import Raito


async def main() -> None:
    bot = Bot(token="TOKEN")
    dispatcher = Dispatcher()
    raito = Raito(dispatcher, "src/handlers")

    await raito.setup()
    await dispatcher.start_polling(bot)


if __name__ == "__main__":
    asyncio.run(main())

Why Raito?

Raito speeds up your bot development by removing the boring parts — no more boilerplate, no more manual restarts, no more duplicated code across projects.
Everything that used to slow you down is already solved.

Showcases

📦 Handling Commands

You can control access to commands using @rt.roles

The @rt.description decorator adds a description to each command — they will show up in the slash menu automatically.

For commands like /ban 1234, use @rt.params to extract and validate the arguments.

@router.message(filters.Command("ban"))
@rt.roles(rt.Role.OWNER, rt.Role.ADMINISTRATOR, rt.Role.MODERATOR)
@rt.description("Ban a user")
@rt.params(user_id=int)
async def ban(message: types.Message, params: rt.Params, bot: Bot):
    if not params.user_id:
        await message.answer("Please provide a user ID.")
        return

    await bot.ban_chat_member(chat_id=message.chat.id, user_id=params.user_id)
    await message.answer(text="✅ User banned successfully!")

---

🔥 Hot-Reload & Router Management

Whenever you change a file with handlers, Raito automatically reloads it without restarting the bot.

You can also manage your routers manually using the .rt load, .rt unload, .rt reload, or .rt routers commands in the bot.

https://github.com/user-attachments/assets/c7ecfb7e-b709-4f92-9de3-efc4982cc926

---

🎭 Roles

Use built-in roles to set different access levels for team members.

---

📚 Pagination

The simplest, most native and most effective pagination. Unlike many other libraries, it does not use internal storage.
It is very user-friendly and fully customizable.

@router.message(filters.Command("pagination"))
async def pagination(message: Message, raito: rt.Raito, bot: Bot):
    if not message.from_user:
        return

    await raito.paginate(
        "button_list",
        chat_id=message.chat.id,
        bot=bot,
        from_user=message.from_user,
        limit=5,
    )


BUTTONS = [
    InlineKeyboardButton(text=f"Button #{i}", callback_data=f"button:{i}")
    for i in range(10000)
]

@rt.on_pagination(router, "button_list")
async def on_pagination(query: CallbackQuery, paginator: InlinePaginator, page: int, limit: int):
    content = BUTTONS[(page - 1) * limit : page * limit]
    await paginator.answer(text="Here is your buttons:", buttons=content)

Contributing

Have an idea, found a bug, or want to improve something?
Contributions are welcome! Feel free to open an issue or submit a pull request.

Security

If you discover a security vulnerability, please report it responsibly.
You can open a private GitHub issue or contact the maintainer directly.

There’s no bounty program — this is a solo open source project.
Use in production at your own risk.

For full details, check out the Security Policy.

Questions?

Open an issue or start a discussion in the GitHub Discussions tab.
You can also ping @Aidenable for feedback or ideas.