Skip to main content

aiogram-cmds

CI PyPI Python versions License

Command management library for aiogram v3 - Manage Telegram bot commands with i18n support, user profiles, and dynamic scopes.

✨ Features

  • Simple & Advanced Modes: Start simple, scale to complex configurations
  • i18n Integration: Built-in support for aiogram i18n with fallback handling
  • User Profiles: Dynamic command sets based on user status (guest, registered, etc.)
  • Multiple Scopes: Support for all Telegram command scopes (private, group, admin, etc.)
  • Auto-Setup: One-call setup with sensible defaults
  • Type-Safe: Full type hints and strict type checking
  • Production Ready: Comprehensive testing, CI/CD, and documentation

📦 Installation

# Basic installation
pip install aiogram-cmds

# With Redis support (for multi-worker deployments)
pip install aiogram-cmds[redis]

⚡ Quick Start

Auto-Setup (Recommended)

from aiogram import Bot, Dispatcher
from aiogram_cmds.auto_setup import setup_commands_auto

async def on_startup():
    # Automatically set up commands with sensible defaults
    command_manager = await setup_commands_auto(bot)
    # Commands are ready to use!

# Your handlers
@dp.message(Command("start"))
async def handle_start(message: Message):
    await message.answer("Welcome! Use /help to see available commands.")

Simple Mode

from aiogram import Bot, Dispatcher
from aiogram_cmds import CommandScopeManager, load_settings, build_translator_from_i18n

# Load settings from pyproject.toml or use defaults
settings = load_settings()
translator = build_translator_from_i18n(i18n)  # Your aiogram i18n instance

# Create manager
manager = CommandScopeManager(bot, settings=settings, translator=translator)

# Set up all command scopes
await manager.setup_all()

# Update user commands dynamically
await manager.update_user_commands(
    user_id=12345,
    is_registered=True,
    has_vehicle=False,
    user_language="en"
)

Advanced Mode

from aiogram_cmds import CmdsConfig, CommandDef, ProfileDef, ScopeDef, MenuButtonDef

# Define your command configuration
config = CmdsConfig(
    languages=["en", "ru", "es"],
    commands={
        "start": CommandDef(i18n_key="start.desc"),
        "help": CommandDef(i18n_key="help.desc"),
        "profile": CommandDef(i18n_key="profile.desc"),
        "admin": CommandDef(i18n_key="admin.desc"),
    },
    profiles={
        "guest": ProfileDef(include=["start", "help"]),
        "user": ProfileDef(include=["start", "help", "profile"]),
        "admin": ProfileDef(include=["start", "help", "profile", "admin"]),
    },
    scopes=[
        ScopeDef(scope="all_private_chats", profile="guest"),
        ScopeDef(scope="chat", chat_id=12345, profile="admin"),
    ],
    menu_button=MenuButtonDef(mode="commands"),
)

# Create manager with custom profile resolver
def my_profile_resolver(flags):
    if flags.is_admin:
        return "admin"
    elif flags.is_registered:
        return "user"
    return "guest"

manager = CommandScopeManager(
    bot, 
    config=config, 
    profile_resolver=my_profile_resolver
)
await manager.setup_all()

🎯 Use Cases

E-commerce Bot

# Different commands for different user states
profiles = {
    "visitor": ProfileDef(include=["start", "catalog", "help"]),
    "customer": ProfileDef(include=["start", "catalog", "cart", "orders", "help"]),
    "vip": ProfileDef(include=["start", "catalog", "cart", "orders", "vip_offers", "help"]),
}

Admin Bot

# Admin commands only for specific users
scopes = [
    ScopeDef(scope="all_private_chats", profile="user"),
    ScopeDef(scope="chat_member", chat_id=12345, user_id=67890, profile="admin"),
]

Multi-Language Bot

# Commands in multiple languages
config = CmdsConfig(
    languages=["en", "ru", "es", "fr"],
    commands={
        "start": CommandDef(i18n_key="commands.start"),
        "help": CommandDef(i18n_key="commands.help"),
    }
)

📚 Documentation

👉 Full Documentation ← Start here!

🏗️ Architecture

aiogram-cmds provides three levels of complexity:

  1. Auto-Setup: Zero configuration, works out of the box
  2. Simple Mode: Settings-based configuration with policies
  3. Advanced Mode: Full control with profiles, scopes, and custom resolvers
┌─────────────────┐    ┌──────────────────┐    ┌─────────────────┐
│   Auto-Setup    │    │   Simple Mode    │    │  Advanced Mode  │
│                 │    │                  │    │                 │
│ setup_commands_ │    │ CmdsSettings +   │    │ CmdsConfig +    │
│ auto()          │    │ CommandPolicy    │    │ ProfileResolver │
└─────────────────┘    └──────────────────┘    └─────────────────┘
         │                       │                       │
         └───────────────────────┼───────────────────────┘
                                 │
                    ┌──────────────────┐
                    │ CommandScopeMgr  │
                    │                  │
                    │ • setup_all()    │
                    │ • update_user()  │
                    │ • clear_user()   │
                    └──────────────────┘

🤝 Contributing

We welcome contributions! See our Contributing Guide for details.

Development Setup

# Clone the repository
git clone https://github.com/ArmanAvanesyan/aiogram-cmds.git
cd aiogram-cmds

# Set up development environment
uv venv
source .venv/bin/activate  # On Windows: .venv\Scripts\activate
uv pip install -e ".[dev]"

# Run tests
uv run pytest

# Run linting
uv run ruff check .
uv run ruff format .

💬 Community & Support

  • 💬 Discussions - Questions, ideas, and community chat
  • 🐛 Issues - Bug reports and feature requests
  • 📖 Documentation - Complete guides and API reference

🔒 Security

For security issues, see SECURITY.md.

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.

🙏 Acknowledgments

  • Built for aiogram v3 - Modern Telegram Bot API framework
  • Inspired by the need for robust command management in production environments

📊 Project Status

  • ✅ Core Features: Command management, i18n, profiles, scopes
  • ✅ Documentation: Comprehensive guides and API reference
  • ✅ Testing: Unit, integration, and performance tests
  • ✅ CI/CD: Automated testing and deployment
  • 🚧 Examples: Working bot examples (in progress)
  • 🔮 Future: Rate limiting, caching, advanced analytics

Made with ❤️ for the aiogram community

Release files for aiogram-cmds 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for aiogram-cmds 0.1.1
File Size Uploaded
aiogram_cmds-0.1.1.tar.gz 274.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for aiogram-cmds 0.1.1
File Interpreter ABI Platform
aiogram_cmds-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 292.6 kB

Release files / aiogram_cmds-0.1.1.tar.gz

Download URL aiogram_cmds-0.1.1.tar.gz
Size 274.6 kB
Tags Source
SHA-256 checksum
How to use checksums
6b8d1f70f3c778adfd578ec2fb600cbd1c36e24cec31ae32926a1ab9c20411c6
BLAKE2b-256 checksum
How to use checksums
87e1394a007e8ec77542bced906bf04181b46a77f89fada2555128759f8cc27a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2025.

Transparency log

Release files / aiogram_cmds-0.1.1-py3-none-any.whl

Download URL aiogram_cmds-0.1.1-py3-none-any.whl
Size 18.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ed12a47fca23ef3e0eb41b5d261c62237268eaf4d9477895c01e822d69bdbf11
BLAKE2b-256 checksum
How to use checksums
70feb73630e9b7e0294e105fed3114528c64540f11750c45b7cb2fceb97296fc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page