Bug Description

Describe the bug

When using Hermes Agent through the Feishu (飞书 / Lark) gateway, the Command Approval flow frequently fails with error code 200340 ("出了错了，请稍后重试 code: 200340").

This happens specifically when Hermes tries to execute a dangerous/sensitive command that requires manual approval (e.g. rm -v ... deleting files in a Claude versions directory).

Steps to reproduce

1. Connect Hermes to Feishu via hermes gateway setup (Feishu bot).
2. Trigger a task that requires a dangerous command (for example, file deletion or modification in a protected path).
3. Hermes sends the "Command Approval Required" card with buttons: Allow Once, Session, Always, Deny.
4. Click any approval button → the approval does not register properly.
5. Hermes reports: "出了错了，请稍后重试 code: 200340" and the task gets stuck (often showing "Still working..." with iteration count).

In the same situation, switching to CLI/TUI mode allows the approval to work immediately.

Expected behavior

The approval flow (Allow Once / Session / Always) should work reliably on Feishu, just like it does on Telegram or in the terminal.

Actual behavior

• The approval card often shows as "(已编辑)" (edited).
• Backend approval service fails to process the callback.
• Error code 200340 is returned.
• Hermes itself described it as "local sandbox approval service temporary issue".

Environment

• Hermes version: [please run hermes --version and fill this in]
• Gateway: Feishu/Lark
• OS: [e.g. macOS / Linux]
• How Hermes is running: Local installation

Additional context

• Using rm command triggers the sandbox approval (as expected for safety).
• Switching to Python os.remove() temporarily bypasses the approval, but this is not ideal.
• Feishu is very convenient for daily use, so having a reliable approval flow on it would be a big improvement.
• This issue seems related to how Feishu handles interactive message cards / callbacks compared to other platforms.

Screenshots

[Attach the screenshot you showed me]

Workarounds

• Use CLI/TUI for dangerous commands.
• Restart the gateway (hermes gateway restart).
• Use safer alternatives (Python os module instead of shell rm).

Would love to see this fixed so Feishu can be used as a first-class gateway for approval-heavy workflows.

Thanks for the great project!

Steps to Reproduce

1. Set up Hermes with the Feishu (飞书 / Lark) gateway using hermes gateway setup.
2. Start a task that requires executing a dangerous/sensitive command (e.g. rm -v to delete files in a protected path like Claude versions directory).
3. Hermes sends the "Command Approval Required" interactive card in Feishu with buttons: Allow Once, Session, Always, Deny.
4. Click any approval button (Allow Once / Session / Always).
5. The approval does not register properly — the card often shows as "(已编辑)".
6. Hermes fails with error: "出了错了，请稍后重试 code: 200340" and the task gets stuck ("Still working..." with iteration count).

Expected Behavior

The Command Approval flow should work smoothly on Feishu, just like it does in the CLI/TUI or on Telegram.

When I click "Allow Once", "Session", or "Always":

• The approval should be successfully registered by the backend.
• The dangerous command should execute (or be allowed for the session).
• No error code 200340 should appear.
• The task should continue without getting stuck.

Actual Behavior

When I click any of the approval buttons ("Allow Once", "Session", or "Always") in the Feishu gateway:

• The approval card often shows as "(已编辑)" (edited).

• The backend does not register the approval successfully.

• Hermes immediately returns the following error:

  出了错了，请稍后重试 code: 200340

• The task gets stuck, showing messages like:
  "Still working... (10 min)"
  "elapsed — iteration 2/90, running:"

• The dangerous command (e.g. rm -v ...) is not executed, and the approval flow fails.

This issue does not happen when using the CLI/TUI mode — approval works instantly there.

Hermes itself mentioned it was a "local sandbox approval service temporary issue".

Affected Component

Gateway (Telegram/Discord/Slack/WhatsApp)

Messaging Platform (if gateway-related)

No response

Operating System

mac mini m4 tahoe 26.3

Python Version

3.11.14

Hermes Version

0.8.0

Relevant Logs / Traceback

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

• I'd like to fix this myself and submit a PR