What is HyperCore?

HyperCore abstracts the repeated setup work around Telegram automation so each bot can focus on its behavior instead of rebuilding the same foundation.

By unifying client initialization, module loading, and event routing into a single infrastructure layer, HyperCore allows multiple Telegram projects to stay lightweight, consistent, and easy to maintain over time.

Why HyperCore Exists

Telegram bot and userbot projects often repeat plugin loading, command registration, configuration, client setup, and utility patterns across repositories.

HyperCore turns those recurring pieces into one reusable layer, eliminating duplicate setup code while establishing standard runtime behaviors and lifecycle safety across deployments.

What HyperCore Provides

The core engine delivers essential infrastructure for modern Telegram automation:

• Command System — A common structure for defining, registering, and handling commands with permission guards.
• Event System — Lets different parts of the project react to events through a shared, decoupled event bus.
• Plugin Loader — Isolated plugin structure that discovers modules and validates manifest requirements dynamically.
• Platform Integration — Unified integration points for Telethon and python-telegram-bot runtimes.
• Runtime & Lifecycle Guard — Single-instance process lock, credential-free health checks, and graceful shutdown handling.

Architecture Preview

v0.3.0 → v0.5.0 Transition

The evolution from v0.3.0 to v0.5.0 refined the core from a Python-only framework into a polyglot-ready architecture. While the Python kernel remains the authoritative source of truth for command dispatch and event loop handling, v0.5.0 introduces an optional Node.js runtime bridge.

This allows external TypeScript plugins to communicate with the Python core over a versioned, line-delimited JSON IPC protocol without compromising internal security or requiring Python rewrites.

Further Reading