This release is a pre-release and may not be stable for production use.
ErisPulse
Write once, deploy on multiple platforms.
An event-driven, multi-platform chatbot development framework based on the OneBot12 standard.
Overview
ErisPulse is an event-driven, modular async framework for building chatbots that run on multiple platforms from a single codebase. It implements the OneBot12 standard event model, so you write command handlers, conversation flows and message senders once — then deploy them to QQ, Telegram, Discord, Kook, Yunhu, Matrix, Email, WeChat and more without touching business logic.
It ships with a flexible plugin system, hot reload, a visual Dashboard, an AI Builder that turns natural-language prompts into modules, and the epsdk CLI scaffolding tool — suitable for everything from a simple chatbot to a complex automation pipeline.
Key Features
- Event-driven architecture — Clear event model based on OneBot12, making message handling intuitive and consistent across platforms.
- Cross-platform compatibility — Write handlers once, deploy to 15+ platforms without rewriting business logic.
- Modular design — Flexible plugin system with hot-plug module management and per-module configuration.
- Hot reload — Local plugins reload on save; any module (including PyPI-installed ones) hot-reloads via a single
sdk.reload_module()call — no process restart, even after pip upgrades. - Unified Event Overrides — Override message triggers, command params and user permissions for every event type with a single config — no module code changes, takes effect instantly.
- Scope Control — Three-dimensional scope (module availability / event admission / outbound limits) with runtime-adjustable fine-grained control.
- Chainable SendDSL — Express
@mention, reply, retry, timeout, progress hook and bulk send as a single fluent chain. - Complete toolchain —
epsdkCLI, visual Dashboard, AI Builder and Module Market included out of the box.
Installation
Option 1 — pip (for library / module developers)
pip install ErisPulse
For a global epsdk CLI without any virtual environment, use uv tool install ErisPulse instead.
Option 2 — Docker (recommended for production)
docker pull erispulse/erispulse:latest
Quick start with docker-compose.yml:
curl -O https://raw.githubusercontent.com/ErisPulse/ErisPulse/main/docker-compose.yml
ERISPULSE_DASHBOARD_TOKEN=your-token docker compose up -d
The image bundles the ErisPulse framework and the Dashboard management panel, supporting linux/amd64 and linux/arm64. After startup, visit http://<host>:<port>/Dashboard and log in with the token you set.
Docker Hub unavailable? Use GitHub Container Registry
docker pull ghcr.io/erispulse/erispulse:latest
And update the image in your docker-compose.yml:
image: ghcr.io/erispulse/erispulse:latest
Docker environment variables
| Variable | Default | Description |
|---|---|---|
ERISPULSE_CHANNEL |
stable |
Version channel: stable or dev (pre-release) |
ERISPULSE_UPDATE_ON_START |
false |
Auto-update to the latest version on container start |
ERISPULSE_DASHBOARD_TOKEN |
empty | Dashboard login token |
ERISPULSE_PORT |
8000 |
Dashboard port mapping |
TZ |
Asia/Shanghai |
Container timezone |
Option 3 — One-click install script (auto-detects environment)
The installer detects Docker / Python / uv and guides you through the most suitable setup. Supports Chinese, English, Japanese, Russian and Traditional Chinese.
Windows (PowerShell):
irm https://get.erisdev.com/install.ps1 -OutFile install.ps1; powershell -ExecutionPolicy Bypass -File install.ps1
macOS / Linux:
curl -fsSL https://get.erisdev.com/install.sh -o install.sh && chmod +x install.sh && ./install.sh
Quick Start
Initialize a new project:
# Interactive initialization
epsdk init
# Quick initialization with a project name
epsdk init -q -n my_bot
Create a main.py file:
from ErisPulse import sdk
from ErisPulse.Core.Event import command
@command("hello", help="Send greeting message")
async def hello_handler(event):
user_name = event.get_user_nickname() or "friend"
await event.reply(f"Hello, {user_name}!")
@command("ping", help="Test if the bot is online")
async def ping_handler(event):
await event.reply("Pong! The bot is running normally.")
if __name__ == "__main__":
import asyncio
asyncio.run(sdk.run(keep_running=True))
Run it:
epsdk run main.py
# Or in development mode with hot reload
epsdk run main.py --reload
Now send /hello or /ping to the bot on any connected platform — the same handlers work everywhere.
For the full walkthrough (multi-turn conversations, request handlers, adapter configuration), see the Quick Start guide.
The SendDSL — fluent message sending
Compose the entire send flow — @mention, reply, retry, timeout, progress hook and bulk dispatch — as one readable chain:
yunhu = sdk.adapter.get("yunhu")
# Single send: @user + reply + retry + timeout + success callback
await (yunhu.Send.To("group", "123")
.At("456").Reply("msg_789")
.Retry(3).Timeout(10)
.Hook(lambda r: print("Send successful!"))
.Text("Hello"))
# Bulk send: build multiple messages, then dispatch in one chain
results = await (yunhu.Send.To("user", "123")
.Build()
.Text("Notification 1")
.Image("pic.jpg")
.Retry(2)
.send_all())
Supported chainable methods include Hook (success callback), Retry (failure retry), Timeout (timeout cancellation), OnProgress (progress monitoring), Defer (delayed send) and Build (batch construction).
Full reference: SendDSL documentation
Supported Platforms
Officially maintained adapters (community contributions welcome):
- Kook — instant messaging platform
- Matrix — decentralized communication protocol
- OneBot11 — universal OneBot v11 protocol
- OneBot12 — OneBot v12 standard protocol
- QQ Bot — official QQ bot platform
- Telegram — global instant messaging
- Discord — community communication platform
- Yunhu / Yunhu User — enterprise IM
- Email — email protocol adapter
- WeChat Official Account
- Webhook — HTTP bridge to any system
- Sandbox — in-browser debugging, no real platform needed
- HuaFeng Coffee House
See the adapter guide for configuration details.
Ecosystem
- Framework — core runtime with a unified event & message model.
- Dashboard — visual management for plugins, logs and configuration. (live demo)
- AI Builder — natural-language prompts → ready-to-use modules. (try it)
- Module Market — plug-and-play community plugins. (browse)
- CLI —
epsdkscaffolding, project init, run and reload. - Docker — multi-architecture images at
erispulse/erispulse.
Documentation & Community
- 📖 Documentation & API reference: erisdev.com
- 💬 GitHub Discussions: ErisPulse/ErisPulse/discussions
- 📋 Changelog: CHANGELOG.md
- 🤝 Contributing: CONTRIBUTING.md
- 🐛 Bug reports: GitHub Issues
- 🧠 DeepWiki: deepwiki.com/ErisPulse/ErisPulse
Chat with us on:
- Telegram: https://t.me/ErisPulse
- QQ Group: https://qm.qq.com/q/TOwnCmypcy
- Yunhu Group: https://yhfx.jwznb.com/share?key=VWJL4fTWXepa&ts=1781889199
Why ErisPulse? Because platform differences should never be your bottleneck — focus on business logic, and let the framework handle the rest. Write once, deploy everywhere.
1 maintainer
Metadata
1 maintainer
Release files for ErisPulse 2.11.0.dev0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| erispulse-2.11.0.dev0.tar.gz | 846.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| erispulse-2.11.0.dev0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.8 MB
Release files / erispulse-2.11.0.dev0.tar.gz
| Download URL | erispulse-2.11.0.dev0.tar.gz |
|---|---|
| Size | 846.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0e3a4e780c7ef2ea0131abc3aea5609a6ecb0a29917d2c69046e6a218281b143
|
|
BLAKE2b-256 checksum How to use checksums |
30f48b0dcb13fa691ffa38fd55508c38814e3de8a5f16cb70d8c833bdf54eaf0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 20, 2026.
Transparency logRelease files / erispulse-2.11.0.dev0-py3-none-any.whl
| Download URL | erispulse-2.11.0.dev0-py3-none-any.whl |
|---|---|
| Size | 938.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d1c12fb5a94912b34e2d41b045c88f2af2621e9a3bbc9ecccca1fec580ce2c6b
|
|
BLAKE2b-256 checksum How to use checksums |
5e086f4219337ed3a4482026dd573d5d8a4e2f5eca87742e73acc103ce200beb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 20, 2026.
Transparency logSecurity for ErisPulse 2.11.0.dev0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for erispulse-2.11.0.dev0.tar.gz
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 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
