wushenghua
d6cf54d724
The runner kills a runner-spawned child whose "session started" webhook misses its bounded wait (15s by default), so a cold resume whose thread has a large rollout always failed with "Session webhook timeout for PID ...": the codex shared runtime only reported after reconciling the full native history (projection.history + refresh + refreshChildren), and replaying tens of thousands of items took longer than that wait. Measured on this machine before the fix: two ~800MB rollouts (36k/43k lines) needed 17-20s to bind; one attempt was killed 2s before its late webhook landed and was reaped as an orphan. Split SharedCodexRoot.bind() into the local claim (queue, projection, metadata, settings) and a separate syncHistory(); runSharedRuntime.bind() now activates the session and reports it to the runner before the replay. The session is controllable when the signal fires (controls registered), and the replay continues in the background; re-sent history is idempotent because projection uses stable message ids that the hub dedupes by local_id. Covered by root.test.ts: bind performs no native history reads, syncHistory does the reconciliation.
HAPI
Run official Claude Code / Codex / Cursor Agent / DeepSeek Harness / Grok Build / OpenCode / Kimi / Copilot / Antigravity / Pi sessions locally and control them remotely through a Web / PWA / Telegram Mini App.
Why HAPI? HAPI is a local-first alternative to Happy. See Why Not Happy? for the key differences.
Features
- Seamless Handoff - Work locally, switch to remote when needed, switch back anytime. No context loss, no session restart.
- Native First - HAPI wraps your AI agent instead of replacing it. Same terminal, same experience, same muscle memory.
- AFK Without Stopping - Step away from your desk? Approve AI requests from your phone with one tap.
- Your AI, Your Choice - Claude Code, Codex, Cursor Agent, DeepSeek Harness, Grok Build, OpenCode, Kimi, Copilot, Antigravity, Pi—different agents, one unified workflow.
- Terminal Anywhere - Run commands from your phone or browser, directly connected to the working machine.
- Voice Control - Talk to your AI agent hands-free using the built-in voice assistant.
- Workspace Browser - Opt-in via one or more
hapi runner start --workspace-root <path>flags: browse scoped file trees from the web and start sessions in allowed subdirectories.
Demo
https://github.com/user-attachments/assets/38230353-94c6-4dbe-9c29-b2a2cc457546
Getting Started
npx @twsxtd/hapi hub --relay # start hub with E2E encrypted relay
npx @twsxtd/hapi # run claude code
hapi server remains supported as an alias.
The terminal will display a URL and QR code. Scan the QR code with your phone or open the URL to access.
The relay uses WireGuard + TLS for end-to-end encryption. Your data is encrypted from your device to your machine.
For self-hosted options (Cloudflare Tunnel, Tailscale), see Installation
Docs
Native apps (iOS / Android)
Fully native SwiftUI and Kotlin Compose clients are in development under ios/ and android/. They pair with your hub by scanning the same terminal QR code as the web app, and follow the same protocol — see the client contract docs.
Build from source
bun install
bun run build:single-exe
Credits
HAPI means "哈皮" a Chinese transliteration of Happy. Great credit to the original project.