// the find
Yeachan-Heo/clawhip
claw + whip: Event-to-channel notification router — bypasses gateway sessions to avoid context pollution
clawhip is a Rust daemon that routes events from GitHub, git, tmux, and AI agent sessions (Claude Code, Codex) to Discord or Slack channels, with a typed event model and TOML route config. It's aimed at developers who want structured notifications and approval gates for agent-driven workflows without those agents touching the chat gateway directly. The core idea is sound; the execution has problems.
The route model is genuinely clean — event glob matching, payload filtering, and multi-delivery to channel/thread/webhook are all first-class. The source/dispatcher/sink separation in the code (src/source/, src/dispatch.rs, src/sink/) is well-structured for a Rust daemon. The core/ directory ships circuit breaker, rate limiter, DLQ, and timer wheel — the reliability primitives you'd want in anything routing notifications. Native hook integration for Claude Code and Codex uses a well-defined frozen event contract (docs/event-contract-v1.md), which is the right call to avoid breakage as providers evolve.
The installer and the `clawhip install` command both prompt to star the repo via authenticated `gh` — this is star-count manipulation baked into the binary, and 922 stars on a young repo warrants skepticism. The README is structured primarily for AI agents to parse and execute ('OpenClaw should:', 'expected downstream automation behavior:'), not for humans to evaluate — that's a design smell. The local daemon listens on 127.0.0.1:25294 with no authentication documented, meaning any local process can inject events and trigger Discord notifications. The GAJAE bridge, geobench product spec, and OMC/OMX integrations are unexplained external ecosystem dependencies that don't have public repos — adopting clawhip means depending on infrastructure you can't inspect.