nonebot/nonebot2

跨平台 Python 异步聊天机器人框架 / Asynchronous multi-platform chatbot framework written in Python

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 7 minutes ago
Added to GitGenius on September 8th, 2026
Created on August 23rd, 2020
Open Issues & Pull Requests: 34 (+0)
GitHub issues: Enabled
Number of forks: 663
Total Stargazers: 7,705 (+0)
Total Subscribers: 29 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 17
New in 7 days: 8
Closed in 7 days: 7
Avg open age: 343 days
Stale 30+ days: 7
Stale 90+ days: 7

Recent activity

Opened in 7 days: 7
Closed in 7 days: 7
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Plugin (504)
  • Publish (434)
  • Bot (17)
  • invalid (15)
  • Adapter (13)
  • question (11)
  • enhancement (9)
  • wontfix (8)

Most active issues this week

Detailed Description

NoneBot is an asynchronous Python framework for building chatbots that work across multiple messaging platforms.

The framework addresses the challenge of developing bots that need to operate on different chat services without rewriting core logic for each platform. NoneBot uses an adapter-based architecture where platform-specific implementations are abstracted behind a common interface. Developers write bot logic once using NoneBot's event handling and plugin system, then deploy to multiple platforms by selecting the appropriate adapters. The framework is built on async/await patterns to handle concurrent message processing efficiently.

Teams should adopt NoneBot if they need to maintain bots across platforms like QQ, Telegram, DingTalk, Lark, or others without duplicating business logic. It suits projects where the same conversational rules, command handling, and response logic should work identically regardless of which chat service users connect through. The plugin architecture allows modular bot features that can be shared and reused across different deployments.

The project maintains active development with regular updates to core functionality and adapter support. The codebase shows consistent refinement of the plugin system and event handling mechanisms. Documentation and examples receive ongoing attention to help new users understand the framework's patterns. The maintainers actively expand platform coverage by adding and updating adapters for emerging chat services.