Feishu Interactive Button Cards

Problem This Solves

When a Hermes Agent sends only plain text in Feishu, approval flows, confirmations, and task feedback feel thin: users do not get clickable actions, and the backend cannot easily tell which button was pressed.

How It Works

The skill packages Feishu interactive cards into reusable Python modules:
- approval.py covers the approval workflow: send_exec_approval() sends an approval card with buttons, handle_card_action() processes button callbacks, and update_approval_card() updates the card after a click.
- builder.py handles card construction: build_streaming_pre_answer_card() creates a streaming response card, build_complete_card() creates the final card, and split_reasoning_text() extracts reasoning text from a response.
- cardkit.py handles low-level sending and updates: send_interactive_card() sends an interactive card, while patch_interactive_card() updates an existing card.

Feishu buttons usually use primary, default, and danger types for main, secondary, and destructive actions. The button's value is returned to the backend when clicked, so the handler can distinguish the selected action.

Scope And Caveats

It is built for Feishu / Lark, not as a generic messaging-button solution. Discord, Telegram, and Slack each require their own component formats. It assumes Python 3.11+ and hermes_feishu_plugin, and is loaded from the Hermes Agent skill directory.