mirror of https://github.com/wu736139669/hapi.git synced 2026-08-05 06:24:37 +00:00

Files

T

weishu bb9c5b66d3 refactor(telegram): remove interactive features and simplify to notifications only

Remove all interactive features from the Telegram bot that are now handled by the
Telegram Mini App. The bot now serves a single purpose: sending notifications for
permission requests and ready events.

Changes:
- bot.ts: Remove /help command and message handler, simplify /start to show Mini App link
- callbacks.ts: Remove all callback handlers except APPROVE and DENY for permissions
- sessionView.ts: Remove detail views and settings, keep only notification formatting
- renderer.ts: Remove session/machine list rendering, keep utility functions

This reduces the codebase by ~1000 lines (58% reduction) while preserving notification
functionality that the Mini App cannot provide.

2025-12-24 14:23:01 +08:00

scripts

feat: add session cleanup script with flexible filtering options

2025-12-23 17:45:15 +08:00

src

refactor(telegram): remove interactive features and simplify to notifications only

2025-12-24 14:23:01 +08:00

package.json

refactor: unify runtime directories and environment variables to HAPI_HOME

2025-12-21 19:17:07 +08:00

README.md

feat: make Telegram optional and unify user authentication with owner ID

2025-12-22 08:52:51 +08:00

tsconfig.json

feat(cli): add single executable with embedded web assets support

2025-12-21 08:42:00 +08:00

README.md

hapi-server

Telegram bot + HTTP API + realtime updates for hapi.

What it does

Telegram bot for notifications and the Mini App entrypoint.
HTTP API for sessions, messages, permissions, machines, and files.
Server-Sent Events stream for live updates in the web app.
Socket.IO channel for CLI connections.
Serves the web app from web/dist or embedded assets in the single binary.
Persists state in SQLite.

Typical deployment flow

Configure env vars.
Expose the server to the internet (HTTPS) if you need Telegram Mini App access.
Run the server.
Point the CLI to the server and open the web app.

Configuration

Required:

CLI_API_TOKEN - shared secret used by CLI and web login.

Optional (Telegram):

TELEGRAM_BOT_TOKEN - token from @BotFather.
ALLOWED_CHAT_IDS - comma-separated chat IDs allowed to use the bot.
WEBAPP_URL - public HTTPS URL for Telegram Mini App access.

Optional:

WEBAPP_PORT - HTTP port (default: 3006).
CORS_ORIGINS - comma-separated origins, or *.
HAPI_HOME - data directory (default: ~/.hapi).
DB_PATH - SQLite database path.

Running

Binary (single executable):

export TELEGRAM_BOT_TOKEN="..."
export ALLOWED_CHAT_IDS="12345678"
export CLI_API_TOKEN="shared-secret"
export WEBAPP_URL="https://your-domain.example"

hapi server

If you only need web + CLI, you can omit TELEGRAM_BOT_TOKEN and ALLOWED_CHAT_IDS. To enable Telegram, set TELEGRAM_BOT_TOKEN and WEBAPP_URL, start the server, send /start to the bot to get your chat ID, set ALLOWED_CHAT_IDS, and restart the server.

From source:

bun install
bun run dev:server

Or inside server/:

bun run start

Build for deployment

From the repo root:

bun run build:server
bun run build:web

The server build output is server/dist/index.js, and the web assets are in web/dist.

Networking notes

Telegram Mini Apps require HTTPS and a public URL. If the server has no public IP, use Cloudflare Tunnel or Tailscale and set WEBAPP_URL to the HTTPS endpoint.
If the web app is hosted on a different origin, set CORS_ORIGINS accordingly.

Architecture overview

The server is the hub for direct-connect mode. It accepts CLI connections over Socket.IO, exposes HTTP endpoints for the web UI, and publishes live updates over SSE. A Telegram bot provides notifications and a Mini App entrypoint. Session and machine state are stored in a local SQLite database.

Security model

Access is controlled by:

Telegram chat ID allowlist (when Telegram is enabled).
CLI_API_TOKEN shared secret for CLI and browser access.

Transport security depends on HTTPS in front of the server.