What problem does it solve?
It solves the problem of keeping users informed about important workflow progress in Feishu/Lark without breaking or delaying the main task when Feishu is misconfigured or unavailable.
Core Features & Use Cases
- Config-guarded notifications (no-op when missing): Reads ~/.claude/feishu.json and silently does nothing when the file is absent, ensuring existing workflows stay unaffected.
- Push-only or interactive modes: Sends webhook notifications in push mode, or uses a local bridge in interactive mode to approve/reject and relay replies back to the calling skill.
- Event-based messaging: Supports standardized event types such as experiment_done, review_scored, checkpoint, pipeline_done, error, and custom for consistent status updates across skills.
Quick Start
Tell the system to run feishu-notify with your message, for example: "feishu-notify 'Notify that the experiment has finished and include the latest results summary'."