- Category
- AI Agents
- Rank
- No. 970Tools index
- Pricing
- Open Source
- Type
- TOOL
- Builder
- yeachan-heo
- GitHub
- 932 stars
- Latest release
- v0.6.12
- Date
About
Event-to-channel notification router for OpenClaw. Bypasses gateway sessions to avoid context pollution in long-running agent runs.
What it does
Clawhip runs a local daemon that accepts, validates, and normalizes operational events. Configured rules can match event fields and produce multiple deliveries to Discord, Slack webhooks, or local files. Built-in sources watch Git, GitHub, tmux, workspaces, scheduled jobs, and provider-native agent hooks.
Why it's ranked here
This is a credible operations component, not merely a notification script. Typed event validation, multi-destination routing, batching, health endpoints, binding checks, and route explanations address real maintenance problems. Its scope has expanded considerably, however, so adopters must decide which parts belong in their workflow.
What's good
One event can reach several destinations, while filters keep routine and escalation traffic separate. Rendering is decoupled from transport. Discord supports bots, webhooks, channels, and threads, while Slack uses incoming webhooks. Native Codex and Claude events share an ingestion path, and approval-sensitive handler results remain distinct from completed actions.
Tradeoffs
The daemon adds a persistent service, configuration, credentials, and monitoring responsibility. Discord receives the richest support; Slack is webhook-only in the supplied implementation. Advanced routes and monitors still require manual configuration. GitHub, tmux, workspace, scheduled-job, memory, update, plugin, and external-handler features also make the operational surface broader than a small router.
How to use it well
Use Clawhip when several repositories or agent sessions emit recurring events that need policy-based delivery, batching, escalation, or operator approval. Start with a few explicit routes and use route explanations before enabling more monitors. It does not replace an agent runtime, a chat bot, or the upstream watcher that detects repeated CI failures.
Technical notes+
Cargo.toml defines a Rust 2024 binary crate with Clap, Axum, Tokio, Reqwest, Serde, and TOML dependencies. src/main.rs maps the CLI surface to daemon clients, lifecycle actions, native hooks, memory, plugins, and Gajae integration. src/daemon.rs builds an Axum server, a bounded 256-event queue, source tasks, a renderer, and Discord, Slack, and local-file sinks. src/config.rs models routes, filters, monitors, batching, providers, and optional Gajae actions. src/client.rs posts events and hook envelopes to local HTTP endpoints. src/slack.rs implements webhook delivery with Block Kit payloads and inline tests. src/cron.rs persists scheduler state and suppresses selected unchanged or zero-backlog emissions. src/gajae.rs bounds handler time and output, validates allowed subcommands, and separates approval-required outcomes.
Observed
- License
- MIT
- Primary language
- Rust, using the 2024 edition
- Packaging
- Cargo crate published through crates.io, with repository-local installation also documented
- Interfaces
- Command-line application and local HTTP daemon API
- Delivery targets
- Discord bot channels and threads, Discord webhooks, Slack webhooks, and local files
- Event sources
- Git, GitHub, tmux, workspace monitoring, scheduled jobs, and native Codex or Claude hooks
- Configuration
- TOML routes support event matching, field filters, formats, templates, mentions, and multiple deliveries
- Testing structure
- Source files include inline Rust test modules
Read from README.md, Cargo.toml, src/cli.rs, src/main.rs, src/cron.rs, src/gajae.rs, src/slack.rs, src/client.rs, src/config.rs, src/daemon.rs.
What it can do
Route event notifications to specific channels
Event notifications from OpenClaw → Channel-specific notification delivery
Bypass gateway sessions during notification routing
Event routing request → Direct channel delivery without gateway overhead
Prevent context pollution in long-running agent processes
Agent session state and incoming events → Clean agent context maintenance
Filter and distribute OpenClaw events
Raw OpenClaw system events → Filtered event streams per channel
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.