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

Files

T

weishu 4f03f29ac3 docs: rebrand Happy to HAPI and add component documentation

This commit rebrands the project from "Happy" to "HAPI" throughout the codebase, including documentation, comments, logs, and tool references. It also adds comprehensive README files for the server and web components, clarifies the monorepo structure in AGENTS.md and root README.md, and removes the outdated roadmap.md file.

Changes include:
- Rebrand references from Happy to HAPI in CLI, server, and web components
- MCP tool names updated from mcp__happy__ to mcp__hapi__
- Process/service names updated consistently
- New server/README.md with deployment and configuration guide
- New web/README.md with stack and development instructions
- Updated root README.md with quickstart guide
- Updated AGENTS.md with cleaner structure documentation
- Removed cli/roadmap.md (now superseded by documentation)

2025-12-21 18:49:04 +08:00

1.0 KiB

Raw Blame History

hapi-web

React Mini App / PWA for monitoring and controlling hapi sessions.

What it does

Session list with status, pending approvals, and summaries.
Chat view with streaming updates and message sending.
Permission approval and denial workflows.
Machine list and remote session spawn.
File browser and git status/diff views.
PWA install prompt and offline banner.

Runtime behavior

When opened inside Telegram, auth uses Telegram WebApp init data.
When opened in a normal browser, you can log in with the shared CLI_API_TOKEN.
Live updates come from the server via SSE.

Development

From the repo root:

bun install
bun run dev:web

If testing in Telegram, set:

WEBAPP_URL to the public HTTPS URL of the dev server.
CORS_ORIGINS to include the dev server origin.

Build

bun run build:web

The built assets land in web/dist and are served by hapi-server. The single executable can embed these assets.

Stack

React 19 + Vite + TanStack Router/Query + Tailwind.

1.0 KiB Raw Blame History